triage

Run five parallel hypotheses to identify root causes and deliver ranked reports.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/sukeun1997/claude-config --skill triage-sukeun1997
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/sukeun1997/claude-config/tree/main/skills/triage
Command: npx skills add https://github.com/sukeun1997/claude-config --skill triage-sukeun1997

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill accelerates bug diagnosis by running five parallel hypotheses and delivering a ranked root-cause report, eliminating the guesswork when symptoms are present but the root cause is unknown or after repeated failed fixes.

Core Features & Use Cases

  • Parallel fan-out diagnosis: five sub-agents investigate different hypothesis classes concurrently.
  • Judge ranking: a reviewer synthesizes reports into a prioritized root cause with confidence levels.
  • Phase-driven workflow: symptom capture, parallel diagnosis, judge, user approval gate, and optional fix dispatch.
  • Evidence-based reports: each hypothesis outputs concrete file:line citations to support conclusions.

Quick Start

Provide symptom details with /triage, and the system will generate five parallel hypothesis reports and a ranked root-cause verdict.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I find a software bug root cause when multiple fixes have failed?

Bug triage identifies root causes by running five parallel hypotheses across type/mismatch, race conditions, data drift, environment, and upstream changes, then delivering a ranked report with evidence-backed file:line citations to resolve persistent software debugging failures.

What is parallel hypothesis diagnosis for software debugging?

Parallel hypothesis diagnosis is a root-cause-analysis technique where five sub-agents investigate different bug hypothesis classes concurrently. A judge synthesizes their reports into a prioritized root cause with confidence levels, eliminating guesswork when symptoms are known but causes are not.

How do I start a bug triage workflow with known symptoms?

Start bug triage by providing symptom details to trigger a phased workflow: symptom capture, parallel diagnosis, judge ranking, user approval gate, and optional fix dispatch. The system generates five parallel hypothesis reports and a formal ranked root-cause verdict.

What's the best way to diagnose race conditions and data drift bugs?

Diagnose race conditions and data drift using a five-hypothesis bug triage workflow that investigates these specific classes concurrently alongside type/mismatches, environment issues, and upstream changes, providing evidence citations and a formal verdict to support gated code changes.

Do I need specific dependencies to run parallel bug triage?

No dependencies are required to run the parallel bug triage workflow. The Skill operates independently to run five concurrent sub-agents for root-cause-analysis, requiring only your symptom details to initiate the phased diagnosis and ranked report generation.

When should I avoid using a five-hypothesis bug triage approach?

Avoid five-hypothesis bug triage when the root cause is already established or for trivial bugs requiring immediate fixes. This parallel diagnosis approach is designed for complex cases where symptoms are known but underlying causes remain unclear after repeated failed attempts.