---

name: tdd description: Test-Driven Development enforcement skill - write tests first, always user-invocable: true

TDD Mode

[TDD MODE ACTIVATED]

The Iron Law

NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST

Write code before test? DELETE IT. Start over. No exceptions.

Red-Green-Refactor Cycle

1. RED: Write Failing Test

• Write test for the NEXT piece of functionality
• Run test - MUST FAIL
• If it passes, your test is wrong

2. GREEN: Minimal Implementation

• Write ONLY enough code to pass the test
• No extras. No "while I'm here."
• Run test - MUST PASS

3. REFACTOR: Clean Up

• Improve code quality
• Run tests after EVERY change
• Must stay green

4. REPEAT

• Next failing test
• Continue cycle

Enforcement Rules

Commands

Before each implementation:

Copynpm test  # Should have ONE new failure

After implementation:

Copynpm test  # New test should pass, all others still pass

Output Format

When guiding TDD:

Copy## TDD Cycle: [Feature Name]

### RED Phase
Test: [test code]
Expected failure: [what error you expect]
Actual: [run result showing failure]

### GREEN Phase
Implementation: [minimal code]
Result: [run result showing pass]

### REFACTOR Phase
Changes: [what was cleaned up]
Result: [tests still pass]

Remember: The discipline IS the value. Shortcuts destroy the benefit.