diagnose-issues

Name: diagnose-issues
Availability: InStock
Author: VirtEngine

Orchestrate parallel debug agents to diagnose UAT gaps and update UAT.md with root causes.

17|4|Updated Oct 8, 2021

Search Tags:#automation #planning #debug #diagnose #root-cause #uat

Ready to run

npx skills add https://github.com/virtengine/virtengine --skill diagnose-issues-virtengine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diagnose-issues
Source: https://github.com/virtengine/virtengine/tree/main/.github/skills/diagnose-issues
Command: npx skills add https://github.com/virtengine/virtengine --skill diagnose-issues-virtengine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate parallel debug agents to investigate UAT gaps and find root causes. After UAT finds gaps, spawn one debug agent per gap. Each agent investigates autonomously with symptoms pre-filled from UAT. Collect root causes, update UAT.md gaps with diagnosis, then hand off to plan-phase --gaps with actual diagnoses. Orchestrator stays lean: parse gaps, spawn agents, collect results, update UAT.

Core Features & Use Cases

Diagnose gaps in UAT with parallel agents: spawn an agent for each gap to investigate root causes concurrently.
Artifact collection and UAT updates: record evidence, root cause, and missing actions, and update UAT.md accordingly.
Plan handoff: hand off diagnosed gaps to the plan phase for targeted fixes.

Quick Start

Spawn parallel debug agents to diagnose UAT gaps and update UAT.md with root causes

Frequently Asked Questions about diagnose-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I diagnose multiple UAT gaps concurrently?▼

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.

How do I find the root cause of a UAT gap?▼

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.

How do I collect artifacts during UAT diagnosis?▼

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.

How do I hand off diagnosed UAT gaps to a planning phase?▼

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.

Can I use parallel agents for UAT workflows with multiple defined gaps?▼

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.

What is the best way to automate root cause analysis for UAT gaps?▼

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.