Skip to content
Back to skills

Five Whys

ASecurity

Finds the root cause of a bug, failure or recurring problem by asking "why" until the answer is a cause you can fix. Use when the user asks why something keeps happening, or wants the root cause rather than a quick fix.

  • 3,098 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 6, 2026
ai-agentsgogit

Works with

  • claude code

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add wesammustafa/Claude-Code-Everything-You-Need-to-Know --skill five-whys --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Five Whys?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Five Whys
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wesammustafa-five-whys-f60a29c8/badge)](https://www.skillsdirectory.com/skills/wesammustafa-five-whys-f60a29c8)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
# What: a project skill that finds a problem's root cause by asking "why" until the answer is something you can fix.
# Runs: when you type /five-whys <problem>, or when Claude matches your request to the description.
# Side effects: none intended. It tells Claude to investigate and change no files; each tool call still follows your permission settings.
# Requires: Claude Code. Platforms: any.
# Remove: delete .claude/skills/five-whys/.
# Tested in Claude Code v2.1.285 (stable) on macOS, 2026-10-06
name: five-whys
description: Finds the root cause of a bug, failure or recurring problem by asking "why" until the answer is a cause you can fix. Use when the user asks why something keeps happening, or wants the root cause rather than a quick fix.
argument-hint: "[problem]"
---

Find the root cause of this problem: $ARGUMENTS

If no problem is given, ask for one in a single sentence, then stop.

1. Restate the problem as a symptom someone can observe: what happens, where and when.
2. Ask "Why does this happen?" Answer from evidence: the code, tests, logs and git history. Mark any answer you can't back with evidence as a guess.
3. Ask "Why?" of that answer, and keep going until the answer is a cause the team can change. That often takes about five rounds; stop sooner if you get there, and say so if you need more.
4. Check the chain backwards: each cause must explain the step before it.
5. Report the chain as a numbered list, the root cause in one sentence, then one fix for the root cause and one for the symptom.

Don't change any files. Propose the fixes and let the user decide.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.