Agent skill
problem-solving
Use when stuck, facing a complex bug, or need root cause analysis — 5 whys, bisection, inversion techniques
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/problem-solving-klara-copilot-epost-agent-kit-2
Metadata
Additional technical details for this skill
- keywords
-
problem-solving root-cause analysis debugging 5-whys bisection crash error stuck
- triggers
-
[ "stuck", "problem", "root cause", "why" ] - platforms
-
[ "all" ] - connections
-
{ "enhances": [ "debugging" ] } - agent affinity
-
[ "epost-debugger", "epost-implementer", "epost-architect" ]
SKILL.md
Problem Solving Skill
Purpose
Root cause analysis and complex problem resolution.
When Active
User reports bug, system is behaving unexpectedly, debugging feels stuck.
Expertise
Techniques
Root Cause Analysis (5 Whys)
Ask "why" 5 times to dig past symptoms to fundamental cause.
Inversion
Ask "what would make this fail?" then prevent those conditions.
Collision Zone Thinking
Find where multiple systems interact. Bugs live at boundaries.
State Machine Extraction
When a component behaves unexpectedly, extract its actual state machine from code. Compare actual vs expected transitions — the diff IS the bug. See planning/references/state-machine-guide.md for notation.
Simplification Cascades
Remove complexity until problem disappears. Add back until it returns.
When Stuck
- Change perspective (explain to rubber duck)
- Bisect the problem (binary search for root cause)
- Check assumptions (what are you taking for granted?)
- Sleep on it (context switch resets mental model)
- Zoom out (is this really the right problem?)
Patterns
Root Cause Analysis Format
Problem: [Observed behavior]
Why 1: [Immediate cause]
Why 2: [What caused that]
Why 3: [Layer deeper]
Why 4: [Systemic issue]
Why 5: [Fundamental cause]
Fix: [Address root, not symptom]
Bisection Strategy
- Create minimal failing test
- Remove half the code
- Does it still fail? If yes, problem is in remaining half
- Repeat until isolated
Best Practices
- Fix root causes, not symptoms
- Don't stop at first "why"
- Test your hypothesis before implementing
- Consider environmental factors
- Document the problem-solving path
- Share what you learned with team
Related Skills
debugging— Systematic debugging methodologyerror-recovery— Error handling and recovery patternsknowledge-capture— Persist root cause findingssequential-thinking— Structured step-by-step reasoning
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?