/five-whys
Use the "Five Whys" root cause analysis technique to deeply understand problems.
$ npx -y skills add NikiforovAll/claude-code-rules --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/five-whys
Context preview
What this command does when you run it.
Use the "Five Whys" root cause analysis technique to deeply understand problems.
Command definition
five-whys.mddescription: Use the "Five Whys" root cause analysis technique to deeply understand problems.
Five Whys Analysis
Use the "Five Whys" root cause analysis technique to deeply understand problems.
Process:
1. Define the Problem
Clearly state the issue or symptom
2. Ask "Why?" Five Times
- Why did this problem occur? → Answer 1
- Why did Answer 1 happen? → Answer 2
- Why did Answer 2 happen? → Answer 3
- Why did Answer 3 happen? → Answer 4
- Why did Answer 4 happen? → Answer 5 (Root Cause)
3. Validate Root Cause
- Verify the logical chain
- Check if addressing root cause prevents recurrence
- Consider multiple root causes if applicable
4. Develop Solutions
- Address the root cause, not just symptoms
- Create preventive measures
- Consider systemic improvements
Example:
**Problem**: Application crashes when processing large files
1. **Why?** → The application runs out of memory 2. **Why?** → It loads entire file into memory at once 3. **Why?** → The file parser wasn't designed for streaming 4. **Why?** → Initial requirements only specified small files 5. **Why?** → Requirements gathering didn't consider future growth
**Root Cause**: Incomplete requirements gathering process **Solution**: Implement streaming parser and improve requirements process
Best Practices:
- Focus on process, not people
- Look for systemic issues
- Document the analysis
- Involve relevant stakeholders
- Test solutions address root cause
Read more
description: Use the "Five Whys" root cause analysis technique to deeply understand problems.
Five Whys Analysis
Use the "Five Whys" root cause analysis technique to deeply understand problems.
Process:
1. Define the Problem
Clearly state the issue or symptom
2. Ask "Why?" Five Times
- Why did this problem occur? → Answer 1
- Why did Answer 1 happen? → Answer 2
- Why did Answer 2 happen? → Answer 3
- Why did Answer 3 happen? → Answer 4
- Why did Answer 4 happen? → Answer 5 (Root Cause)
3. Validate Root Cause
- Verify the logical chain
- Check if addressing root cause prevents recurrence
- Consider multiple root causes if applicable
4. Develop Solutions
- Address the root cause, not just symptoms
- Create preventive measures
- Consider systemic improvements
Example:
**Problem**: Application crashes when processing large files
1. **Why?** → The application runs out of memory 2. **Why?** → It loads entire file into memory at once 3. **Why?** → The file parser wasn't designed for streaming 4. **Why?** → Initial requirements only specified small files 5. **Why?** → Requirements gathering didn't consider future growth
**Root Cause**: Incomplete requirements gathering process **Solution**: Implement streaming parser and improve requirements process
Best Practices:
- Focus on process, not people
- Look for systemic issues
- Document the analysis
- Involve relevant stakeholders
- Test solutions address root cause
A collection of Claude Code recommendations and practices. Learn practical techniques to enhance your AI-assisted development workflow with Claude Code.
Other commands on claude-code-rules.
- /update-component-reference
description: Add plugin components to the website docs, including component reference pages, plugin index entries, and plugin READMEs argument-hint: Component or plugin to document (e.g., "skill glab", "agent code-reviewer", "plugin handbook-reflect") allowed-tools:
Open command - /version-bump
Bump versions across the monorepo during release process
Open command - /explain
Provide clear explanations of code, concepts, and system behavior with educational clarity
Open command - /prompt-generator
Generate effective prompts for Claude 4.5 Sonnet to achieve user-defined outcomes
Open command - /reflect
Create a reflective analysis of the current Claude Code session, focusing on techniques, patterns, lessons learned, and workflow improvements.
Open command - /save-prompt
Generalize the current discussion into a reusable prompt and save it as a file
Open command

