Agent skill
systematic-thinking
Rigorous problem decomposition and evidence-based analysis methodology for software engineering tasks. Use to analyze situations, figure out concepts or investigations.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/systematic-thinking
SKILL.md
Systematic Thinking
Systematic thinking is a structured methodology for decomposing complex problems and arriving at root causes through evidence-based reasoning. Use this skill for debugging, investigation, and any problem where the true cause is not immediately apparent.
When to Use
- Debugging issues where surface symptoms don't reveal the cause
- Analyzing incidents or failures with multiple potential factors
- Investigating why something isn't working as expected
- Breaking down complex problems into actionable components
- Any task where quick conclusions have led to incomplete fixes
The 5 Phases
-
Problem Decomposition - Break the issue into discrete components. What exactly is failing? Where does it manifest?
-
Evidence Gathering - Collect data before forming conclusions. Logs, traces, reproduction steps, environment details.
-
Hypothesis Formation - Form specific, testable hypotheses. Not "something is wrong" but "X causes Y because Z."
-
Testing & Verification - Test hypotheses systematically. Verify assumptions. Reproduce the issue in isolation.
-
Root Cause Focus - Distinguish symptoms from causes. Keep asking "why" until you reach the fundamental cause.
Red Flags
- Jumping to solutions before fully understanding the problem
- Focusing on symptoms instead of root causes
- Assuming without verification
- Ignoring contradictory evidence
- Stopping at the first plausible explanation
- Fixing the same issue repeatedly
See Also
- systematic-debugging - The rigid debugging companion skill for test-first debugging discipline
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
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.
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.
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.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
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?