qa-tdd-orchestrate

You can coordinate TDD cycles across context-isolated agents by using an outer-loop orchestration workflow that manages RED/GREEN/REFACTOR phases. It enforces strict isolation by using artifact files like handoff-red.json and handoff-green.json to gate progress between phases.

The best way to prevent context leakage during TDD handoffs is to use template-driven prompts and artifact-only handoffs. This approach enforces clean boundaries between agents, ensuring internal reasoning does not cross phase transitions and test outcomes remain reproducible.

To start an automated RED/GREEN/REFACTOR workflow, you trigger the orchestration process by providing a feature description and explicit acceptance criteria. The outer-loop coordinator then uses these inputs to guide the sub-agents through each testing phase.

Yes, you need explicit acceptance criteria to use context-isolated TDD orchestration. The workflow relies on these criteria to gate progress and validate results during the outer-loop coordination of the RED, GREEN, and REFACTOR cycles.

Internal reasoning affects reproducible test outcomes when context is not strictly isolated between phases. By implementing context-isolated sub-agents and artifact-only handoffs, you prevent cross-talk and ensure that prior reasoning does not influence subsequent test results.

Yes, you can trace phase changes when orchestrating context-isolated TDD. The workflow generates auditable artifact files such as handoff-red.json and handoff-green.json at each phase boundary, providing a clear record of progress and changes.