superpowers-writing-plans

To break down a complex spec, you structure it into a detailed plan with a clear goal, architecture, tech stack, and a task-by-task breakdown. This ensures multi-step features are executable and independently testable across subsystems.

The best way to apply TDD and YAGNI during feature planning is to enforce these principles directly within the task breakdown. The plan outputs bite-sized tasks ordered from setup to verification, ensuring test-driven development and avoiding unnecessary features.

Planning cross-subsystem changes involves generating one structured plan per subsystem. This approach lists required files, code changes, and verification steps for each subsystem, allowing them to be implemented and tested independently.

Upfront planning is needed for non-trivial software implementations involving multi-step features or complex workflows. It transforms a vague written spec into a complete, executable plan detailing required files, testing, and verification steps.

Yes, spec breakdown works effectively for multi-step features spanning multiple subsystems. It produces a thorough plan detailing required code changes and yields one plan per subsystem that can be implemented and tested independently.