체계적인 뿌리 원인 분석 방법론을 제공하는 Claude Code Skills, tracing problem back to their basic issues instead of just addressing damage.

이것은 무엇입니까?

이것은 Claude Code에 대한 ** skill**입니다. Claude의 능력은 벌레잡기, 사고 조사 및 문제 해결을위한 엄격한 5-Whys 분석 수행 할 수 있습니다.

설치

Option 1: 기술 디렉토리에 복사

옵션 2: 심 링크

사용법

같은 문구를 사용할 때 기술 방아쇠는 자동으로 :

예제

구조

핵심 방법론

기술은 5 단계 과정을 따릅니다:

1. **문제 정의 ** - 특정 상태, 관찰 가능한 사실
2. Ask “왜?” Iteratively - 각 대답을 위해, 왜 일어난 일
3. ** 루트 원인을 식별 ** - 행동, 예방, 기본
4. Validate the Chain - 카시리얼을 확인하기 위해 다시 작업
5. 명세.

5-Whys Root Cause Analysis Skill

A Claude Code skill that provides systematic root cause analysis methodology, tracing problems back to their fundamental causes instead of just addressing symptoms.

What is This?

This is a skill for Claude Code that enhances Claude’s ability to perform rigorous 5-Whys analysis for debugging, incident investigation, and problem-solving.

Installation

Option 1: Copy to your skills directory

# Clone the repo
git clone https://github.com/tt-a1i/5-whys-skill.git

# Copy to Claude Code skills directory
cp -r 5-whys-skill ~/.claude/plugins/superclaude/skills/5-whys

Option 2: Symlink

git clone https://github.com/tt-a1i/5-whys-skill.git ~/skills/5-whys-skill
ln -s ~/skills/5-whys-skill ~/.claude/plugins/superclaude/skills/5-whys

Usage

The skill triggers automatically when you use phrases like:

Example

User: 用5-whys分析一下为什么部署后服务变慢了

Claude: [Applies 5-Whys methodology]

## 5-Whys Analysis: Service Performance Degradation

### Problem Statement
**What:** API latency increased from 100ms to 500ms after deployment
**When:** After v2.1.0 deployment
**Impact:** User complaints, increased timeout errors

### Why Chain
| Level | Question | Answer | Evidence |
|-------|----------|--------|----------|
| Why 1 | Why did latency increase? | DB queries slower | Query metrics |
| Why 2 | Why are queries slower? | Full table scan | EXPLAIN ANALYZE |
...

Structure

5-whys-skill/
├── SKILL.md                           # Main skill definition (~1170 words)
├── README.md                          # This file
├── LICENSE                            # MIT License
├── references/
│   ├── toyota-origins.md              # Toyota Production System history
│   └── software-patterns.md           # Common root cause patterns
└── examples/
    ├── production-incident.md         # Payment service outage analysis
    └── performance-regression.md      # Latency investigation example

Core Methodology

The skill follows a 5-phase process:

1. Define the Problem - State the problem as specific, observable fact
2. Ask “Why?” Iteratively - For each answer, ask why it happened
3. Identify Root Cause - Actionable, preventable, fundamental
4. Validate the Chain - Work backwards to verify causality
5. Define Countermeasures - Immediate fix + prevention + detection

Output Format

## 5-Whys Analysis: [Problem Title]

### Problem Statement
**What:** [Specific behavior]
**When:** [Time/conditions]
**Impact:** [Consequence]

### Why Chain
| Level | Question | Answer | Evidence |
|-------|----------|--------|----------|
| Why 1 | ... | ... | ... |