cdd-executor

You can automate the Red-Green-Refactor TDD cycle by activating an executor that reads plan.md and spec.md, generates tests for the first unchecked item, runs them, and updates the plan upon completion.

The best way to execute test-driven development tasks autonomously is using a tool that targets the first unchecked task in plan.md, writes failing tests, implements code to pass them, and refactors while adhering to spec.md EARS requirements.

Yes, you can use a TDD executor with existing plan.md and spec.md documents. It reads these files directly to identify the next unchecked task and ensures the generated tests adhere to the established EARS requirements.

No, you do not need external testing tools beyond your local test environment. The executor autonomously generates tests, runs them locally, and updates the plan.md file without relying on external dependencies.

An automated TDD loop updates plan management files by using a recite command to mark the targeted item as complete in plan.md, leaving the system prepared to automatically tackle the next unchecked task.