Generate category-specific root-cause hypotheses and render fishbone HTML with JSON output.
npx skills add https://github.com/koseki2580/skills --skill fishbone-analysis
Please help me install this Agent Skill. Skill: fishbone-analysis Source: https://github.com/koseki2580/skills/tree/main/skills/fishbone-analysis Command: npx skills add https://github.com/koseki2580/skills --skill fishbone-analysis
Fishbone analysis helps you diagnose an unclear or scattered failure by widening the cause space across independent perspectives before you converge on a plausible root cause.
Use fishbone-analysis to enumerate potential causes for a bug report when the cause is unclear and spans multiple plausible areas in the system.
High-intent search queries and answers about installing and using this skill.
Root cause analysis for an unclear bug requires widening the cause space. You enumerate 3–7 cause hypotheses per fixed category across isolated perspectives, preventing bias by explicitly forgetting earlier categories before converging on the actual failure.
A fishbone diagram in incident triage visually maps root-cause hypotheses from multiple perspectives. It generates category-specific candidates, consolidates duplicates, and renders an interactive HTML artifact to track adopted, held, or rejected causes.
To enumerate debugging hypotheses systematically, generate 3–7 cause candidates per fixed preset category. Consolidate duplicate root-cause candidates and surface mutually exclusive pairs after all categories are covered to prepare for downstream verification.
Use multi-perspective root cause analysis when causes are unclear, scattered, or after standard systematic debugging fails multiple times. It widens the failure space across independent perspectives before convergence, making it ideal for complex incident investigation and redesign preparation.
Yes, incident triage results export to a machine-readable JSON state and an interactive HTML fishbone artifact. The JSON output enables downstream verification handoff, while a copyable follow-up prompt transfers adopted hypotheses directly to systematic debugging.
tonone-aiDiagnose production incidents by analyzing logs, metrics, and traces to identify root cause.
ArrowsHQGenerate follow-up emails, CRM notes, and resources from verifiable call data.
dev-khoiFrame ambiguous questions into structured, testable hypothesis trees.
Im5tuIdentify root causes of software bugs through a four-phase debugging process.
