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.

A situation 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.
test-driven-development (superpowers). test-driven-development (superpowers) is the practice that encourages stating expected behavior first and making minimal, incremental changes that can be refactored—helping keep edits small and reversible. The other skills supply tests, data, or browser automation, but TDD is the working habit that shapes how you approach new work.

4 scenarios in the bank answer to test-driven-development (superpowers). The rest are in the game.

Skills it gets confused with

These share a family with test-driven-development (superpowers), which is another way of saying they are the ones you might reach for by mistake.

Knowing what test-driven-development (superpowers) does is the easy half. Telling it apart from the others under time pressure is the game.

Today's session

test-driven-development (superpowers) is part of obra/superpowers. Licence: MIT. The description above was written for this game, not taken from the skill.

← All skills