skills.rest
takusaotome
takusaotomeCOMMUNITY
Explore all skills by this author →
GitHub

incident-rca-specialist

Guide post-incident reviews with timeline, impact, root cause, and corrective action planning.

5|4|Updated Nov 9, 2025
Search Tags:#timeline#impact assessment#corrective actions#post-incident review#incident rca#smart criteria#fault tree analysis
One-click install
npx skills add https://github.com/takusaotome/claude-skills-library --skill incident-rca-specialist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incident-rca-specialist
Source: https://github.com/takusaotome/claude-skills-library/tree/main/skills/incident-rca-specialist
Command: npx skills add https://github.com/takusaotome/claude-skills-library --skill incident-rca-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you perform consistent, organizationally focused post-incident reviews by turning incident facts into a structured timeline, impact assessment, root cause analysis, and corrective action plan—without drifting into log-level technical debugging.

Core Features & Use Cases

  • Incident information gathering: Collects interview-based facts (what happened, when, who was involved) and identifies missing information gaps.
  • Timeline & metrics: Constructs a chronological timeline and computes key metrics (TTD, TTR, TTM, TTRe) plus bottleneck identification.
  • Impact assessment (P0–P4): Evaluates impact across user, service, business, and operational dimensions using an SLA/severity matrix and quantifies business impact.
  • Root cause analysis (RCA): Provides process/system-oriented RCA via 5 Whys with branching, Fishbone (People/Process/Technology/Environment/Data/External), and Fault Tree Analysis with SPOF-focused insight.
  • Corrective actions that actually execute: Produces SMART corrective actions using the 3D Prevention Framework (Detect/Defend/Degrade) and organizes them into time horizons (immediate/short-term/long-term) with ownership tracking templates.
  • Full RCA report generation: Outputs a comprehensive Markdown RCA report using Japanese or English templates.
  • Blame-free guidance: Enforces a method of focusing on process and system improvements, including decomposing “human error” into process/system/training gaps.

Quick Start

Use the incident-rca-specialist skill for a completed (mitigated or closed) incident where you need to produce an incident timeline, severity assessment, root cause analysis, and a SMART corrective action plan (without performing log-level debugging).

Frequently Asked Questions about incident-rca-specialist

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

FAQPage Schema
How do I conduct a post-incident review without getting stuck in log-level debugging?▼

A post-incident review should focus on organizational process and system improvements. This Skill facilitates timeline construction, impact assessment, and root cause analysis, enforcing evidence-based causal links rather than drifting into technical log debugging.

What is the best way to structure root cause analysis using 5 Whys and Fishbone diagrams?▼

Root cause analysis using 5 Whys with branching, Fishbone, and Fault Tree Analysis helps identify SPOF-focused insights. This Skill guides you through these frameworks to systematically decompose issues into process, system, and training gaps.

How do I generate SMART corrective actions after an incident?▼

SMART corrective actions are generated using the 3D Prevention Framework, which organizes tasks into Detect, Defend, and Degrade categories. This approach produces time-phased action items with ownership tracking templates for immediate, short-term, and long-term horizons.

Can I assess incident severity and SLA impact across different business dimensions?▼

Incident severity and SLA impact can be assessed across user, service, business, and operational dimensions. This Skill uses a P0–P4 severity matrix to quantify business impact and evaluate SLA compliance during the post-incident review.

How do I calculate incident metrics like TTD, TTR, and TTM for a timeline?▼

Incident metrics like TTD, TTR, TTM, and TTRe are computed by constructing a chronological timeline of events. This Skill identifies bottlenecks and calculates these key metrics to provide a clear picture of incident response performance.

Does this incident RCA tool support blame-free post-incident reviews?▼

Blame-free post-incident reviews are supported by enforcing a method that focuses strictly on process and system improvements. This Skill actively decomposes human error into underlying process, system, or training gaps instead of assigning individual blame.

Related Skills

Explore More Software Engineering Skills→
CygnusfearCygnusfear
5

delphi

Coordinate parallel oracle investigations and synthesize reports into a final document.

Community
Advanced
leonardoteodorooleonardoteodoroo

postmortem-writing

Generate blameless postmortems with root cause analysis, timelines, and action items.

Community
Advanced
shaun0927shaun0927

trace

Generate a chronological agent flow trace timeline and summary.

Community
Intermediate
BagelHoleBagelHole
46

alerting-oncall

Configure Prometheus alert rules and on-call rotations with PagerDuty or Grafana OnCall.

Community
Advanced