Document root causes through iterative Why analysis with corrective actions.
npx skills add https://github.com/fockus/claude-skill-build --skill kaizen-why-fockus
Please help me install this Agent Skill. Skill: kaizen:why Source: https://github.com/fockus/claude-skill-build/tree/main/skills/kaizen-why Command: npx skills add https://github.com/fockus/claude-skill-build --skill kaizen-why-fockus
Systematic root-cause analysis for issues by iteratively drilling down from symptoms to fundamental causes, reducing quick fixes and recurring problems.
Describe the symptom and run five sequential Why analyses to reveal the root cause.
High-intent search queries and answers about installing and using this skill.
Root-cause analysis using the Five Whys technique involves iteratively asking why a symptom occurred to drill down to fundamental causes. This structured workflow records each step to ensure traceability and exposes systemic issues rather than just treating surface symptoms.
To perform Five Whys analysis for a process failure, describe the symptom and run sequential why questions to explore potential causes. The workflow captures each iteration, validates the root cause, and culminates in concrete corrective actions that address the fundamental problem.
Yes, you can explore multiple potential causes during root-cause analysis. The workflow supports branch exploration to investigate different systemic issues and their associated mitigations simultaneously before validating the fundamental cause and recommending corrective actions.
Yes, the Five Whys method is suitable for engineering and operations teams. It specifically targets product, engineering, and operations groups to analyze incidents, process failures, and quality issues, providing structured guidance to move beyond quick fixes and document actionable solutions.
The best way to document root causes is through a structured why-analysis workflow that records each iteration and evolving understanding. This ensures traceability from the initial symptom to the validated root cause and culminates in concrete corrective actions addressing the fundamental issue.
awesome-skillsTraces operational and technical problems to actionable root causes via iterative why-chaining.
edwardmonteiroGenerate standardized postmortem documents with root-cause analysis and corrective actions.
Tonybleything76Manages Corrective and Preventive Action workflows for medical device QMS, including root cause analysis and corrective action tracking.
VoDaiLoczAnalyze systemic issues using 5 Whys and Fishbone diagrams.
