knoopx/task-decomposition
agent/skills/protocols/task-decomposition/SKILL.md
Break complex tasks into GIVEN/UNKNOWN/PLAN before taking action. Use when tasks have multiple steps, require planning, or involve multi-step reasoning.
$ install --global
skillsauthnpx skillsauth add knoopx/pi task-decompositionInstall 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: May 18, 2026, 6:41 AM124.8s1 file scanned
SKILL.md
- name:
- task-decomposition
- description:
- Break complex tasks into GIVEN/UNKNOWN/PLAN before taking action. Use when tasks have multiple steps, require planning, or involve multi-step reasoning.
- related:
- [research-protocol, cite-before-answer]
- token_cost:
- 140
Task Decomposition
Before taking ANY tool action, reply with a short decomposition:
GIVEN: <one line — what the prompt already states> UNKNOWN: <one or two items — what you need to find out> PLAN:
- <first tool action, concrete>
- <second tool action>
- <final answer step>
Rules
- Keep UNKNOWN to 1–2 items. If it grows past 2, split the task further in step 1
- Resolve one unknown fully before moving to the next — NEVER interleave
- After each tool call, check: did this resolve an UNKNOWN? If yes, strike it. If no, revise the PLAN
- ALWAYS write the decomposition before taking any tool action
- NEVER skip decomposition on multi-step tasks
Example
GIVEN: User wants to know when Turing machines were invented
UNKNOWN: Year of Turing machine invention
PLAN:
1. BrowserNavigate to Wikipedia article on Turing machines
2. BrowserExtract to find the invention date
3. evidence-add the fact and answer with citation
Workflow
- Write decomposition: Before any tool action, state GIVEN, UNKNOWN, and PLAN
- Limit unknowns: Keep to 1-2 unknowns; split further if more arise
- Resolve sequentially: Complete one unknown fully before moving to the next
- Check progress: After each tool call, verify if an unknown was resolved
- Revise plan: If a step doesn't resolve an unknown, adjust the plan accordingly
Related Skills
knoopx/notify
tools
VerifiedTrustedCommunity
Inform the user what is happening — skip passive lookups
52SKILL.mdUpdated May 20, 2026
knoopx/markdown-rendering
development
VerifiedTrustedCommunity
Renders markdown to self-contained HTML with a custom dark stylesheet and opens in browser. Use when previewing markdown documents, generating styled HTML from README or report files.
52SKILL.mdUpdated May 20, 2026
knoopx/jj-hunk
testing
VerifiedTrustedCommunity
Programmatic hunk selection for Jujutsu — split, commit, or squash specific hunks without interactive prompts. Use when making partial commits or selective squashes.
52SKILL.mdUpdated May 18, 2026
knoopx/jj-core
content-media
VerifiedTrustedCommunity
Manage version control with Jujutsu (jj) — no staging area, immediate changes, smart rebasing. Use when navigating history, squashing, or pushing to Git remotes.
52SKILL.mdUpdated May 18, 2026