Test-Driven Development
Testingby obra
3/3 audits passMIT
Use when implementing any feature or bugfix, before writing implementation code
Test-Driven Development, published by obra in the superpowers repository under MIT, enforces strict red-green-refactor on a coding agent. Its iron law is no production code without a failing test first: code written before its test is deleted and re-implemented from the test. The cycle is to write one minimal test for one behaviour, run it and confirm it fails for the right reason, write the simplest code that passes, confirm everything is green, then refactor while staying green.
The skill shows good and bad test examples (a clear name and real behaviour versus mock-heavy tests), lists common rationalisations for skipping TDD and red flags that mean start over, walks through a bug-fix example, and ends with a verification checklist and guidance for when stuck. A companion file covers writing good tests. It applies to new features, bug fixes, refactoring and behaviour changes; throwaway prototypes, generated code and configuration are exceptions only with your agreement. It is deliberately strict and slower than writing code first.
This is a skill for coding agents like Claude Code; it has no particular use inside BusinessMCP's business-data workflows.
What you can do with it
- Make an agent write and run a failing test before any feature code
- Fix a bug by first reproducing it in a test
- Refactor safely while keeping the suite green
- Catch an agent rationalising its way out of testing
Run it on your business data
Imported into BusinessMCP, Test-Driven Development becomes a playbook your AI business analyst applies to your product analytics and real user journeys.
Use Test-Driven Development in BusinessMCPInstall it in a coding agent
One command adds Test-Driven Development to your project.
npx skills add https://github.com/obra/superpowers --skill test-driven-developmentHow we vetted it
- Source
- obra/superpowers at 5bf4e78
- Licence
- MIT
- Security audits (skills.sh)
- Gen Agent Trust Hub: Pass · Socket: Pass · Snyk: Pass
- Bundled scripts
- None, instructions only
Checked 2026-09-25 against its skills.sh listing. How we vet skills
Related skills
All skillsWriting Plans
Use when you have a spec or requirements for a multi-step task, before touching code
Testing Strategy
Design test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or…
Systematic Debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Frequently asked questions
How do I install Test-Driven Development?
Run `npx skills add obra/superpowers --skill test-driven-development` to add it to a Claude Code or other skills-compatible agent. You can also import it from the BusinessMCP dashboard, where it becomes a playbook in your workspace.
What is the iron law in this skill?
No production code without a failing test first. If code was written before its test, the skill says to delete it and start over from the test.
Are there exceptions?
Throwaway prototypes, generated code and configuration files can be exceptions, but only after asking your human partner.
Run Test-Driven Development against your whole business
Free plan, no credit card.
Use Test-Driven Development in BusinessMCP