alexismanuel/systematic-thinking
.config/opencode/skills/systematic-thinking/SKILL.md
Rigorous problem decomposition and evidence-based analysis methodology for software engineering tasks. Use to analyze situations, figure out concepts or investigations.
development
Updated Apr 1, 2026
$ install --global
skillsauthnpx skillsauth add alexismanuel/dotfiles systematic-thinkingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 2, 2026, 3:25 AM61.2s1 file scanned
SKILL.md
- name:
- systematic-thinking
- description:
- Rigorous problem decomposition and evidence-based analysis methodology for software engineering tasks. Use to analyze situations, figure out concepts or investigations.
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
Related Skills
alexismanuel/mr-generator
development
VerifiedTrustedCommunity
Generate GitLab merge request descriptions from git commits with automatic categorization and Jira integration.
SKILL.mdUpdated Apr 1, 2026
alexismanuel/workflow-validate-plan
development
VerifiedTrustedCommunity
This skill should be used when validating that an implementation plan was correctly executed. It verifies success criteria, runs tests, identifies deviations, and presents structured completion options including MR creation or discard.
SKILL.mdUpdated Apr 1, 2026
alexismanuel/workflow-review-code
development
VerifiedTrustedCommunity
This skill should be used when reviewing code changes in a branch against main/master/develop. It analyzes commits, integrates JIRA ticket and MR context when available, and produces a structured code review using Conventional Comments format.
SKILL.mdUpdated Apr 1, 2026
alexismanuel/workflow-research-codebase
development
VerifiedTrustedCommunity
This skill should be used when conducting comprehensive codebase research to answer questions, understand architecture, or prepare context for implementation planning. It spawns parallel sub-agents and synthesizes findings into a structured research document.
SKILL.mdUpdated Apr 1, 2026