dispatching-incremental-tdd

To enforce one test at a time during TDD, dispatch an incremental TDD agent that strictly manages each test cycle through RED-GREEN-REFACTOR phases, preventing test batching and ensuring incremental design discovery.

Writing multiple tests at once undermines TDD by batching implementation, which bypasses incremental design discovery and reduces the discipline needed to properly refactor code per individual test case.

The best way to maintain RED-GREEN-REFACTOR discipline is to use an automated agent that enforces a strict one-test-at-a-time cycle, guiding each phase individually to ensure robust API creation and component building.

Yes, you can use incremental TDD for building new APIs and complex components. It applies a strict one-test-at-a-time methodology to new functionality, ensuring each cycle is individually implemented and refactored.

To dispatch an incremental TDD agent for a user authentication feature, use the Task tool with the subagent type and provide the feature context, implementation goal, and scope to enforce the one-test-at-a-time cycle.