Perform iterative Five Whys root cause analysis from stated symptoms.
npx skills add https://github.com/Gamezar/opencode-cek --skill kaizen-why-gamezar
Please help me install this Agent Skill. Skill: kaizen-why Source: https://github.com/Gamezar/opencode-cek/tree/main/plugins/kaizen/skills/kaizen-why Command: npx skills add https://github.com/Gamezar/opencode-cek --skill kaizen-why-gamezar
This Skill helps you systematically uncover the fundamental root causes of problems by iteratively asking "why," preventing superficial fixes and addressing systemic issues.
Analyze the problem 'Users see 500 error on checkout' using the kaizen-why skill.
High-intent search queries and answers about installing and using this skill.
Five Whys root cause analysis is an iterative troubleshooting method that drills down from a production error symptom to its fundamental cause by repeatedly asking why, preventing superficial fixes and exposing systemic process failures.
To perform root cause analysis for a process failure, you provide a clear problem statement and the skill systematically drills down through the causal chain, iteratively asking why until the fundamental issue is identified.
Yes, you can adjust the analysis depth when tracing a 500 error, allowing the iterative questioning to stop at the appropriate systemic flaw or missing check rather than forcing a fixed number of iterations.
You need root cause analysis when a system failure or bug is recurring, because it moves beyond surface-level symptoms to identify deeper process-related flaws and missing checks that allowed the error to happen.
Yes, the Five Whys approach works for troubleshooting both software bugs and process failures by systematically drilling down through causal chains from the stated symptom to the underlying systemic issue.
simonwjacksonTrace causal chains from trigger to symptom to confirm root causes.
VoDaiLoczAnalyze systemic issues using 5 Whys and Fishbone diagrams.
weirdgmeInstrument distributed systems with OpenTelemetry and correlate logs, metrics, and traces.
GamezarAnalyze root causes using the Fishbone diagram across six predefined categories.
