5-whys

Guide structured why-chains to identify root causes of recurring problems.

1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/bcbeidel/toolkit --skill 5-whys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 5-whys
Source: https://github.com/bcbeidel/toolkit/tree/main/plugins/consider/skills/5-whys
Command: npx skills add https://github.com/bcbeidel/toolkit --skill 5-whys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drill to root cause by asking why repeatedly until fundamentals emerge — use when a problem recurs or the quick fix keeps failing to hold.

Core Features & Use Cases

  • Structured why-chain analysis that reveals the underlying causes behind recurring problems.
  • Supports multiple causal paths, guards against single-chain tunnel vision, and documents findings for accountability.
  • Handy handoff to additional mental models or actions to address root causes.

Quick Start

Provide a clear problem statement and I will generate a five-why analysis with root causes and recommended actions.

Frequently Asked Questions about 5-whys

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

FAQPage Schema
How do I find the root cause of a recurring problem in my operations process?

Root cause analysis identifies underlying factors by iteratively asking why through structured causal chains. This method drills past recurring symptoms to reveal verifiable fundamental causes for process improvement.

When should I use a five-why analysis instead of a quick fix?

Use five-why analysis when problems recur or quick fixes keep failing. It reveals underlying systemic factors through structured why-chains, preventing repeated failures in product or operations workflows.

How do I structure a five-why analysis for cross-team problem investigation?

Start with a clear problem statement, then generate iterative why-chains across multiple causal paths to prevent tunnel vision. Document root causes and verification steps to ensure cross-team accountability.

Can I explore multiple causal paths to avoid single-chain tunnel vision during root-cause analysis?

Yes, structured why-analysis supports multiple causal paths to prevent single-chain tunnel vision. Exploring various chains ensures comprehensive discovery of underlying factors before documenting root causes.

What are the limitations of using a five-why approach for complex product issues?

Five-why analysis risks single-chain tunnel vision without structured multiple causal paths. It requires clear problem statements to reveal verifiable root causes and avoid oversimplifying complex cross-team product issues.