root-cause-analysis

Identify and document root causes of failures using 5 Whys and fishbone diagrams.

1|Updated May 7, 2026

Search Tags:#problem-solving #root-cause-analysis #process-improvement #incident-management #rca #5-whys #fishbone

Ready to run

npx skills add https://github.com/ChristopherAlphonse/calphonse-skills --skill root-cause-analysis-christopheralphonse

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Root-cause analysis enables teams to identify underlying issues causing incidents and prevent recurrence through structured methodologies.

Core Features & Use Cases

Structured RCA workflow using techniques like The 5 Whys and Fishbone diagrams.
Documentation templates for RCA reports, follow-up plans, and preventative measures.
Collaborative, repeatable process enabling teams to reproduce and verify root causes.

Quick Start

Analyze the latest incident to identify its root cause and plan preventive actions.

Frequently Asked Questions about root-cause-analysis

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

FAQPage Schema

How do I conduct a root cause analysis for an incident or outage?▼

Conduct a root cause analysis by following a structured RCA workflow using the 5 Whys and fishbone diagrams to identify underlying issues, document findings in RCA reports, and track follow-up preventative plans to prevent recurrence.

What is the 5 Whys technique and when should I use it for problem-solving?▼

The 5 Whys is an iterative problem-solving method used to identify the root cause of failures by asking why repeatedly. Use it during incident management to diagnose performance degradations, outages, and process failures across software and operations.

Can I use a fishbone diagram for process improvement and incident management?▼

Yes, you can use a fishbone diagram for process improvement and incident management to visually map and categorize potential causes of failures. It supports a structured RCA workflow to diagnose root causes fast and prevent recurrence across delivered services.

What's the best way to document RCA reports and preventative measures?▼

The best way to document RCA reports and preventative measures is using structured documentation templates within a repeatable RCA workflow. This ensures collaborative verification of root causes and tracks follow-up plans for preventing incident recurrence across software and operations.

Does root cause analysis work for performance degradations and process failures?▼

Yes, root cause analysis works for performance degradations and process failures across software, operations, and delivered services. It identifies and documents underlying issues causing these incidents to plan preventive actions and prevent future recurrence.