tdd

# Test-Driven Development (TDD) Guides you through the complete TDD workflow with Red-Green-Refactor cycle. ## Usage `/tdd <ACTION> [ARGUMENTS]` ## Actions - **start <FEATURE>** - Initialize TDD session for a feature - **red <TEST_NAME>** - Create failing test (Red phase) - **green** - Run tests and implement code (Green phase) - **refactor** - Guide refactoring process (Refactor phase) - **cycle <FEATURE>** - Run complete Red-Green-Refactor cycle - **watch** - Start test watcher for continuous feedback - **status** - Show current test status and next steps ## TDD Principles ### The Red-Green-Refactor Cycle 1. **Red**: Write a failing test that defines desired behavior 2. **Green**: Write minimal code to make the test pass 3. **Refactor**: Improve code quality while keeping tests green ### Best Practices - Write tests first - Tests define the interface and behavior - Small steps - Make tiny, incremental changes - Fast feedback - Run tests frequently for immediate validation - Clean code - Refactor regularly to maintain quality - One concept per test - Keep tests focused and atomic - AAA Pattern - Structure tests as Arrange, Act, Assert - Black-box testing - Test only public methods and behavior, not implementation details ## Process ### For "start <FEATURE>": 1. Initialize TDD session for the feature 2. Create or identify target source file 3. Create corresponding test file if it doesn't exist 4. Explain the feature requirements and acceptance criteria ### For "...