// Use when you have a written implementation plan to execute. Load plan, review critically, execute tasks in batches with verification.
Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when executing implementation plans with independent tasks. Dispatches subagents per task with two-stage review (spec then quality).
Use when encountering any bug, test failure, or unexpected behavior. Always find root cause before attempting fixes. Evidence before assertions.
Use when implementing any feature or bugfix. Write the test first, watch it fail, write minimal code to pass. Red-Green-Refactor cycle.
Use when about to claim work is complete, fixed, or passing. Run verification commands and confirm output before making any success claims. Evidence before assertions.
Use when you have a spec or requirements for a multi-step task, before touching code. Creates detailed implementation plans with bite-sized tasks.
| name | executing-plans |
| description | Use when you have a written implementation plan to execute. Load plan, review critically, execute tasks in batches with verification. |
Load plan, review critically, execute tasks in batches, verify after each task.
Core principle: Batch execution with verification checkpoints.
Default: First 3 tasks
For each task:
When batch complete:
Based on feedback:
After all tasks complete:
STOP executing immediately when:
Ask for clarification rather than guessing.