writing-plans

To create an implementation plan from a software specification, define tasks, files, tests, and steps before coding to ensure alignment. This process converts vague specs into concrete blueprints by decomposing complex projects into bite-sized tasks mapped to exact file changes.

Task decomposition in software engineering planning is the process of breaking down complex project requirements into structured, bite-sized tasks. It creates decomposition-driven task trees that map directly to exact file changes, tests, and documentation for incremental commits.

You document multi-step software tasks by generating comprehensive implementation plans that outline files, tasks, tests, and review steps. Save these plans to docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md to provide versioned reference and ensure traceability across the team.

You need to generate a plan document before coding when starting a new feature with a spec or set of requirements. Generating a plan beforehand guides engineers through design, implementation, review, and verification, ensuring alignment and traceability before any code is written.

Yes, you can iteratively refine an implementation plan as project requirements change by breaking down complex projects into bite-sized tasks. This structured planning approach allows tasks to be committed incrementally, supporting continuous adjustment throughout the development lifecycle.