superpowers-writing-plans

To generate an implementation plan from a feature spec, provide your high-level requirements to produce a structured task breakdown saved as a dated Markdown document in the docs/plans directory. This plan outlines bite-sized, testable steps for engineers.

Breaking down multi-step engineering tasks for TDD involves splitting high-level requirements into bite-sized, testable steps that identify touched files, code, tests, and docs. This structured task breakdown enforces DRY, YAGNI, and TDD principles while outlining clear milestones and commits.

This plan generation workflow requires no external dependencies or components. It operates using a frontmatter-based YAML Skill entry to process your feature spec and output the final versioned plan delivery directly to your filesystem.

The generated implementation plan gets saved and versioned by writing the final Markdown document to docs/plans with a date stamp and feature name. This creates a dated, feature-named file at docs/plans/YYYY-MM-DD-<feature-name>.md for versioned plan delivery.

Yes, you can use this task planning approach for projects starting from high-level requirements. It applies specifically to projects needing bite-sized, testable steps, documentation, and versioned plan delivery before the actual coding begins.

Using a dedicated workflow for implementation plan generation ensures nothing is missed before coding by systematically enforcing DRY, YAGNI, and TDD principles. It transforms a clear spec into actionable tasks with identified touched files, tests, and clear milestones for frequent commits.