rca-methodology

Identify and analyze incident root causes using 5 Whys, Fishbone, and Fault Tree Analysis.

1|Updated Nov 27, 2025

Search Tags:#postmortem #root-cause-analysis #incident-management #rca #5-whys #fishbone #fta

Ready to run

npx skills add https://github.com/buenhyden/hy-home.k8s --skill rca-methodology

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rca-methodology
Source: https://github.com/buenhyden/hy-home.k8s/tree/main/.agents/skills/rca-methodology
Command: npx skills add https://github.com/buenhyden/hy-home.k8s --skill rca-methodology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides structured, repeatable methods for root-cause analysis to uncover underlying causes of incidents, reduce recurrence, and improve incident response quality.

Core Features & Use Cases

5 Whys, Fishbone (Ishikawa), Fault Tree Analysis, Change Analysis, and cognitive bias checks as RCA tools.
Timeline reconstruction guidance for incident review and remediation planning.
Use Case: When a service experiences outages or performance issues, apply techniques to identify root causes and contributing factors, then document action items.

Quick Start

Run a structured RCA session on a recent incident and capture the findings in a centralized Root Cause Analysis document.

Frequently Asked Questions about rca-methodology

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

FAQPage Schema

How do I conduct a root-cause analysis for a service outage in distributed systems?▼

To conduct a root-cause analysis for distributed systems, apply structured techniques like 5 Whys and Fault Tree Analysis during post-incident reviews to identify contributing factors and capture learning opportunities.

What is the best way to structure a postmortem using 5 Whys and Fishbone diagrams?▼

The best way to structure a postmortem is by applying structured RCA templates that guide you through 5 Whys, Fishbone diagrams, and cognitive bias checks, outputting a standardized document of findings.

When should I use Fault Tree Analysis instead of 5 Whys for incident management?▼

Use Fault Tree Analysis instead of 5 Whys when investigating complex incidents with multiple contributing factors across distributed systems, as it handles branching failure paths better than linear questioning.

Can I use this RCA methodology to identify contributing factors in DevOps workflows?▼

Yes, you can use this RCA methodology in DevOps workflows to identify contributing factors during post-incident reviews across distributed systems, providing structured techniques and templates for remediation planning.

Does root-cause analysis prevent cognitive bias during post-incident reviews?▼

Root-cause analysis reduces cognitive bias during post-incident reviews by applying explicit bias checks alongside structured methodologies like Change Analysis and 5 Whys to uncover true underlying causes.