writing-plans

Implementation plans are generated by breaking down a project spec into end-to-end task lists, mapping each task to concrete files, tests, and documentation. This ensures traceability and prevents scope creep during feature development and project scoping.

Breaking down multi-step feature development tasks involves mapping work to concrete files, tests, and documentation to ensure traceability. This approach delivers a complete plan that engineers, testers, and documentation teams can follow for cross-functional handoffs.

Mapping project scope to specific files and tests is achieved by generating a comprehensive implementation plan from a given spec. This process ensures every task within the project scope is directly linked to specific files, tests, and documentation for complete traceability.

Generated implementation plans are saved to docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md. This structured file path ensures plans are organized by date and feature name, containing design, task lists, tests, docs, and commit recommendations.

This planning approach supports cross-functional handoffs by delivering a complete implementation plan that engineers, testers, and documentation teams can follow. It maps work to concrete files, tests, and documentation to ensure clear traceability across all roles.

You can avoid scope creep when starting a project with a spec by generating comprehensive, implementation-ready plans. This approach strictly maps project scope to specific tasks, files, tests, and documentation, keeping feature development tightly controlled.