superpowers-writing-plans

To turn specs into a test-driven implementation plan, you decompose multi-component requirements into small-grained, actionable tasks mapping each step to precise file changes, testing steps, and documentation updates.

Breaking down multi-component tasks requires generating small-grained, self-contained work items that explicitly detail file modifications, code segments, testing procedures, and documentation checks for reliable execution.

The best way to structure an implementation plan for TDD workflows is enforcing a small-grained task format that defines testing steps alongside file changes, following DRY and YAGNI principles with frequent commits.

Yes, task decomposition supports cross-module software design reviews by creating independently understandable small tasks mapped to specific file changes and tests, enabling thorough team collaboration and review.

You should avoid small-grained task decomposition for coding when a software project demands rapid prototyping without upfront specs, or when requirements are too ambiguous to map to specific file changes and testing steps.