consider-5-whys

Diagnose underlying issues by repeatedly asking why to identify root causes.

7|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/hhellbusch/my-ai-workspace --skill consider-5-whys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: consider-5-whys
Source: https://github.com/hhellbusch/my-ai-workspace/tree/main/.agents/skills/consider-5-whys
Command: npx skills add https://github.com/hhellbusch/my-ai-workspace --skill consider-5-whys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify the underlying root cause of a problem by systematically asking "why" multiple times, enabling more effective problem resolution.

Core Features & Use Cases

  • Problem Diagnosis: Guides users through structured questioning to uncover fundamental issues.
  • Root Cause Analysis: Helps teams avoid superficial fixes by drilling down into core causes.
  • Use Case: When a recurring defect appears in a product, apply this Skill to determine the true underlying process or systemic issue causing the defect.

Quick Start

Apply this Skill to analyze a specific problem by clearly defining the problem statement and follow the prompts to ask "why" until reaching the root cause.

Frequently Asked Questions about consider-5-whys

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

FAQPage Schema
How do I conduct root cause analysis for a recurring product defect?

Root cause analysis for a product defect involves defining the problem statement and iteratively asking "why" to diagnose the underlying systemic issue, ensuring effective resolution instead of superficial fixes.

What is the five whys method for problem solving?

The five whys problem solving method is an iterative questioning technique that drills down into core causes by asking "why" repeatedly until the fundamental issue is uncovered for troubleshooting.

When should I use iterative questioning for troubleshooting?

Iterative questioning for troubleshooting is suitable when a recurring defect appears and you need to drill down past superficial symptoms to identify the true underlying process or systemic issue.

Can I use this structured questioning approach for process improvement?

Yes, you can use this structured questioning approach for process improvement by methodically asking "why" to diagnose fundamental issues and provide actionable interventions across various scenarios.