claudekit/.claude/commands/tdd.md

/tdd - Test-Driven Development Workflow

Purpose

Start a TDD workflow: write failing tests first, then implement to make them pass.

Usage

/tdd [feature or function description]

---

Start TDD workflow for: $ARGUMENTS

Workflow

Phase 1: Red - Write Failing Tests

1. Understand Requirements

   • What should the code do?
   • What are the inputs/outputs?
   • What edge cases exist?

2. Write Tests First

   def test_feature_does_expected_thing():
       result = feature("input")
       assert result == "expected"
   

3. Run Tests (Expect Failure)

   pytest -v  # Should fail
   

Phase 2: Green - Make Tests Pass

1. Implement Minimal Code

   • Just enough to pass tests
   • No premature optimization

2. Run Tests (Expect Success)

   pytest -v  # Should pass
   

Phase 3: Refactor

1. Improve Code Quality

   • Clean up implementation
   • Remove duplication
   • Improve naming

2. Run Tests (Ensure Still Passing)

   pytest -v  # Should still pass
   

Phase 4: Repeat

Add more test cases and repeat the cycle.

TDD Best Practices

• Write one test at a time
• Tests should be specific and focused
• Keep the red-green-refactor cycle short
• Commit after each green phase

Output

## TDD Session: [Feature]

### Tests Written
1. `test_basic_functionality` - [description]
2. `test_edge_case` - [description]

### Implementation
`src/feature.py` - [description]

### Cycle Summary
- Red: 3 tests written
- Green: All passing
- Refactor: Extracted helper function