diagnose-issues

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

Updated Feb 13, 2026

Search Tags:#automation #testing #debugging #root cause analysis #agent orchestration #uat

Ready to run

npx skills add https://github.com/bhanukushwah/parinaya-os --skill diagnose-issues-bhanukushwah

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of investigating User Acceptance Testing (UAT) failures by spawning parallel debug agents to pinpoint the root cause of each identified gap.

Core Features & Use Cases

Parallel Debugging: Spawns multiple independent agents to investigate different UAT gaps simultaneously, significantly reducing investigation time.
Root Cause Analysis: Focuses agents solely on identifying the underlying reason for a failure, ensuring accurate diagnosis before planning fixes.
Automated Reporting: Updates UAT.md with detailed findings, including root causes, involved files, and debug session paths.
Use Case: After UAT identifies several bugs, this Skill will automatically assign a dedicated agent to each bug to find its exact source code location and the reason for the failure, preparing the team for efficient bug fixing.

Quick Start

Use the diagnose-issues skill to investigate all failed gaps listed in UAT.md.

Frequently Asked Questions about diagnose-issues

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

FAQPage Schema

How do I automate root cause analysis for multiple UAT failures?▼

Automating root cause analysis for UAT failures is done by spawning parallel debug agents that independently investigate each gap, collect evidence, and update UAT.md with specific causes and involved files.

What is the best way to debug several UAT gaps at the same time?▼

The best way to debug several UAT gaps simultaneously is orchestrating parallel debug agents, assigning one dedicated agent per gap to autonomously pinpoint the exact source code location and report the underlying failure reason.

How does parallel agent orchestration work for investigating User Acceptance Testing bugs?▼

Parallel agent orchestration for UAT bugs works by spawning independent debug agents for each failed gap, collecting their diagnoses with evidence, and updating UAT.md to prepare the team for efficient bug fixing.

Can I use automated debugging to find root causes before planning code fixes?▼

Yes, you can use automated debugging to find root causes before planning fixes by spawning agents focused solely on identifying the underlying reason for failure, ensuring accurate diagnosis prior to any repair work.

Does diagnosing UAT issues require specific dependencies or components?▼

Diagnosing UAT issues requires no external dependencies or components, relying on autonomous debug agents that investigate failed gaps and document their findings with evidence directly into UAT.md.

Why should I use parallel debug agents instead of manually investigating UAT gaps?▼

You should use parallel debug agents instead of manual investigation to significantly reduce the time spent finding failure sources, as each agent autonomously reports specific causes with evidence for accurate diagnosis.