tdd-enforcement ยท diff
git:20260325.a6b3a88 to git:20260507.56f011d
62 added, 59 removed. Audit A to A.
- ---
- name: tdd-enforcement
- description: Red-Green-Refactor TDD methodology with mandatory failing tests, minimal implementation, quality refactoring, and 80% coverage gating.
- allowed-tools: Read, Write, Edit, Bash, Grep, Glob
- ---
-
- # TDD Enforcement
-
- ## Overview
-
- Strict test-driven development enforcement adapted from the Everything Claude Code methodology. Mandates the Red-Green-Refactor cycle with evidence-based verification at each phase.
-
- ## TDD Process
-
- ### 1. RED Phase - Write Failing Tests
- - Write tests that define expected behavior
- - Tests MUST fail (exit code 1)
- - Use CI=true or --run flag, never watch mode
- - Apply timeout guards (60s) to prevent hanging
- - Record exit code as evidence
-
- ### 2. GREEN Phase - Minimal Implementation
- - Write the minimal code to make tests pass
- - Do NOT add features not covered by tests
- - Do NOT optimize prematurely
- - Tests MUST pass (exit code 0)
- - Record exit code as evidence
-
- ### 3. REFACTOR Phase - Quality Improvement
- - Apply SOLID principles and clean code patterns
- - Improve naming, reduce coupling
- - Remove duplication
- - Run tests after EACH refactoring step
- - Tests MUST remain passing (exit code 0)
-
- ### 4. Coverage Gate
- - Measure coverage: statements, branches, functions, lines
- - Minimum 80% overall coverage required
- - Iterate: write additional tests for gaps until threshold met
- - Maximum 3 convergence iterations
-
- ## Rules
-
- - Never skip the RED phase
- - Never accept GREEN without exit code 0
- - Never use watch mode in CI
- - Always record evidence (exit codes, coverage numbers)
- - Enforce 80% coverage threshold
-
- ## When to Use
-
- - All code implementation tasks
- - Feature development
- - Bug fixes (write regression test first)
-
- ## Agents Used
-
- - `tdd-guide` (primary consumer)
- - `code-reviewer` (validates test quality)
+ ---
+ name: tdd-enforcement
+ description: Red-Green-Refactor TDD methodology with mandatory failing tests, minimal implementation, quality refactoring, and 80% coverage gating.
+ allowed-tools: Read, Write, Edit, Bash, Grep, Glob
+ graph:
+ domains: [domain:software-engineering]
+
+ ---
+
+ # TDD Enforcement
+
+ ## Overview
+
+ Strict test-driven development enforcement adapted from the Everything Claude Code methodology. Mandates the Red-Green-Refactor cycle with evidence-based verification at each phase.
+
+ ## TDD Process
+
+ ### 1. RED Phase - Write Failing Tests
+ - Write tests that define expected behavior
+ - Tests MUST fail (exit code 1)
+ - Use CI=true or --run flag, never watch mode
+ - Apply timeout guards (60s) to prevent hanging
+ - Record exit code as evidence
+
+ ### 2. GREEN Phase - Minimal Implementation
+ - Write the minimal code to make tests pass
+ - Do NOT add features not covered by tests
+ - Do NOT optimize prematurely
+ - Tests MUST pass (exit code 0)
+ - Record exit code as evidence
+
+ ### 3. REFACTOR Phase - Quality Improvement
+ - Apply SOLID principles and clean code patterns
+ - Improve naming, reduce coupling
+ - Remove duplication
+ - Run tests after EACH refactoring step
+ - Tests MUST remain passing (exit code 0)
+
+ ### 4. Coverage Gate
+ - Measure coverage: statements, branches, functions, lines
+ - Minimum 80% overall coverage required
+ - Iterate: write additional tests for gaps until threshold met
+ - Maximum 3 convergence iterations
+
+ ## Rules
+
+ - Never skip the RED phase
+ - Never accept GREEN without exit code 0
+ - Never use watch mode in CI
+ - Always record evidence (exit codes, coverage numbers)
+ - Enforce 80% coverage threshold
+
+ ## When to Use
+
+ - All code implementation tasks
+ - Feature development
+ - Bug fixes (write regression test first)
+
+ ## Agents Used
+
+ - `tdd-guide` (primary consumer)
+ - `code-reviewer` (validates test quality)