Test Driven Development

Strict RED-GREEN-REFACTOR cycle enforcement. Tests are never skipped or deferred. Run mode only, never watch mode. Exit code evidence mandatory.

a5c-ai Updated 1.7k repo stars

File contents

Non-Negotiable Rules

  • Always use run mode (CI=true npm test or --run flag)
  • NEVER use watch mode (prevents hanging processes)
  • Use timeout guards (timeout 60s) as backup
  • Record exit codes as evidence at each phase
  • If tests fail 3 consecutive times in GREEN, report failure status
  • Never skip RED phase (failing test must exist before implementation)
  • Never defer tests to "later" -- TDD means tests first

Scope Discipline

  • If implementation requires >3 file changes, flag for scope review
  • Architectural choices require user approval unless pre-approved in plan
  • New dependencies require user approval

When to Use

  • Every feature implementation in BUILD workflow
  • Every bug fix in DEBUG workflow (regression test)

Agents Used

  • component-builder (primary consumer)
  • bug-investigator (regression tests)

a5c-ai/babysitter/tree/main/library/methodologies/cc10x/skills/test-driven-development commit 6a84c34351

Frequently asked questions

npx skillmds@latest add a5c-ai/test-driven-development