superpowers-writing-plans

To convert a project spec into an implementation plan, provide the high-level spec to generate a detailed, task-by-task breakdown. The plan maps tasks to specific file touchpoints, tests, and documentation references for executable guidance.

An implementation plan for multi-step software tasks requires structured plan headers, discrete task steps, commit guidelines, and file decomposition. It also supports sub-plan generation for complex subsystems to maintain structured execution.

You need to generate an implementation plan before coding when handling multi-step software tasks, feature development, or refactoring scenarios. This ensures engineers have executable task steps, file touchpoints, and testing guidance before starting.

Yes, you can use this for refactoring scenarios and feature development. It applies structured task decomposition to map out file touchpoints, testing requirements, and documentation references for any multi-step software task.

Generated implementation plans are versioned and saved for team handoffs by writing the plan artifact to the docs/superpowers/plans directory using a date-based filename, ensuring organized tracking and easy retrieval.

The best way to decompose a high-level spec into executable coding tasks is to map the spec into discrete task steps with clear file touchpoints. This enforces consistent plan structure and supports sub-plan generation for subsystems.