Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
Tasks
Create the tasks/ directory (if it does not exist) and save the implementation plan to tasks/plan.md using the provided Plan Document Template.
Save the checklist-style task list to tasks/todo.md, ensuring each task has acceptance criteria, verification steps, dependencies, files likely touched, and an estimated scope.
Arrange tasks into phases (e.g., Foundation, Core Features, Polish) and insert verification checkpoints after every 2-3 tasks or between major phases.
Inputs
A spec or clear requirements
Relevant codebase sections (read during planning)
Human input for open questions and plan review
Outputs
Plan document saved to tasks/plan.md
Task list saved to tasks/todo.md
Limitations and checks
Should not be used for single-file changes with obvious scope
Should not be used when the spec already contains well-defined tasks
No code should be written during planning; the output is plan and task documents only
Confirm every task has acceptance criteria
Confirm every task has a verification step
Confirm task dependencies are identified and ordered correctly
Confirm no task touches more than approximately 5 files
Confirm checkpoints exist between major phases
AI Search
Find projects, verify facts, compare options, or turn a complex need into an actionable plan
Try a searchA click only fills the search box; you stay in control