root-cause-analysis

Diagnose and verify controllable system causes of recurring business failures.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/fritzgeraldz/Vibe-Managing --skill root-cause-analysis-fritzgeraldz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: root-cause-analysis
Source: https://github.com/fritzgeraldz/Vibe-Managing/tree/main/skills/quality/root-cause-analysis
Command: npx skills add https://github.com/fritzgeraldz/Vibe-Managing --skill root-cause-analysis-fritzgeraldz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Recurring operational failures are often treated at the symptom level, causing the same problems to return. This Skill guides an evidence-backed root cause analysis that identifies and verifies the controllable system causes behind failures, then produces a corrective action and monitoring plan. ## Core Features & Use Cases - Structured Causal Analysis: Walks through problem definition, impact containment, timeline collection, cause mapping, hypothesis testing, and corrective action verification. - Decision-Grade Output: Produces a diagnosis with evidence and confidence scores, ranked options by risk-adjusted value, and a plan with owners, approvals, and stop conditions. - Use Case: A founder notices customer churn keeps recurring despite fixes. The Skill loads company metrics and prior decisions, maps candidate causes, tests hypotheses against evidence, and recommends the smallest corrective action portfolio with leading indicators and a review date. ## Quick Start Use root cause analysis to find why our recurring fulfillment delays keep happening and recommend a corrective action plan within our cash and risk limits.

Frequently Asked Questions about root-cause-analysis

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

FAQPage Schema
How do I perform a root cause analysis for recurring business problems?▼

Define the problem precisely, contain its impact, collect a timeline and data, map candidate causes, test hypotheses against evidence, and identify the root and escape cause. Then verify the corrective action and set leading indicators with a review date.

What is the difference between root cause analysis and treating symptoms?▼

Root cause analysis identifies and verifies the controllable system causes behind a failure, while symptom treatment addresses surface effects that let the problem recur. Verified root-cause rate and recurrence are tracked as KPIs to confirm the fix worked.

When should I not use root cause analysis?▼

Do not use it during an active emergency, where the relevant incident or crisis workflow takes command first. Also avoid it for legal, tax, clinical, safety, or engineering determinations that require a licensed specialist.

What inputs does a root cause analysis need to be reliable?▼

It needs a clear objective with baseline and target, hard constraints, current state, evidence with sources and confidence scores, and business context such as industry profile, stage, and jurisdictions. Missing material facts are requested in one batch rather than invented.

How are corrective actions verified after a root cause analysis?▼

Corrective actions are verified by defining leading indicators, stop and scale conditions, and a review date, then comparing expected versus actual results at review. If indicators cross a stop threshold, automation pauses and the case escalates to an accountable human.