test-driven-development
Write tests first, watch them fail, then implement minimal code to pass.
What it does
- New features
- Behavior changes
- Throwaway prototypes
- Generated code
- Configuration files
- Don't keep it as "reference"
- Don't "adapt" it while writing tests
Requirements & configuration
- | "Need to explore first" | Fine. Throw away exploration, start with TDD. |
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
Write tests first, watch them fail, then implement minimal code to pass.
Source
Repository: https://github.com/obra/superpowers
test-driven-development FAQ
What does the test-driven-development skill do?
Use when implementing any feature or bugfix, before writing implementation code New features Behavior changes
What does test-driven-development require?
| "Need to explore first" | Fine. Throw away exploration, start with TDD. |
How do I install test-driven-development?
Run: npx -y skills add https://github.com/obra/superpowers --skill test-driven-development --agent claude-code — the source lives at github.com/obra/superpowers.
Maintain test-driven-development?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[](https://getagentictools.com/skills/obra-superpowers-test-driven-development?ref=badge) npx agentictools info skills/obra-superpowers-test-driven-development The second line is the CLI lookup for this page — handy in READMEs and docs.