tdd
Installation
SKILL.md
Test-Driven Development
Write each new behavior's test before that behavior exists and see it fail first. Several tests may come before one implementation that makes them pass; work one test at a time only when the user asks for that or for red-green-refactor.
Read GLOSSARY.md, then use docs/decisions/README.md to load only the decision
subjects relevant to the behavior under test. If code, spec, and a decision
contract conflict at the decision level, surface the conflict instead of
silently choosing one. Use current terms in test names and public interfaces.