Sheshiyer Five Whys Root Cause Analyzer
Use this skill for structured root-cause analysis when users report recurring problems or unclear failures.
Trigger Conditions
- User asks for root cause analysis
- User mentions recurring issue or repeated failure
- User asks to apply Five Whys
Required Inputs
- Problem statement
- Symptoms and evidence
- Timeline/context of occurrence
- Stakeholders/systems involved
Workflow
- Problem definition: state issue in observable, measurable terms.
- Five Whys chain: ask successive why questions with evidence checks.
- Root cause validation: test if cause explains repeated symptoms.
- Corrective actions: design fixes at system/process level.
- Prevention plan: define controls and monitoring.
Output Format
- Problem statement
- Five Whys chain
- Confirmed root cause(s)
- Corrective + preventive actions (CAPA)
- Verification checklist
Guardrails
- Don’t stop at superficial or person-blame causes.
- Require evidence at each why step.
- Include system-level prevention measures.