superpowers-writing-plans

To write an implementation plan, generate a comprehensive document covering bite-sized tasks, files to touch, tests to write, and documentation. Save the plan under docs/plans/YYYY-MM-DD-<feature-name>.md using a Feature Implementation Plan template.

Breaking down vague requirements involves applying structured task splitting to produce bite-sized tasks. This planning workflow defines precise file touchpoints, testing guidance, and documentation for future maintainers to ensure all context and dependencies are clarified.

Test-driven development fits into feature planning by defining specific tests to write for each task. The planning process encourages adherence to TDD principles, ensuring verification steps and testing guidance are established before touching code.

Yes, you can use this planning workflow for projects with evolving or unclear requirements. It enables structured task breakdown and establishes a repeatable planning workflow to manage dependencies and context as requirements change.

When creating a plan document, you should follow DRY, YAGNI, and TDD principles. Adhering to these software engineering principles during planning ensures tasks are comprehensive, avoid redundancy, and focus on necessary features.

You should avoid using a detailed feature implementation plan for single-step tasks or trivial changes that do not require structured task breakdown, file touchpoint tracking, or testing guidance, as the overhead would outweigh the benefits.