writing-plans

Map out the file structure first, then decompose work into bite-sized tasks of 2-5 minute steps. Each task follows TDD: write the failing test, run it, implement minimal code, verify it passes, and commit. Include exact file paths and complete code in every step.

Each step should be one action taking 2-5 minutes, such as writing a single test or running one command. Tasks must be self-contained with exact paths, full code blocks, and expected command output so an engineer with zero context can execute them independently.

Split when the spec covers multiple independent subsystems. Each plan should produce working, testable software on its own. If the spec was not broken into sub-project specs during brainstorming, suggest separate plans per subsystem before writing.

Plans fail when they contain placeholders like TODO or 'add error handling', reference undefined functions, or use inconsistent naming across tasks. A self-review checking spec coverage, placeholder patterns, and type consistency catches these issues before handoff.

Save plans to docs/superpowers/plans/YYYY-MM-DD-feature-name.md by default, though user preferences for plan location override this. The plan header must state the goal, architecture, tech stack, and required execution sub-skill.