Use when implementing any feature or bugfix, before writing implementation code
Security grade of this SKILL.md: SAFE · how we grade
How to install test-driven-development
npx skills add obra/superpowers --skill test-driven-development -a claude-code
The skills CLI copies this one skill into Claude Code (use -a for another agent). Or read its SKILL.md on GitHub.
What the SKILL.md says
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. Always: New features. Bug fixes. Refactoring. Behavior changes. Exceptions (ask your human partner): Throwaway prototypes. Generated code. Configuration files. Thinking "skip TDD just this once"? Stop. That's rationalization. Write code before the test? Delete it. Start over. No exceptions: Don't keep it as "reference". Don't "adapt" it while writing tests. Don't look at it. Delete means delete. Implement fresh from tests. Period. Write one minimal test showing what should happen. Clear name, tests real behavior, one thing Vague name, tests mock not code Requirements: One behavior. Clear name. Real code (no mocks unless unavoidable). MANDATORY. Never skip.
Other skills in obra/superpowers
brainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning…
diagnosing-superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results,…
dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
executing-plansUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, o…
finishing-a-development-branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work
receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable…
requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirements
subagent-driven-developmentUse when executing implementation plans with independent tasks in the current session
systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
using-git-worktreesUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated w…
using-superpowersUse when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clari…
verification-before-completionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and…
writing-plansUse when you have a spec or requirements for a multi-step task, before touching code
writing-skillsUse when creating new skills, editing existing skills, or verifying skills work before deployment