Skill
Test Driven Development
superpowers
The discipline of writing a failing test before any production code: watch it fail for the right reason, add just enough code to make it pass, then refactor. It governs the ORDER in which you write code, not which framework runs it - it is a way of working, not a test runner or a coverage tool.
Situations it fits
Your team wants a lightweight rule to make new work safer: write something that forces you to think about the desired behavior before coding changes and keeps your edits tiny and reversible.Your team has a ritual: before adding any feature, they codify the expected behavior as a short executable check, see it fail under CI, then implement the tiniest change to make the check satisfied and clean up the code. Which practice are they following?4 scenarios in the bank answer to Test Driven Development. The rest are in the game.
Skills it gets confused with
These share a family with Test Driven Development, which is another way of saying they are the ones you might reach for by mistake.
- AI Test GenerationTurns a spec, user story, code diff, or API schema into brand-new test code through a…
- Playwright CLIDrives a real browser one command at a time - open a page, click and type by element…
- Test Data GenerationManufactures realistic, consistent fixtures and seed data with factories and fake-data…
Knowing what Test Driven Development does is the easy half. Telling it apart from the others under time pressure is the game.
Today's sessionTest Driven Development is part of obra/superpowers. Licence: MIT. The description above was written for this game, not taken from the skill.