// Use when a plan exists and needs to be executed or continued. Reads the plan, works task by task, commits after each, and pauses at phase boundaries.
| name | execute-plan |
| description | Use when a plan exists and needs to be executed or continued. Reads the plan, works task by task, commits after each, and pauses at phase boundaries. |
Start or continue executing this plan: $ARGUMENTS
- [ ])- [x] in the same commit as the code changego test ./...For each task:
- [ ] to - [x]If the plan contains parallel notation:
**Parallel Tasks: 2b, 2c**
- [ ] 2b: Task one
- [ ] 2c: Task two
Execute these simultaneously using multiple agents, then commit each separately.
For parallel phases (**Parallel Phases: 2,3**), spawn agents for each phase and work them concurrently.
Naming convention — phase number + letter:
1a: Add Cell and Axis structs
1b: Add Workbook and Sheet structs
2a: Implement text format parser
Every commit includes the checkmark update to the plan file.
At the end of each phase:
go test ./...When pausing or completing, report:
When all tasks in a plan are marked - [x], the plan is complete. Run /manage-plans to archive it to plans/archive/.
Use when the user wants to plan a task, feature, or change. Creates a structured plan with phases and checkmarked subtasks.
Review, archive, and clean up plans. Use to archive completed plans, list plan status, or tidy the plans directory.