skills.rest
flpbalada
flpbaladaCOMMUNITY
Explore all skills by this author →
GitHub

five-whys

Identify root causes by iteratively asking Why and documenting each step.

23|4|Updated Jan 4, 2026
Search Tags:#collaboration#problem-solving#root-cause-analysis#process-improvement#five-whys#systems-thinking
One-click install
npx skills add https://github.com/flpbalada/thinking-toolkit --skill five-whys-flpbalada
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: five-whys
Source: https://github.com/flpbalada/thinking-toolkit/tree/main/plugins/five-whys/skills/five-whys
Command: npx skills add https://github.com/flpbalada/thinking-toolkit --skill five-whys-flpbalada

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Five Whys technique helps teams quickly uncover the root causes behind problems by iteratively asking "Why?" until the underlying issue is revealed, reducing guesswork and recurring defects.

Core Features & Use Cases

  • Structured Why Chain: Build a clear sequence of why questions and responses to trace root causes.
  • Collaborative Analysis: Facilitate cross-functional discussions among product, engineering, and support.
  • Actionable Root Causes: Translate findings into focused improvements and prevention measures.
  • Use Case: When a defect recurs, run a Five Whys session to identify contributing factors and define corrective actions.

Quick Start

Start a Five Whys session by posing "Why did this happen?" for the observed issue, capture each answer, repeat until you reach a root cause, then document the root cause and propose concrete fixes.

Frequently Asked Questions about five-whys

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

FAQPage Schema
How do I perform root cause analysis for recurring product defects?▼

Root cause analysis for recurring defects uses the Five Whys technique, asking "Why?" iteratively to reveal underlying factors, document each step, and define actionable fixes.

What is the Five Whys technique and how does it work for process failures?▼

The Five Whys technique for process failures builds a structured question chain, capturing each answer sequentially until reaching a validated root cause with actionable prevention measures.

How do I start a Five Whys session for engineering and operations issues?▼

Start a Five Whys session by posing "Why did this happen?" for the observed issue, capturing each response, and repeating the question until you reach a validated root cause to document.

Can I use root cause analysis for cross-functional team collaboration?▼

Root cause analysis facilitates cross-functional team collaboration by structuring discussions among product, engineering, and support to translate findings into focused process improvements.

Do I need external tooling to identify root causes using structured questioning?▼

Identifying root causes with structured questioning requires no external tooling, relying solely on documenting each step to output a validated root cause with actionable fixes.

When should I not use a structured questioning approach for problem-solving?▼

A structured questioning approach for problem-solving is less suitable for novel issues requiring rapid experimentation rather than tracing recurring defects, churn, or process failures to underlying causes.

Related Skills

Explore More Product & Management Skills→
bcbeidelbcbeidel
1

5-whys

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

Community
Advanced
amoutiersamoutiers
1

systematic-debugging

Guide root-cause investigations across four debugging phases with validation.

Community
Advanced
ylxaiylxai
2

RootCauseAnalysis

Analyze incident reports to identify root causes and contributing factors.

Community
Advanced
devmuslimdevmuslim

System Thinking

Apply systems thinking frameworks to diagnose root causes of delivery problems.

Community
Advanced