aidd-tdd

You can automate the test-driven development cycle by orchestrating the red-green-refactor process, which coordinates specialized subagents to write tests, implement code, and verify outcomes automatically. It enforces TDD principles throughout software implementation.

The best way to enforce the red-green-refactor methodology is to use an automated TDD orchestration process that manages the cycle, runs tests to verify code correctness at each stage, and delegates tasks to specialized subagents for test writing and implementation.

You do not need a specific test runner, but the automated TDD workflow requires detection of your project's existing test runners to execute tests properly. It adheres to your project's scope and test selection constraints during the red-green-refactor cycle.

Yes, you can use automated TDD orchestration for both software implementation and bug fixing. It manages the red-green-refactor process for any code changes by coordinating test writing and code implementation while verifying test outcomes at each stage.

Automated test execution during the refactoring phase works by running tests to verify code correctness after changes are made. The TDD cycle orchestrator coordinates specialized subagents to implement code, then executes tests to ensure adherence to TDD principles before proceeding.

You should use a TDD orchestrator because it enforces disciplined adherence to TDD principles by managing the entire red-green-refactor process automatically. It coordinates specialized subagents for test writing and code implementation, ensuring robust and well-tested code without manual workflow overhead.