How are the analysis results saved?

Results are saved locally in your project repository under a dedicated sessions directory, containing a result.md summary and a detailed log.md of the conversation.

Can it handle incidents with more than one cause?

Yes, the skill is designed to identify and split complex factors into separate branches, allowing for parallel '5 Whys' analysis for each contributing factor.

Does this skill suggest technical fixes?

No, the skill follows a neutral facilitation protocol. It asks probing questions to help users identify causes based on evidence rather than offering its own speculative technical opinions.

What is the purpose of the Incident RCA skill?

It serves as an objective facilitator to help teams conduct '5 Whys' analysis to find the structural root cause of technical incidents without relying on guesswork.

Does it support visual mapping?

Yes, it generates and updates a Mermaid-based mind map in real-time to help users visualize the relationship between symptoms and root causes.

Root Cause Analysis Facilitator

Name: Root Cause Analysis Facilitator
Author: windschord

bywindschord

Productivity & Workflow

Facilitates systematic 5 Whys incident investigations by recording evidence, generating real-time mind maps, and identifying structural root causes.

About

Incident RCA is a specialized facilitation skill designed to guide developers and SRE teams through a rigorous '5 Whys' analysis process following system failures. It acts as a neutral facilitator that avoids speculation, focusing instead on recording user-provided facts and observations. The skill automatically organizes complex, multi-factor incidents into visual Mermaid mind maps and persists all findings into standardized session logs and reports within your repository, ensuring that every investigation leads to at least one actionable, structural root cause.

Key Features

Automatic documentation including result.md and chronological log.md files
Standardized session management with customizable storage paths and directory structures
Real-time Mermaid mind map generation for visual incident mapping
Multi-factor factor splitting for analyzing complex, parallel failure chains
Guided 5 Whys facilitation using a neutral, non-speculative stance
0 GitHub stars

Use Cases

Conducting formal post-mortem investigations after service outages or system failures
Analyzing complex software bugs that involve multiple interacting components
Identifying organizational or process-level bottlenecks that contribute to technical debt

About

Key Features

Automatic documentation including result.md and chronological log.md files
Standardized session management with customizable storage paths and directory structures
Real-time Mermaid mind map generation for visual incident mapping
Multi-factor factor splitting for analyzing complex, parallel failure chains
Guided 5 Whys facilitation using a neutral, non-speculative stance
0 GitHub stars

Use Cases

Conducting formal post-mortem investigations after service outages or system failures
Analyzing complex software bugs that involve multiple interacting components
Identifying organizational or process-level bottlenecks that contribute to technical debt