root-cause-analyzer

Guide users through the 5 Whys method and document findings in a knowledge base.

1|Updated Mar 8, 2026

Search Tags:#debugging #documentation #problem-solving #root-cause #knowledge-base #5-whys #incident-analysis

Ready to run

npx skills add https://github.com/tense-i/stock-market-simulator --skill root-cause-analyzer-tense-i

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: root-cause-analyzer
Source: https://github.com/tense-i/stock-market-simulator/tree/main/skills/root-cause-analyzer
Command: npx skills add https://github.com/tense-i/stock-market-simulator --skill root-cause-analyzer-tense-i

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides developers through structured root-cause analysis using the 5 Whys methodology to identify root causes and document findings for institutional knowledge.

Core Features & Use Cases

KB-aware analysis: Reuses existing patterns from the Knowledge Base to avoid duplication.
Structured 5 Whys workflow: Guides through Why #1 to Why #5 with evidence capture.
Documentation & Actionables: Generates learning patterns in docs/development-learnings/ and creates KB entries and TodoWrite items for fixes.
Validation & Prevention: Includes validation steps and cross-reference linking to prevent recurrence.

Quick Start

Start a new 5 Whys session for the observed problem and document the findings using the provided template.

Frequently Asked Questions about root-cause-analyzer

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

FAQPage Schema

How do I find the root cause of a recurring software bug or process failure?▼

To find the root cause of a software bug or process failure, you can use the 5 Whys methodology to sequentially ask why an issue occurred, capturing evidence at each step until the fundamental cause is identified.

What is the 5 Whys method for incident analysis and how does it work?▼

The 5 Whys method for incident analysis works by asking a sequence of why questions starting from the observed problem, digging deeper through each answer to peel back symptoms and expose the underlying root cause.

How do I document root cause analysis findings to prevent incident recurrence?▼

Document root cause analysis findings by capturing the 5 Whys sequence, validating evidence, and generating structured learning patterns and action items in a knowledge base to prevent incident recurrence.

Can I reuse existing knowledge base patterns when analyzing a new incident?▼

Yes, you can reuse existing knowledge base patterns when analyzing a new incident by cross-referencing the current issue against documented learnings to avoid duplication and identify matching root causes.

Does root cause analysis work for operations and product workflows as well as software bugs?▼

Root cause analysis works across operations and product workflows as well as software bugs by applying the 5 Whys technique to systematically identify fundamental issues in any complex problem scenario.

What is the best way to create action items after completing a 5 Whys root cause analysis?▼

The best way to create action items after a 5 Whys root cause analysis is to generate TodoWrite items directly from the documented findings, ensuring fixes are tracked and linked to the validated root cause.