writing-plans

An implementation plan maps specs to repository structure by defining file touchpoints, tests, docs, and commit cadence for each task. It breaks down feature-level work into actionable tasks with explicit delivery milestones and clear task boundaries.

The best way to plan refactoring an existing system is to generate a decomposition plan that maps to repository structure and task granularity, defining explicit delivery milestones, file touchpoints, and boundaries to ensure executable, unambiguous steps.

Decompose a feature spec by mapping its requirements to task granularity within your repository structure, explicitly defining file touchpoints, necessary tests, documentation, and commit cadence for each actionable task to ensure clear ownership and boundaries.

Yes, this approach works for introducing a new module by generating a decomposition plan that maps to repository structure and task granularity, explicitly defining commits, file touchpoints, and tests to ensure clear delivery milestones under version control.

Vague specs cause project delays because they fail to translate into concrete, executable steps, creating ambiguity. Generating a detailed implementation plan with clear task boundaries, file touchpoints, and ownership prevents this execution breakdown.

Save implementation plan artifacts for feature-level work to docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md, ensuring the plan includes a commit cadence, file touchpoints, and clear task boundaries for ready-to-implement execution.