tdd-feature

TDD Feature Implementation

Implement a new feature using strict Test-Driven Development: $ARGUMENTS

Parse Arguments

Extract from arguments:

• Feature description: The main description (required)
• --strict / --standard / --relaxed: Override strictness mode (optional)
• --no-refactor: Skip refactor phase after green (optional)
• --file : Target specific file for tests/implementation (optional)
• --plan: Force planning mode (require approval before test and implementation)
• --skip-plan: Skip planning entirely, execute directly

Pre-Flight Checks

1. Load settings: Read .claude/tdd-dev.local.md if exists
2. Determine strictness: Use flag override > settings > default (strict)
3. Detect test command: From settings or auto-detect from project files
4. Identify test location: Find appropriate test file or create new one
5. Reset TDD cycle state: Create/update .claude/.tdd-cycle-state to start fresh RED phase:

   {"phase": "red", "testFilesWritten": [], "testsRan": false, "testsFailed": false}
   

   This ensures hooks enforce "write test first" for this new feature.

Plan Mode Decision

Determine planning behavior based on flags:

1. If --skip-plan flag: Skip all planning, proceed directly to TDD loop
2. If --plan flag: Force planning before both RED and GREEN phases
3. If neither flag (default): Ask user using AskUserQuestion:
   • "Would you like to review and approve the test plan before I write tests?"
   • Options: "Yes, show me the plan" / "No, proceed directly"
   • Store response for consistent behavior in GREEN phase

Test Planning Phase (unless --skip-plan)

If planning is enabled (via --plan flag or user choice):

1. Enter plan mode: Use EnterPlanMode tool
2. Analyze requirements:
   • What behaviors need testing for this feature?
   • What edge cases should be covered?
   • What test structure fits the project best?
3. Write test plan to plan file including:
   • Test file location
   • Test cases to write (describe/it structure)
   • Expected assertions for each test
   • Mocking strategy if external dependencies involved
4. Exit plan mode: Wait for user approval via ExitPlanMode
5. Proceed to RED phase only after approval