5why-root-cause
SolidDrill 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.
Install
Quality Score: 86/100
Skill Content
Details
- Author
- RBraga01
- Repository
- RBraga01/Quality-Engineering-Skills
- Created
- 3 months ago
- Last Updated
- 2 days ago
- Language
- JavaScript
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
5-why
Performs 5-Why root-cause analysis (RCA) from the Toyota Production System, tracing a problem through five why-questions in dialog until the actual cause — not the symptom — is found. Use when the user says root cause, RCA, postmortem, incident, retrospective, recurring bug, "why does this keep happening", 5 whys or 5w, or reports a defect or failure that keeps coming back. Also handles the what-for variant for sharpening goals or OKRs. Not for complex social systems with circular causality (team dynamics, feedback loops) — label results as hypotheses there.
five-whys
Run root-cause analysis the Toyota way: ask why five times to reach the system failure behind a product or process incident, then invest a proportional fix at each level. Blocks blame answers and stops teams from fixing symptoms. Use after any incident, outage, missed release, quality regression, or repeated process failure, when writing a postmortem, or when the user says five whys, root cause, why did this happen, postmortem, or blameless analysis. Not for strategic decisions, metric analysis, or interpersonal conflict — those are not causal chains.
thinking-five-whys-plus
Enhanced root cause analysis with explicit bias guards and stopping criteria. Use for incident post-mortems, bug investigations, and process failures where standard 5 Whys might mislead.