diagnose-issues

To diagnose multiple UAT gaps concurrently, spawn parallel debug agents to investigate each gap independently. The orchestration reads gaps from UAT.md, assigns one agent per gap, and aggregates root causes and artifacts concurrently.

Finding the root cause of a UAT gap involves spawning an autonomous debug agent per gap. Each agent investigates pre-filled symptoms from UAT, collects evidence, and documents the root cause directly into UAT.md.

Collect artifacts during UAT diagnosis by assigning debug agents to autonomously investigate each gap. Agents record evidence and missing actions, then update UAT.md with the collected artifacts and root causes.

Hand off diagnosed UAT gaps to the planning phase by updating UAT.md with actual diagnoses and artifacts. The orchestrator aggregates results and passes the documented root causes to plan-phase --gaps for targeted fixes.

Yes, you can use parallel agents for UAT workflows with multiple defined gaps. The orchestrator applies to workflows where multiple gaps require concurrent investigation, artifact collection, and documentation.

The best way to automate root cause analysis for UAT gaps is orchestrating parallel debug agents. The orchestrator parses gaps, spawns agents autonomously, collects results, and updates UAT.md without manual intervention.