writing-plans

Turn a formal spec into an implementation plan by processing requirements into a standardized structure with headers, per-task steps, and a review loop. The plan maps file changes, tests, documentation, and validation scenarios before any code is written.

Breaking down multi-subsystem feature tasks requires a structured plan that maps file changes, tests, and validation scenarios per task. This enforces a standardized breakdown with dedicated steps and a review loop to guide developers through large feature work.

Generate implementation checklists by transforming formal specs into structured planning artifacts. These artifacts guide developers through per-task file changes, tests, documentation, commits, and validation scenarios, ensuring comprehensive coverage for large features.

Yes, the implementation planning approach supports a dedicated worktree workflow. It generates reproducible planning artifacts saved as markdown files, ensuring structured task breakdown and file mapping align with isolated development environments.

You need a formal implementation plan from requirements when tackling multi-subsystem tasks or large feature work. It enforces a standardized structure with per-task steps and a review loop before touching code, guiding file changes, tests, and documentation.

The standardized structure for saving generated implementation plans is a markdown file located at docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md. It includes a header, per-task steps, and a review loop to guide the entire implementation process.