Automate root cause analysis with 5-whys and fishbone categorization.
npx skills add https://github.com/sebdenes/ExtendedRCA --skill extended-rca
Please help me install this Agent Skill. Skill: extended-rca Source: https://github.com/sebdenes/ExtendedRCA/tree/main/skills/extended-rca Command: npx skills add https://github.com/sebdenes/ExtendedRCA --skill extended-rca
The Extended Root Cause Analysis skill addresses the need for deep, structured post-incident analyses that go beyond attributing blame to reveal trigger, proximate, contributing, and systemic causes, with explicit corrective actions and a verifiable self-check.
Provide the incident details (summary, timeline, and logs) and run the skill to generate an extended RCA with the default mode.
High-intent search queries and answers about installing and using this skill.
A deep root cause analysis for software incidents requires structured techniques like 5-Whys and fishbone categorization to move past human actions and reveal trigger, proximate, contributing, and systemic causes. This approach ensures you uncover underlying system flaws rather than stopping at individual mistakes, producing a blameless and auditable RCA artifact.
The best way to structure a postmortem with actionable corrective actions is to use a rigorous taxonomy that categorizes steps into Prevent, Detect, Mitigate, and Respond. Layering findings across these categories ensures your RCA template includes explicit corrective actions that address each causal layer, making the artifact verifiable and complete.
To use a fishbone diagram for RCA hypothesis generation, you categorize potential causes across six domains: People, Process, Code, Infrastructure, Data, and External dependencies. This structured categorization ensures your root cause analysis explores all relevant system areas comprehensively rather than focusing narrowly on a single failure point.
To run an automated RCA after an incident is resolved, you provide the incident details, timeline, and logs to generate an extended RCA artifact. The process applies 5-Whys chains and layered findings automatically, producing a structured postmortem document with explicit actions and a self-check for completeness.
Yes, this root cause analysis approach works for complex incidents because it separates findings into four distinct causal layers: Trigger, Proximate, Contributing, and Systemic. By mapping hypotheses across fishbone categories and applying 5-Whys, it handles multi-factor incidents by isolating distinct causes and assigning specific corrective actions to each.
To ensure your post-incident RCA is blameless and auditable, you apply a self-check driven artifact template that verifies completeness and avoids attributing blame. The structured RCA process uses explicit corrective actions and layered findings, creating a standardized, verifiable document that focuses on systemic improvements.
lugassawanGuide teams in producing blameless postmortems with timelines, root causes, and action items.
45black-LimitedIdentify and document root causes using Ishikawa categories and Five Whys.
yongwoonGenerate structured incident postmortems with timeline reconstruction and 5 Whys analysis.
Gami19Plan incident response workflows with SLO/SLI design and ICS-based flows.
