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.
Profile →npx skills add majiayu000/claude-skill-registry --skill thinking-five-whys-plus --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Five Whys Plus ## Overview The Five Whys technique from Toyota Production System is powerful but often misapplied. This enhanced version adds explicit guards against common failures: premature stopping, single-cause bias, blame-oriented thinking, and confirmation bias. It transforms a simple technique into a rigorous root cause methodology. **Core Principle:** Keep asking "why" until you reach actionable root causes, but guard against the technique's known failure modes. ## When to Use - Incident post-mortems - Bug investigations - Process failures - Customer complaints - Recurring problems - Any situation where you need root cause, not just proximate cause Decision flow: ``` Problem occurred? → Is the cause obvious and verified? → yes → Fix directly → Need to find root cause? → yes → APPLY FIVE WHYS PLUS → Is this a complex multi-factor problem? → yes → Consider Kepner-Tregoe PA ``` ## Standard Five Whys Failure Modes | Failure Mode | Description | Guard | |--------------|-------------|-------| | Premature stopping | Accepting first plausible cause | Minimum depth + actionability test | | Single-cause bias | Assuming one root cause | Branch on "what else?" | | Blame orientation
- Overview
- When to Use
- Standard Five Whys Failure Modes
- The Five Whys Plus Process
- Step 1: State the Problem Precisely
- Step 2: Apply "Why" with Evidence Requirement
- Step 3: Branch on "What Else?"
- Step 4: Apply "Why Was This Possible?" for Human Error
- Step 5: Check Stopping Criteria
- Step 6: Verify with Counter-Analysis
- Enhanced Template
- Example: Production Outage
- Common Patterns to Catch
- The Blame Stop
What does the thinking-five-whys-plus skill do?
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.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill thinking-five-whys-plus --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.