| name | implement-plan |
| description | Works through the next open phase of a plan, implementing toward its acceptance criteria and checking each off as it is verified. Use when the user wants to execute an existing implementation plan one phase at a time. |
Implement Plan
Read the referenced plan and work through one phase at a time.
Workflow
- Read the plan and find the next phase with unmet acceptance criteria (
- [ ])
- Read that phase's Context block — it lists the relevant files
- Critically review the phase with that context in hand — check for ambiguous acceptance criteria, missing context, or conflicting instructions. Raise concerns with the user first; if there are none, proceed
- Implement the phase's "What to build", working toward its acceptance criteria
- Check off each acceptance criterion (
- [ ] → - [x]) once you have verified it
- After the phase's criteria are met: run the project's build, lint, and test suite
- Stop — do not start the next phase
When to stop
Stop and ask the user rather than guessing when:
- A required dependency, file, or instruction is missing or unclear
- Verification (build/lint/test) fails repeatedly for the same reason
Constraints
- Prefer simple, clear, idiomatic solutions
- No performance optimisation at the cost of readability
- Small local duplication is fine when it makes the code more understandable
Quality
- Once the phase is implemented, run the shared
self-review checklist on the change. Surface issues in the
chat only if found.
