writing-plans

To turn an approved spec into an executable plan, you provide the requirements and work-item details to generate a structured document featuring task decomposition, file touchpoints, dependencies, and acceptance criteria.

The best way to plan multi-file work with explicit failure paths is to generate a comprehensive plan document that outlines risk-aware sequencing, validation steps, and a RED/GREEN/REFACTOR workflow before coding.

Yes, cross-team implementation planning requires defining dependencies and file touchpoints before coding to ensure explicit sequencing, failure paths, and risk management are established for complex multi-step work.

To generate a runbook-integrated plan document, you input the approved spec and work-item details, which produces a ready-to-publish markdown file saved to a repository path like docs/superpowers/plans/.

You need a structured task-based plan for software engineering projects when handling multi-file, cross-team work where sequencing, dependencies, failure paths, and risk must be explicit before coding begins.