writing-plans

Turning a software spec into an implementation plan involves decomposing requirements into design units, mapping required files, tests, and boundaries for each task, and outputting a structured document with a header and task breakdown.

The best way to plan multi-step coding tasks is to generate an end-to-end plan detailing files, tests, and commit steps, while running a recurrent plan review loop to ensure structured execution before code changes.

Yes, you can save implementation plans to a custom directory. While the default location is docs/superpowers/plans/YYYY-MM-DD-feature-name.md, the skill provides override options to specify your preferred custom save path.

Yes, this implementation planning approach operates in a dedicated worktree workflow, keeping your brainstorming and planning sessions isolated from main branches to prevent interference with active development.

A plan review loop is a recurrent validation process that refines task decomposition and design unit boundaries before execution handoff. You need it for multi-step tasks to reduce ambiguity and rework across engineering teams.

Starting coding without an end-to-end implementation plan increases ambiguity and rework across teams. Generating a structured plan with detailed commit steps and file mappings first ensures structured execution and reduces errors.