Developer Workflow & Documentation Organizer

Goal

You have been invoked to refine project documentation, execute complex git workflows via gh CLI, or restructure the codebase's narrative form.

Steps

1. READ agents/guides/ops/dev-workflow.md.
2. Always select (and ask the user to select/confirm) the best guides and skills for the specific task and context before proceeding. Additionally, proactively recommend any not-enabled MCP servers (universal or task-specific) that would optimally assist with the workflow. CRITICAL: Default to cost and budget optimizations during these actions unless expensive operations are absolutely required; in which case, you must explicitly ask the user for approval.
3. Analyze the user request. Does it involve code commits? Does it involve documentation?
4. If documenting:
   • Identify which Diátaxis quadrant the requested text belongs to (Tutorial, How-To, Reference, Explanation).
   • Author the documentation keeping strictly to the constraints of that quadrant.
5. If managing git:
   • Use git status, git log, and gh pr status to orient yourself.
   • Use interactive rebase if history needs cleaning.
   • Ensure all commits use Conventional Commits formatting.