Implement an approved change one Capability at a time, each test written and watched failing before the code that makes it pass. TRIGGER when the Architect says "tdd" or hands over an approved change to implement with tests. DO NOT TRIGGER to write or fix a test with no implementation to follow; use /write-test.
Installs into .claude/skills of the current project.
Are you the author of Tdd?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/heyjordanparker-tdd)
---
name: tdd
description: Implement an approved change one Capability at a time, each test written and watched failing before the code that makes it pass. TRIGGER when the Architect says "tdd" or hands over an approved change to implement with tests. DO NOT TRIGGER to write or fix a test with no implementation to follow; use /write-test.
---
# TDD
## 1. Use /plan-tests to list the Capabilities and the tests to write
## 2. Take one Capability and write its test with /write-test
## 3. Run that one test and watch it fail
### Read the failure against the test's own check
It fails there, because the app does not do what the sentence says.
IF it passes:
### Remove the code that provides the Capability, run the test again, then put the code back
The app already does it, so this is the only way to see that the test can fail.
IF it fails anywhere else:
### Fix the starting state and run it again
## 4. Write the code
### Write the least code that makes it pass
The expected value does not move.
## 5. Run that one test again
## 6. Repeat from step 2
## 7. Run the whole file once every Capability's test passes
