tdd-red

Automating failing test creation for Test-Driven Development involves scanning your PLAN.md file to identify the next unmarked task and generating a corresponding failing test. This enforces TDD discipline by defining behavior upfront before implementation begins.

The RED phase in Test-Driven Development is the initial step of writing a failing test that defines desired behavior before any implementation. It ensures tests are written first, guiding subsequent development steps to maintain strict TDD discipline.

Generating a failing test from PLAN.md requires identifying the next unmarked item in the file and automatically writing a test for it. This ensures the test fails initially, confirming the behavior is properly defined before writing the implementation code.

Yes, automated TDD test generation can enforce writing tests in Korean (ko-KR). This ensures the failing tests for the RED phase are consistently generated in the specified language while maintaining adherence to the development workflow.

Yes, you need a PLAN.md file to start the TDD RED phase because the automation identifies the next unmarked task within it. This file drives the workflow by providing the task context needed to generate the corresponding failing test.

You should use an automated RED phase tool when starting a new feature to ensure a failing test is written before implementation. It maintains TDD discipline by automatically defining behavior upfront and confirming the test fails before proceeding.