Test-Driven Development is the Superpowers skill for every feature, bug fix, refactor and behavior change. Its iron law is no production code without a failing test first. The agent writes one minimal test, runs it and confirms it fails for the right reason, writes the simplest code that passes, then runs the whole suite and refactors while it stays green.
What You Get
- The red-green-refactor cycle with a diagram and paired good and bad examples
- Mandatory verify-red and verify-green steps
- A checklist to confirm before marking work complete
- A table of common excuses and the reply to each
- A bug-fix example that begins with a reproducing test
Common Use Cases
- Building a new feature test first
- Fixing a bug with a reproducing test
- Refactoring with a safety net
What Makes It Unique
Many TDD guides describe the cycle. This one sets rules for an agent that talks itself out of tests: it requires deleting code written before its test, makes watching the failure a mandatory step, and extends verification to the full project suite, with any failure reported by name.
Under The Hood
Instructions with TypeScript examples and a reference file on writing good tests. The agent runs the project’s own test command, such as npm test, pytest or cargo test. The skill ships no scripts of its own.