writing-plans

To generate an implementation plan from a spec, you need a task-by-task breakdown detailing files to create or modify, tests to write, and documentation steps. This ensures engineers have structured guidance before touching code.

The best way to decompose multi-step engineering tasks is to draft a comprehensive plan enforcing DRY, YAGNI, and TDD principles. This produces focused, actionable steps for development, testing, and documentation across your codebase.

You structure test-driven development plans by generating a document that specifies exact tests to write alongside file modifications. This approach integrates testing directly into the task decomposition phase before coding begins.

Writing implementation plans does not require specific dependencies or components. It operates independently to generate a structured markdown file detailing file changes, tests, and commit steps for your engineering project.

You should save the generated implementation plan file in your project at docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md. This standardizes documentation and ensures plans are easily accessible for the engineering team.