tdd-go

Automating the TDD workflow requires orchestrating the RED, GREEN, and REFACTOR phases to write failing tests, implement minimum code, and refactor. This Skill executes that cycle by reading a PLAN.md file, writing one test at a time, and applying the smallest possible changes to pass.

The automated TDD cycle handles the RED, GREEN, and REFACTOR phases by identifying the next test, writing a failing test, implementing the minimum code to pass, and optionally refactoring. It ensures strict adherence to TDD principles by processing one test at a time from your PLAN.md file.

Yes, you can use a test plan to drive automated test generation by placing your planned tests in a PLAN.md file. The Skill automatically finds and marks the next test from this file, ensuring the automated TDD cycle systematically works through your planned test cases one by one.

The best way to enforce strict TDD principles is to automate the RED, GREEN, and REFACTOR loop while restricting code changes to the smallest possible increments. This Skill guarantees adherence by writing one test at a time and implementing only the minimum code required to pass.

Yes, you need a PLAN.md file to start the automated TDD cycle because the Skill uses it to identify and mark the next test. This file drives the workflow, allowing the system to automatically select the next failing test to write and implement.

You should not use an automated test-driven development workflow when your project lacks a structured PLAN.md file or when exploratory coding requires flexible, rapid changes outside strict TDD principles. The automation relies on predefined test plans and making the smallest possible changes sequentially.