superpowers-writing-plans

To turn a software spec into an implementation plan, you provide the high-level specification, and the system decomposes it into a sequence of concrete tasks detailing suggested files, tests, and milestones ready for engineering execution.

Plan decomposition for multi-component features is the process of breaking down broad requirements into actionable steps with explicit file changes, task granularity, and validation steps to guide development from definition to delivery.

You generate development documentation by processing a requirement spec into a high-density plan document that maps explicit file changes, outlines prerequisites, and defines validation steps for review by engineers and QA.

Yes, this handles multi-component feature decomposition by applying structured planning to break requirements into actionable steps with explicit file changes, milestones, and commit history tracking for delivery.

Yes, this generates collaboration-ready plan documents designed for review by PMs, engineers, and QA, ensuring task granularity, prerequisites, and validation steps are clearly documented for all stakeholders.