Documentation
README
Writing Plans
For complex tasks, always plan before implementing.
Plan Structure
- Goal: What are we trying to achieve?
- Approach: High-level strategy
- Steps: Ordered, actionable items
- Risks: What could go wrong?
- Alternatives: What else was considered?
When to Plan
- Task spans multiple files or modules
- User explicitly asks for a plan
- Architecture decisions are needed
- Breaking changes to existing APIs
Anti-Patterns
- Planning for trivial tasks (single-file, single-function)
- Over-planning: more time planning than coding
- Plan has no action items — just abstract theory