thinking-five-whys-plus

Guide evidence-backed five-why chains to actionable root causes.

941|129|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/tjboudreaux/cc-thinking-skills --skill thinking-five-whys-plus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: thinking-five-whys-plus
Source: https://github.com/tjboudreaux/cc-thinking-skills/tree/main/skills/thinking-five-whys-plus
Command: npx skills add https://github.com/tjboudreaux/cc-thinking-skills --skill thinking-five-whys-plus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enhanced root cause analysis with explicit guards against common failure modes: premature stopping, single-cause bias, blame orientation, and confirmation bias. It helps teams reach actionable root causes, not just proximate causes, in incident post-mortems and process investigations.

Core Features & Use Cases

  • Guided Why chains with evidence requirements for each step to prevent guesswork
  • Explicit stopping criteria: actionable, controllable, fundamental, evidenced, and system-focused
  • Counter-analysis prompts to surface alternative explanations and guard against confirmation bias
  • Use cases include incident response, bug investigations, and process improvement efforts

Quick Start

Initiate Five Whys Plus on an incident to guide iterative why-questions with evidence requirements until a concrete root cause is reached.

Frequently Asked Questions about thinking-five-whys-plus

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I conduct a root cause analysis that avoids blame and finds actionable causes?

Root cause analysis should guide an evidence-backed why-chain with explicit stopping criteria—actionable, controllable, and system-focused—to yield auditable root causes rather than proximate causes or individual blame.

What is the best way to run a Five Whys analysis for an incident post-mortem?

The best Five Whys analysis enforces evidence requirements for each iterative why-question, includes counter-analysis prompts to surface alternative explanations, and applies explicit stopping criteria to reach a concrete, system-focused root cause.

Why does my root cause analysis stop too early and produce only proximate causes?

Root cause analysis stops prematurely when it lacks explicit stopping criteria and evidence requirements; enforcing guardrails against premature stopping and single-cause bias ensures the investigation reaches fundamental, actionable causes.

How do I prevent confirmation bias during a bug investigation's why-chain?

Prevent confirmation bias by using counter-analysis prompts that surface alternative explanations at each step, requiring structured problem statements, and demanding evidence for every why to guard against guesswork.

Can I use structured root cause analysis for process improvement efforts, not just incident response?

Yes, evidence-backed root cause analysis applies to process improvement efforts and bug investigations as well as incident post-mortems, guiding iterative why-questions with evidence requirements until a concrete root cause is reached.

What are the limitations of using a Five Whys approach for incident management?

A basic Five Whys approach risks blame orientation, single-cause bias, and premature stopping; rigorous guardrails with evidence requirements and counter-analysis prompts are needed to prevent these failure modes.