Test-Driven Development (TDD)
Test-Driven Development (TDD)
Overview
Write the test first. Watch it fail. Write minimal code to pass.
Core principle: If you didn't watch the test fail, you don't know if it tests the right thing.
Violating the letter of the rules is violating the spirit of the rules.
When to Use
Always:
- New features
- Bug fixes
- Refactoring
- Behavior changes
Exceptions (ask your human partner):
More from obra/superpowers-skills
getting started with skills
Skills wiki intro - mandatory workflows, search tool, brainstorming triggers
297brainstorming ideas into designs
Interactive idea refinement using Socratic method to develop fully-formed designs
11writing plans
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
9systematic debugging
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
9code review reception
Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation
8executing plans
Execute detailed plans in batches with review checkpoints
8