writing-plans

To create an implementation plan for multi-step software features, provide a feature spec to generate comprehensive task decomposition, mapping tasks to files, tests, and milestones without writing code.

The best way to break down large engineering tasks is scope-aware planning that maps task decomposition to specific files, cross-cutting concerns, and integration points for engineers to execute.

Document project workflows by generating plan documentation that saves to docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md, defining tasks and file structure for isolated worktree auditing.

Yes, you can scope cross-cutting concerns and integration points before writing code by assessing the feature spec to map out complete file structures and task milestones for verification.

This planning approach generates only documentation and does not touch code. It outputs comprehensive plans defining tasks, file structures, and plan steps saved as markdown for engineering reviews.

You need task decomposition for project management when planning large features, ensuring engineers understand exactly what to build, what to touch, and how to verify success before coding begins.