RootCauseAnalysis

Run FiveWhys, Fishbone, Postmortem, FaultTree, and Kepner-Tregoe analyses to identify actionable contributing factors.

Updated Aug 23, 2026

Search Tags:#root cause #postmortem #incident analysis #blameless #operational excellence #fault tree

Ready to run

npx skills add https://github.com/julianobarbosa/.claude --skill rootcauseanalysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: RootCauseAnalysis
Source: https://github.com/julianobarbosa/.claude/tree/main/skills/RootCauseAnalysis
Command: npx skills add https://github.com/julianobarbosa/.claude --skill rootcauseanalysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It helps teams replace shallow “because X happened” explanations with actionable contributing factors and systemic fixes that prevent recurrence.

Core Features & Use Cases

Incident/defect investigation workflows: run FiveWhys for causal chains, Fishbone for category mapping, Postmortem as a blameless wrapper, FaultTree for safety-critical Boolean logic, and Kepner-Tregoe for IS/IS-NOT deviation analysis.
Blameless, evidence-structured reasoning: builds a timeline first, resists hindsight/confirmation bias, and frames failures as system conditions (Swiss Cheese) rather than individual mistakes.
Actionability stop condition: identifies the deepest cause where you can implement a change within organizational control, producing concrete corrective actions with verification guidance.

Quick Start

Ask the AI: "Run a RootCauseAnalysis postmortem for this outage and produce a timeline, contributing factors, and a ranked set of actionable remediation steps."

Frequently Asked Questions about RootCauseAnalysis

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

FAQPage Schema

How do I conduct a blameless postmortem for a production outage?▼

A blameless postmortem builds an evidence-based timeline first, framing failures as system conditions rather than individual mistakes, and identifies actionable contributing factors to prevent recurrence.

What is the best way to map root causes for recurring software defects?▼

Mapping root causes for recurring defects uses Five Whys for causal chains and Fishbone diagrams for category mapping, decomposing issues into systemic, actionable causes rather than stopping at proximate cause.

When do I need a fault tree analysis for security events?▼

Fault tree analysis is needed for safety-critical security events, applying Boolean logic to evaluate failure paths and identify the deepest cause where you can implement a change within organizational control.

Can I use Kepner-Tregoe for incident analysis on pre-launch risks?▼

Yes, Kepner-Tregoe supports pre-launch risk inversion and incident analysis by performing IS and IS-NOT deviation analysis to isolate evidence-based contributing factors and produce concrete corrective actions.

Does blameless incident analysis work without hindsight bias affecting the timeline?▼

Blameless incident analysis actively resists hindsight and confirmation bias by enforcing a timeline-first execution order, ensuring systemic causes are identified through evidence-based decomposition before assigning corrective actions.