superpowers-writing-plans

To turn software specifications into actionable development plans, you translate them into structured documents with a header, architecture sections, and task-by-task execution guidance that includes tests and commit checkpoints.

Test-driven task planning is structuring development work so each task starts with a failing test, followed by implementing minimal code to pass it, and concluding with a commit checkpoint before moving to the next task.

Plan multi-step features by using a plan template that defines scope and interfaces in a header section, then breaks work into sequential tasks with explicit tests, file boundaries, and review checkpoints.

Yes, you can coordinate plan execution across subagents or inline sessions, as the structured plan format supports both subagent-driven and inline execution to fit different workflow preferences.

The best way to document architecture and scope is using a plan template with dedicated header and architecture sections that define interfaces and boundaries before outlining task-by-task implementation work.

No specific dependencies or frameworks are required to write structured engineering plans, as the planning process relies on a template format with headers, tasks, tests, and checkpoints rather than external libraries.