tddlisted

Test-driven work in two modes. Default: real Test-Driven Development — red-green-refactor, one failing test at a time, used while implementing features (and by the work skill). With --debug: test-first debugging — generate all plausible root-cause hypotheses, write tests to validate each before touching production code, fix based on which tests fail, then sweep the codebase for the same pattern. Use for 'tdd', 'test-driven', 'write the test first', implementing with tests leading — and with --debug whenever the user reports a bug, unexpected behavior, or failed fix attempts and the root cause is unclear.
supermodo/skills · ★ 0 · Testing & QA · score 70

Install: claude install-skill supermodo/skills

# tdd — Test-Driven Development & Test-First Debugging > **Requires:** the sibling `protocols` skill (shared protocol masters); uses `skills.config.json` when present. Missing protocols → tell the user to install the full supermodo package. > **Project rules.** Read `.supermodo/rules/tdd.md` if present, plus any > `.supermodo/rules/INDEX.md` rows naming `tdd` — that file IS this project's > tdd process and replaces the defaults below wherever they overlap. Contract: > `../protocols/references/rules.md`. Never in that file, so never switchable off: > watching each test fail for the right reason first, no production code without a failing test demanding it, and the zero-trace grep gate. Two modes, one discipline: tests lead, production code follows. **Command preflight.** With `skills.config.json` present, validate it per `../protocols/references/config.md` and run tests ONLY via the configured tiers (`../protocols/references/tooling.md`): `commands.test` (fallback `commands.testUnit`) inside the red-green loop — the fast tier, after every change — `commands.testUnit` as the completion gate, `commands.testAll` for full-suite checks, `commands.coverage` against `coverage.target` for coverage gates. A needed tier that is missing → say so and point at `config --edit commands`; and when a configured project has NEITHER `test` nor `testUnit`, HALT before touching production code — a test-first workflow with no way to run tests is impossible, not degradable. Never invent a comman