claude-settings/commands/tdd-next.md

TDD Next Test Cycle

Start the next TDD Ping-Pong cycle by proposing and writing a failing test.

Workflow

1. Ask for feature specification:

   • What exact behavior should be tested?
   • What are the acceptance criteria?
   • Are there any edge cases to skip for now?

2. Propose the next single test:

   • Describe what behavior will be tested
   • Explain why this is the next logical test
   • Confirm with user before proceeding

3. Write the failing test (RED phase):

   • Write ONE failing test for the smallest increment
   • Test behavior, NOT implementation details
   • Use appropriate test framework for the language
   • Ensure test fails for the right reason

4. Commit the test:

   git add <test-file>
   git commit -m "test: RED - <behavior being tested>"
   

5. Hand off to developer:

   • Developer implements minimum code to make test pass
   • Developer commits with: git commit -m "feat: GREEN - <feature>"

6. Refactoring cycles:

   • Review tests for improvements (extract fixtures, remove duplication)
   • Review implementation for improvements (SOLID, DRY, naming)
   • Each refactoring gets its own commit with REFACTOR phase marker

7. Feature completion:

   • When feature is complete, update CLAUDE.md
   • Commit: git commit -m "docs: COMPLETE - <feature name>"
   • Tag: git tag -a "feature-<name>-v1" -m "<description>"

Remember

• ONE test at a time
• Test behavior, not implementation
• Stay minimal
• Always confirm with user before writing test