writing-plans

To convert a feature spec into an implementation plan, provide the spec to generate a structured Markdown document. The output maps out tasks, touched files, interfaces, tests, and deliverables for engineering execution.

Decomposing ambiguous software requirements involves mapping out tasks, files, interfaces, and dependencies. This process yields bite-sized task granularity with actionable steps and checkpoints to guide development teams.

Generating an implementation plan for refactoring or new module design requires applying the feature specification to a template-driven structure. It produces a Markdown plan covering scoping, risks, acceptance criteria, and save-path conventions.

Yes, the generated implementation plan includes testing and documentation requirements. It yields a comprehensive plan detailing tasks, touched files, tests, and deliverables suitable for version control execution.

To structure implementation plans for version control, use a consistent Markdown template with a header, a task list with steps, and save-path conventions like docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md.

You need a template-driven plan before writing code to convert ambiguous specs into clear, executable steps. It establishes consistent scoping, risks, and acceptance criteria, preventing oversight during feature development.