superpowers-writing-plans

To generate an implementation plan, provide your project spec to receive a comprehensive, task-by-task breakdown with clear deliverables, file-structure mapping, and testing plans. It decomposes vague or detailed specs into structured, auditable work items.

Task decomposition is breaking down project specs into structured, step-by-step implementation items with clear owners and dependencies. You need it for multi-team feature development, refactors, or new initiative launches to ensure work is auditable and nothing is missed.

Yes, you can use this for multi-team projects. It generates structured task decomposition with file-structure mapping and dependency planning, ensuring clear deliverables and owners are assigned across teams for complex software engineering tasks.

The best way to document a refactor plan is providing your project spec to generate a comprehensive breakdown. This produces task-by-task implementation items, testing plans, and version-controlled planning exports to ensure the refactor work is fully auditable.

No, you do not need a detailed spec. You can provide either vague or detailed project specs, and the system will generate a complete, task-by-task implementation plan with structured task decomposition, dependency planning, and testing plans.

Your implementation plan lacks clear deliverables because it likely misses structured task decomposition. Providing your project spec generates a comprehensive breakdown with explicit deliverables, owners, file-structure mapping, and version-controlled exports.