root-cause-analysis

Identify root causes using 5 Whys, Fishbone, Pareto, and Fault Tree methodologies.

22|2|Updated Nov 22, 2025

Search Tags:#analysis #root-cause #pareto #five-whys #rca #fishbone #fault-tree

Ready to run

npx skills add https://github.com/markpitt/claude-skills --skill root-cause-analysis-markpitt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: root-cause-analysis
Source: https://github.com/markpitt/claude-skills/tree/main/skills/root-cause-analysis
Command: npx skills add https://github.com/markpitt/claude-skills --skill root-cause-analysis-markpitt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you systematically identify root causes using proven RCA methodologies (5 Whys, Fishbone, Pareto, Fault Tree) to move beyond symptoms and craft durable solutions.

Core Features & Use Cases

Phase-based orchestration: problem classification, methodology selection, execution, and verification.
Access to core RCA methodologies and common root causes references.
Worked examples across software, hardware, process, and personal life.
Advanced: barrier analysis and multi-methodology orchestration options for complex problems.

Quick Start

Explain how to apply 5 Whys to a software bug and map a simple fishbone diagram.

Frequently Asked Questions about root-cause-analysis

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

FAQPage Schema

How do I identify the root cause of a problem instead of just treating symptoms?▼

Root-cause analysis uses structured methodologies like 5 Whys, Fishbone diagrams, and Pareto analysis to move beyond surface symptoms and uncover underlying issues. These techniques systematically trace problems back to their origins, enabling durable solutions rather than temporary fixes across software, hardware, processes, and personal domains.

What's the best way to apply 5 Whys and Fishbone diagrams to debugging?▼

5 Whys repeatedly asks 'why' to drill down through layers of causation; Fishbone diagrams map contributing factors across categories like people, process, and environment. Combined, they create a visual evidence trail from symptom to root cause, helping teams document and communicate findings clearly during troubleshooting.

When should I use Pareto analysis or Fault Tree analysis for problem investigation?▼

Pareto analysis prioritizes the vital few root causes responsible for most failures, ideal when multiple factors contribute. Fault Tree analysis works backward from a failure event through logical chains to identify critical paths. Choose Pareto for prioritization and Fault Tree for safety-critical or complex system failures.

Can root-cause analysis work for non-software problems like process failures or personal issues?▼

Yes. RCA methodologies apply across software, hardware, processes, and personal domains. The phase-based approach—problem classification, methodology selection, execution, and verification—remains consistent, allowing teams to debug maintenance issues, performance problems, and operational bottlenecks using the same structured framework.

How do I structure findings from multiple RCA methodologies into a final report?▼

Multi-methodology orchestration combines insights from 5 Whys, Fishbone, Pareto, and Fault Tree into a structured RCA deliverable containing the identified root cause, contributing factors, supporting evidence, and recommended corrective actions for stakeholder review and implementation.