root-cause-analysis

Trace software, data quality, AI/ML, and regulatory failures to root causes.

1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/45black/uk-legal-plugins --skill root-cause-analysis-45black
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: root-cause-analysis
Source: https://github.com/45black/uk-legal-plugins/tree/main/skills/root-cause-analysis
Command: npx skills add https://github.com/45black/uk-legal-plugins --skill root-cause-analysis-45black

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Root Cause Analysis (RCA) provides a structured, blameless framework to identify root causes and corrective actions for software, data quality, AI/ML, and regulatory incidents.

Core Features & Use Cases

  • Structured five-whys analysis and Ishikawa-style factor mapping to uncover multiple contributing factors
  • CAPA-oriented action planning with detect, prevent, mitigate, process, and document categories
  • Comprehensive RCA reporting templates and governance-aligned evidence trails for regulatory readiness

Quick Start

Summarize the incident, collect evidence, and apply the five whys to identify root causes and corrective 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 blameless root cause analysis for a software incident?

Conduct a blameless root cause analysis by summarizing the incident, collecting evidence, and applying the five whys framework to identify contributing factors and CAPA-oriented corrective actions. This structured process ensures traceability and prevents recurrence without assigning individual blame.

What is the five whys framework in incident postmortems?

The five whys framework in incident postmortems is an evidence-based questioning technique used to trace failures back to their root causes. It works alongside Ishikawa-style factor mapping to uncover multiple contributing factors across software, data quality, AI/ML, and regulatory domains.

How do I create corrective and preventive action plans from an RCA?

Create corrective and preventive action plans by categorizing your RCA findings into detect, prevent, mitigate, process, and document action items. This CAPA-oriented planning ensures your incident review produces structured, traceable steps to prevent recurrence.

Can I use a structured RCA process for AI/ML and data quality failures?

Yes, you can use a structured RCA process for AI/ML and data quality failures. The framework traces these specific failure types to their root causes using evidence gathering and factor analysis, ensuring your governance investigations maintain regulatory readiness.

What is the best way to prepare an evidence trail for a regulatory incident review?

The best way to prepare an evidence trail for a regulatory incident review is to use a structured RCA template that aligns with governance requirements. This framework guides teams through evidence collection and factor analysis to ensure comprehensive regulatory readiness.

When should I not use a blameless RCA framework?

A blameless RCA framework may not be suitable when an incident investigation requires identifying individual performance issues rather than systemic process failures. This approach specifically targets software, data quality, AI/ML, and regulatory system factors to prevent recurrence.