Individual skill

rca-methodology

Detailed guide for Root Cause Analysis (RCA) methodologies. Structured RCA techniques including 5 Whys, Fishbone diagrams, Fault Tree Analysis, change analysis, and a cognitive bias prevention checklist. Use this skill for 'root cause analysis', 'RCA', '5 Whys', 'fishbone', 'Fault Tree', 'cause analysis methodology', 'change analysis', and other incident cause analysis tasks. Enhances the analysis capabilities of root-cause-investigator. Note: timeline reconstruction and remediation planning are outside the scope of this skill.

en/25-incident-postmortem/.claude/skills/rca-methodology/skill.md

Read pinned source

Source commit 8e8d35c6a19166614d1af1df85512266d51121ae

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,324
Repository last updated: Mar 22, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

skill.mdcore · 5,989 bytes

Read excerpt


# RCA Methodology — Root Cause Analysis Methodology Guide

A collection of structured analysis techniques for systematically tracing incident root causes.

## 1. 5 Whys Technique

### Procedure
```
Problem: Payment service was down for 30 minutes.

Why 1: Why did the payment service go down?
-> The DB connection pool was exhausted.

Why 2: Why was the connection pool exhausted?