Appearance
Planning
What
A plan records the approach, files, steps, tests, risks, rollback, and open questions.
Why
It makes reasoning reviewable before code changes.
When
Use for any task where the change is not obvious.
Example
See templates/plan.md.
Common mistake
Treating a plan as a promise when new evidence invalidates it.
Checklist
- [ ] Each step has a reason
- [ ] Tests and rollback are considered
Next step
Implement in small steps.