root-cause-analysis

Identify and document root causes using Ishikawa categories and Five Whys.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured Root Cause Analysis (RCA) for incidents across software, data quality, AI/ML, and legal/compliance, enabling blameless learning and actionable CAPA.

Core Features & Use Cases

  • Systematic root-cause mapping using Ishikawa categories and Five Whys to identify contributing factors.
  • CAPA planning, action item management, and audit trails for governance and regulatory needs.
  • Use cases include postmortems, incident reviews, data quality investigations, and regulatory investigations.

Quick Start

Run an RCA on the latest incident to generate a structured root-cause and action-item plan.

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 root cause analysis for a software incident?

Conduct a root cause analysis by applying structured methodologies like Ishikawa categories and Five Whys to map contributing factors. This Skill systematically documents incident root causes across software, data, and compliance domains to produce a formal RCA.

What is the best way to structure a postmortem with corrective actions?

Structure a postmortem with corrective actions by using this Skill to map root causes and generate a formal CAPA plan. It provides action item management and audit trails to ensure blameless learning and actionable corrective actions.

Can I use Ishikawa diagrams and Five Whys for data quality investigations?

Yes, you can use Ishikawa categories and Five Whys for data quality investigations. This Skill applies these structured methodologies to identify contributing factors and document root causes across software, data, AI/ML, and compliance domains.

How does root cause analysis support compliance and audit requirements?

Root cause analysis supports compliance by generating formal RCA documents with evidence trails and governance considerations. This Skill produces CAPA plans and audit trails required for regulatory investigations and compliance reporting.

When do I need a structured RCA for incident management?

You need a structured RCA for incident management when you require formal documentation of contributing factors, root causes, and corrective actions. This Skill enables blameless learning and produces evidence trails necessary for governance and regulatory needs.