Root cause analysis for complex bugs. Use when initial fix fails or incident is severe. Traces Effect → Cause → Root with confidence levels and prevention hierarchy.
Performs systematic root cause analysis when initial fixes fail. Triggers on persistent bugs or production incidents, tracing from effect to root cause with confidence levels and prevention hierarchy.
/plugin marketplace add saadshahd/moo.md/plugin install hope@moo.mdThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Root cause analysis when surface fixes fail.
| Trigger | Action |
|---|---|
| Bug persists after initial fix | Run trace |
| Production incident (SEV 1-2) | Run trace |
| Complex failure (multiple sources) | Run trace |
| Trivial bug (< 10 min fix) | Skip |
HH:MM - [Event] - [System state] - [Action taken]
Note: detection time vs. start time (how long hidden?)
Effect: [What users/systems experienced]
Why 1: [Immediate cause] (X-Y% confident)
Why 2: [Underlying mechanism] (X-Y% confident)
Why 3: [System/process gap] (X-Y% confident)
Why 4: [Organizational factor] (X-Y% confident)
Why 5: [Root cause] (X-Y% confident)
Gates: < 70% any level → request logs/reproduction Root cause = deepest answer with ≥70% confidence
Beyond root cause, what amplified impact?
Process: Monitoring gaps, testing gaps, review gaps People: Unclear ownership, missing runbooks Technical: Dependency failures, capacity limits, config drift Context: Traffic patterns, deployment timing, external factors
List 2-4 factors with specific mechanisms.
Tools: Ishikawa for categorization, Iceberg for deep structure analysis.
Users: Count, experience, business cost (quantified) Systems: Downstream effects, data integrity, security
1. [Code/config change]
File: [path:line]
Verification: [how to confirm]
Owner: [who]
1. [Alert/test/automation]
Trigger: [when it fires]
Owner: [who]
1. [Architectural change]
Problem class: [what it prevents]
Effort: [story points]
Owner: [who]
Each tier needs ≥1 item.
See soul/references/blameless.md
Focus on system gaps, not individual mistakes.
# Incident: [Title]
## Timeline
[Detection → Resolution]
## Five Whys
[With confidence per level]
## Contributing Factors
[2-4 items]
## Impact
[Quantified]
## Prevention
[Immediate / Short-Term / Long-Term]
## Top 3 Actions
1. [Task] | Owner: [Name] | Due: [Date]
2. ...
3. ...
| Bad | Good |
|---|---|
| "Human error" | Identify automation gap |
| "Communication failure" | Identify process gap |
| "Be more careful" | Add system safeguard |
| "Performance issue" | Specific: "Pool exhausted at 1K req/s" |
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.