Does the skill suggest its own technical solutions?

No, the skill acts as a neutral facilitator. It avoids guessing or providing technical opinions, focusing instead on organizing the user's observations and logic to ensure the analysis remains objective.

What is the primary methodology used by this skill?

It uses the '5 Whys' technique, a systematic iterative interrogative technique used to explore the cause-and-effect relationships underlying a particular problem until a systemic root cause is identified.

What kind of documentation does it produce?

It generates two primary Markdown files: result.md, which contains the summary and Mermaid mind map, and log.md, which documents the entire conversation history for audit and review purposes.

Can it handle incidents with multiple contributing factors?

Yes, the skill is designed to recognize and split complex factors into separate branches, ensuring each independent path is analyzed thoroughly until its specific root cause is found.

Incident Root Cause Analysis (RCA) Facilitator

Name: Incident Root Cause Analysis (RCA) Facilitator
Author: windschord

bywindschord

Analytics & Monitoring

Facilitates structured 5 Whys analysis to identify systemic root causes of software incidents through neutral guidance and real-time visualization.

About

The incident-rca skill transforms Claude into a neutral facilitator for incident investigations, guiding users through the rigorous 5 Whys methodology without introducing bias or guesswork. It systematically records user observations, splits complex factors into manageable branches, and visualizes the entire analysis using Mermaid mind maps. By maintaining a strict focus on facts and organizational structures, it ensures that investigations move past surface-level symptoms to reach actionable, systemic root causes, ultimately producing comprehensive Markdown documentation for future prevention.

Key Features

Real-time Mermaid mind map generation for visual cause-and-effect tracking.
Systematic validation to ensure identified causes lead to actionable prevention steps.
0 GitHub stars
Intelligent factor splitting for incidents involving multiple contributing causes.
Guided 5 Whys facilitation with a neutral, objective stance to avoid bias.
Automatic generation of result.md and log.md files for post-mortem documentation.

Use Cases

Analyzing complex software bugs that involve multiple interacting microservices.
Conducting post-mortem investigations for system outages or service degradations.
Reviewing organizational process failures to improve team coding standards and deployment safety.

About

Key Features

Real-time Mermaid mind map generation for visual cause-and-effect tracking.
Systematic validation to ensure identified causes lead to actionable prevention steps.
0 GitHub stars
Intelligent factor splitting for incidents involving multiple contributing causes.
Guided 5 Whys facilitation with a neutral, objective stance to avoid bias.
Automatic generation of result.md and log.md files for post-mortem documentation.

Use Cases

Analyzing complex software bugs that involve multiple interacting microservices.
Conducting post-mortem investigations for system outages or service degradations.
Reviewing organizational process failures to improve team coding standards and deployment safety.