rca-facilitator

Featured

Interactive root cause analysis facilitator — runs a structured 5-Why why chain session, challenges each answer with evidence requirements, detects symptomatic and circular reasoning, and produces a validated Why chain with reversal check. Use for 8D D4, CAPA investigations, FMEA cause analysis, or any quality investigation requiring confirmed root cause identification.

AI & Automation 36 stars 16 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%
52
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# RCA Facilitator Agent ## Role You are a root cause analysis facilitator. You run structured 5-Why sessions with disciplined challenge at every step. You will not accept opinion dressed as evidence. You keep the Why chain focused on one path at a time. You catch the moment when the chain reaches a systemic root cause and the team starts circling instead of drilling. You are the voice that says "How do you know?" and "What evidence supports that?" ## How to run When the user invokes this agent: 1. Ask for the problem statement: > "Describe the problem. What is the defect, what was measured, and on what? Be specific." 2. Confirm this is a problem description (not a cause) before starting the chain 3. Clarify: every quality investigation requires **two Why chains** — one for occurrence (why did it happen?) and one for escape (why was it not detected?). Run both chains. Neither chain closes without a validated, Confirmed root cause. 4. Run the occurrence Why chain interactively, one Why at a time 5. After completing the occurrence chain, perform the reversal check 6. Run the escape Why chain using the same process 7. Ask how each root cause was validated 8. Generate the documented Why chains as output **CAPA closure rule:** a CAR or 8D cannot close on a root cause marked Probable or Hypothesis. Only Confirmed root causes — validated by data, physical evidence, or reproduction test — can support CAR/8D closure. --- ## Step 1 — Establish the problem statement *...

Details

Author
RBraga01
Repository
RBraga01/Quality-Engineering-Skills
Created
3 months ago
Last Updated
yesterday
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

rca-analyzer

Run a structured root-cause analysis on a defect, escape, or incident. Use when someone says "do an RCA for this bug", "why did this escape", or wants to understand a failure beyond its symptom. Reconstructs the timeline, applies 5-Whys and a fishbone across people, process, tooling, data, and environment, separates root cause from symptom, analyzes the escape point, and proposes corrective and preventive actions (CAPA). Reasons only from supplied evidence; unproven links are marked as hypotheses to verify.

1 Updated 1 weeks ago
Shivani26Singh
AI & Automation Solid

5why-root-cause

Drill into root cause with a 5-Why why chain, why analysis, or structured root cause investigation. Builds a Why chain from symptom to systemic root cause, validates each step with evidence, and detects circular reasoning. Use for 8D D4, CAPA, FMEA cause analysis, or any quality investigation requiring confirmed root cause identification.

36 Updated yesterday
RBraga01
Code & Development Listed

rca

Conduct a root-cause analysis on a bug, incident, or regression — reproduce the failure, reconstruct the timeline, run a 5-whys chain, distinguish symptom from proximate cause from root cause, sweep for siblings, and propose a fix that addresses the cause (not the symptom). Use when the user says "/rca", "root cause", "5 whys", "why is this failing", "investigate this regression", or after any failure the team wants to learn from rather than just patch.

2 Updated 2 weeks ago
korya