Root Cause Analysis

Five Whys, fishbone diagrams, identifying systemic causes not just symptoms.

48 stars 10 forksOther Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill root-cause-analysis
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/debugging/skills/root-cause-analysis ~/.claude/skills/root-cause-analysis

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Root Cause Analysis

Finding the true cause of problems, not just surface symptoms.

## Context

You are helping identify root causes. Use 5 Whys or fishbone to dig deeper.

## Domain Context

- **5 Whys**: Ask "why" 5 times until you reach systemic cause
- **Fishbone**: Visual; categorize causes by area (code, data, infra)
- **Systemic vs. Symptomatic**: Symptom = bug manifested; root cause = why it was possible
- **Preventable**: Good RCA identifies what would have prevented it

## Instructions

1. **Identify Symptom**: What failed? What did users see?
2. **Ask Why**: Why did that happen?
3. **Repeat**: Ask why 4 more times; each answer becomes new "why"
4. **Categorize**: Use fishbone: Code, Data, Infrastructure, People?
5. **Identify Root**: Most fundamental cause; fixing it prevents recurrence
6. **Verify**: Would fixing root cause prevent this bug?

## Anti-Patterns

- Stopping at first cause ("typo in condition"); dig deeper
- Blame-driven RCA (focusing on who made the mistake); focus on prevention
- RCA on every bug; only on critical/recurring issues
- Ignoring environmental factors (load, hardware, timing)
- RCA without action items; analysis without prevention is waste

## Further Reading

- The Art of Systems Thinking (Daniel H. Kim)
- Blameless postmortems from Google SRE
Read the full skill on GitHub

Details

Skill name
root-cause-analysis
Path
engineer/debugging/skills/root-cause-analysis/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Root Cause Analysis skill do?

Five Whys, fishbone diagrams, identifying systemic causes not just symptoms.

How do I install the Root Cause Analysis skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Root Cause Analysis popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.