agent-workflow

Agent Workflow

Mandatory classification, approval, scope, implementation, and review gates are owned by the workflow rule (${HANDBOOK_ROOT}/rules/010-workflow.mdc). This skill owns detailed procedures and templates.

Golden Rules

Follow this three-phase approach for all non-trivial work:

1. PLAN → Design solution → Document approach → WAIT FOR EXPLICIT APPROVAL
2. IMPLEMENT → Code ONLY what was approved → STOP when agreed scope is complete
3. REVIEW → Verify results → Suggest improvements → Return to PLAN phase

Critical Violations to Avoid

- DON'T DO THIS:
User: "Can you add authentication?"
AI: [Immediately starts coding without discussion]

+ DO THIS INSTEAD:
User: "Can you add authentication?"
AI: "Let me design a solution first. Key decisions needed:
     - OAuth 2.0 vs local authentication?
     - JWT tokens vs session-based?
     - User data storage location?
     
     Let's agree on the approach before I write any code."

Why This Matters:

• Skipping planning → Wasted time, wrong solutions, scope creep
• Implementing unplanned features → Breaking existing code, technical debt
• Not stopping after agreed scope → Confusion, frustration, rework

Complexity Levels

Level	Type	Workflow	Example
1	Simple	Direct implementation → Quick review	Fix typo, simple bug fix
2	Moderate	Brief plan → QA → Implement → Review	Add new function
3	Complex	Full Plan → Creative → QA → Implement → Review	Multi-file feature
4	Architectural	Detailed Plan → Creative (mandatory) → QA → Implement → Review	Major refactoring

Phase 1: Planning

You MUST NOT begin implementation until:

• User has explicitly approved the plan
• All clarifying questions have been answered
• The scope is clearly defined and agreed upon

Process:

1. Analyze the request - understand scope, constraints, requirements
2. Check existing code - look for patterns and reusable components
3. Design the solution - propose approach with alternatives
4. WAIT FOR APPROVAL - present plan and await confirmation