Five whys root cause analyzer
Skill Sheshiyer/skill-clusters/skills/five-whys-root-cause-analyzer
Hub-and-spoke agent-skill clusters, one per stack (Astro·GSAP·Remotion, Tauri, …). Installable via skills.sh.
npx -y skills add Sheshiyer/skill-clusters --skill five-whys-root-cause-analyzerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Apply Five Whys rigorously to trace issues to root causes and define durable corrective actions. USE WHEN a task matches the Craft workspace workflow for five-whys-root-cause-analyzer.
SKILL.md
1.3 KB, as published. Nobody here has run it
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.