MD 5 Whys Root Cause Analyst
by ben ja
Describe any operational problem or paste data. Get a structured 5 Whys analysis with fishbone diagram and corrective action plan.
- Analyze production line downtime and find root cause
- Close NCR reports with structured 5 Whys documentation
- Reduce defect recurrence with corrective action plans
$9
· or 45 creditsSecure checkout via Stripe
Included in download
- Analyze production line downtime and find root cause
- Close NCR reports with structured 5 Whys documentation
- file_read automation included
- Ready for VS Code Copilot
See it in action
You say
Line 3 had 47 hours unplanned downtime in June. Scrap rate jumped to 8.2%. Find the root cause and give me a corrective action plan.
Your agent does
ROOT CAUSE ANALYSIS — Line 3 Downtime
5 WHYS CHAIN: Why 1: Machine stopped → Bearing failure Why 2: Bearing failed → Overheating Why 3: Overheating → Cooling blocked Why 4: Cooling blocked → PM skipped 3 cycles Why 5: PM skipped → No PM scheduling system
ROOT CAUSE: Absence of systematic PM tracking
CORRECTIVE ACTIONS: → Immediate: Manual PM check all Line 3 → 30 days: SAP PM module implementation → 60 days: Overheating sensor alert
Recurrence risk: HIGH without systematic fix
MD 5 Whys Root Cause Analyst
by ben ja
Describe any operational problem or paste data. Get a structured 5 Whys analysis with fishbone diagram and corrective action plan.
$9
· or 45 creditsSecure checkout via Stripe
Included in download
- Analyze production line downtime and find root cause
- Close NCR reports with structured 5 Whys documentation
- file_read automation included
- Ready for VS Code Copilot
- Instant install
See it in action
You say
Line 3 had 47 hours unplanned downtime in June. Scrap rate jumped to 8.2%. Find the root cause and give me a corrective action plan.
Your agent does
ROOT CAUSE ANALYSIS — Line 3 Downtime
5 WHYS CHAIN: Why 1: Machine stopped → Bearing failure Why 2: Bearing failed → Overheating Why 3: Overheating → Cooling blocked Why 4: Cooling blocked → PM skipped 3 cycles Why 5: PM skipped → No PM scheduling system
ROOT CAUSE: Absence of systematic PM tracking
CORRECTIVE ACTIONS: → Immediate: Manual PM check all Line 3 → 30 days: SAP PM module implementation → 60 days: Overheating sensor alert
Recurrence risk: HIGH without systematic fix
About This Skill
Most teams stop at the symptom — "machine broke down" — without finding the real cause. MD 5 Whys Analyst forces systematic depth: 5 levels of why, validated against your data, not guesswork. WHAT IT DOES: - 5 Whys chain analysis (5 levels deep) - Ishikawa fishbone diagram (6M framework) - Corrective action plan with owner + deadline - Recurrence prevention checklist - RAG scoring on root cause confidence WHY USE THIS: Built for lean manufacturing, quality teams, and operations managers who need to close NCRs fast — without spending hours in a whiteboard session. SEE IT IN ACTION: Input: "Line 3 had 47 hours unplanned downtime in June. Scrap rate jumped to 8.2%." Output: Root Cause: Absence of systematic PM tracking 5 Whys Chain: Bearing failure → Overheating → Cooling blocked → PM skipped → No PM system Actions: Immediate manual PM check + SAP PM module in 30 days OUTPUT FORMATS: → In-chat: 5 Whys chain + fishbone summary → PPTX: RCA Presentation → DOCX: NCR Closure Report → XLSX: Corrective Action Tracker WORKS WITH: Any industry · Manufacturing · Logistics · Healthcare · 14 languages output · Any ERP data KNOWN LIMITATIONS: - Depends on quality of problem description — vague inputs produce shallow analysis - Does not replace on-site investigation for safety-critical incidents - Not a substitute for certified quality auditor (ISO 9001, IATF 16949) sign-off Built on MD-UBAOS™ v4.6 — 9 Hard Gate quality-controlled analysis framework.
Use Cases
- Analyze production line downtime and find root cause
- Close NCR reports with structured 5 Whys documentation
- Reduce defect recurrence with corrective action plans
- Identify bottlenecks from SAP or ERP operational data
Known Limitations
Depends on quality of problem description — vague inputs produce shallow analysis. Does not replace on-site investigation for safety-critical incidents. Not a substitute for certified quality auditor (ISO 9001, IATF 16949) sign-off on formal NCRs.
How to Install
mkdir -p ~/.claude/skills && curl -sL https://www.agensi.io/api/install/md-5-whys-root-cause-analyst -o /tmp/md-5-whys-root-cause-analyst.zip && unzip -o /tmp/md-5-whys-root-cause-analyst.zip -d ~/.claude/skills && rm /tmp/md-5-whys-root-cause-analyst.zipFree skills install directly. Paid skills require purchase - use the download button above after buying.
Reviews
No reviews yet - be the first to share your experience.
Only users who have downloaded or purchased this skill can leave a review.
Early access skill
Be the first to review this skill.
Only users who have downloaded or purchased this skill can leave a review.
Security Scanned
Passed automated security review
Permissions
File Scopes
This skill reads user-provided CSV/Excel files only. No internet connection, terminal, or external system access required.
Best with Claude.ai and Claude Code. Works with any SKILL.md-compatible agent (Cursor, VS Code Copilot, Gemini CLI). No Node.js or special runtime required — analysis skill only.
Creator
Frequently Asked Questions
Learn More About AI Agent Skills
More Premium Skills
designing-hybrid-context-layers
Architects the right retrieval strategy for every query — teaching your agent when to use RAG, a knowledge graph, or a temporal index instead of defaulting to vector search for everything.
diagnosing-rag-failure-modes
RAG fails quietly. It retrieves documents, returns confident-looking answers, and misses the question entirely — because the question required connecting facts across documents, reasoning about sequence, or tracing causation. This skill gives you a five-question diagnostic checklist that classifies any failing query as either RAG-safe or structurally RAG-incompatible, then maps it to the specific failure pattern and the architectural fix that resolves it.
synthesizing-institutional-knowledge
Builds the organizational memory schema your AI agent needs to answer why — capturing decision provenance, causal chains, and event context that embedding-based retrieval permanently discards.
research-to-decision-pro-skill
Turn messy research into rigorous, evidence-backed decision memos with specialized modes for technical and business leads.