root-cause

Guide root-cause analysis through Five Whys, First Principles, and JTBD workflows.

9|2|Updated Aug 12, 2025
One-click install
npx skills add https://github.com/fernandobandeira/djinn --skill root-cause
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: root-cause
Source: https://github.com/fernandobandeira/djinn/tree/main/.claude/skills/root-cause
Command: npx skills add https://github.com/fernandobandeira/djinn --skill root-cause

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dig beneath symptoms to find fundamental causes and truths. Stop treating symptoms and solve actual problems.

Core Features & Use Cases

  • Five Whys - Chain backward from symptom to root cause by repeatedly asking why.
  • First Principles Decomposition - Strip away assumptions to rebuild from fundamental truths.
  • Jobs-to-be-Done (JTBD) - Understand user needs beyond stated wants to uncover true motivations.
  • Practical guidance on selecting the right technique for the situation and verifying root causes.

Quick Start

  1. Identify what you're trying to understand.
  2. Select a technique (Five Whys, First Principles, or JTBD).
  3. Continue digging until you reach a fundamental truth and define concrete actions.

Frequently Asked Questions about root-cause

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

FAQPage Schema
How do I identify the root cause of a problem instead of just treating symptoms?

Root cause analysis digs beneath surface symptoms to find fundamental causes. This Skill guides you through structured techniques—Five Whys, First Principles, and Jobs-to-be-Done—to decompose problems systematically and uncover underlying truths rather than addressing temporary fixes.

What's the difference between Five Whys, First Principles, and Jobs-to-be-Done analysis?

Five Whys chains backward from a symptom by repeatedly asking why to expose cause chains. First Principles strips away assumptions to rebuild understanding from fundamentals. Jobs-to-be-Done uncovers true user motivations beyond stated wants. Each suits different diagnostic contexts.

How do I know which root-cause technique to use for my problem?

The Skill provides practical guidance for technique selection based on your situation. Five Whys works well for linear cause chains; First Principles for rethinking assumptions; Jobs-to-be-Done for understanding user behavior. Structured workflow helps you match the right method to your diagnostic challenge.

Can I use root-cause analysis for product, process, and strategy problems?

Yes. Root-cause analysis applies across product diagnostics, operational process failures, and strategic challenges. The same structured reasoning—decomposition, verification, and actionable documentation—works for any domain where you need to move from symptoms to fundamental causes.

How do I verify I've found the actual root cause and not just another symptom?

The Skill includes root-cause verification steps within its structured workflow to ensure you've reached a fundamental truth rather than an intermediate layer. Verification prevents stopping at symptoms, confirming you can take concrete action to eliminate the underlying problem.

What output do I get after completing a root-cause analysis?

You produce actionable documentation that traces the problem from symptom through decomposition to verified root cause, with concrete actions defined. This record makes findings transparent, shareable, and implementable across product, process, or strategy contexts.