skill-npbuilds-skill-library-problem-decomposition · by Install
$ agentstack add skill-npbuilds-skill-library-problem-decomposition ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-npbuilds-skill-library-problem-decomposition) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Problem Decomposition — Director
A diagnosed problem is rarely atomic. This director realizes six-eyes' Phase 3 (Decompose): it selects the right root-cause method for the problem's typology and stakes, tags each piece as root vs. symptom, and grounds the work in Polya's problem-solving heuristics. The goal is a set of atomic, root-tagged claims that downstream reframing and audit can operate on cleanly.
Decomposition partners with the research domain's claim-decomposer (cross-domain) for atomic-claim extraction; this director focuses on root-cause structure — which split is causal, which is cosmetic.
Routing Table
| Child skill | Use when | Output | |---|---|---| | root-vs-symptom-tagger | You need to pick a root-cause method (5 Whys / Fishbone / dependency map / Current Reality Tree) and tag each part root vs. symptom | Method choice + per-claim root/symptom tags | | polya-method | You need the heuristic basis for understand → plan → execute → look-back, or specialize/generalize moves | Reference: Polya's How to Solve It catalog |
Routing Logic
- Take the typology tag from
problem-diagnosis. It selects the method: dependency mapping for
mess, Current Reality Tree for wicked, 5 Whys / Fishbone for well- or ill-defined. root-vs-symptom-tagger performs this selection.
- Pull
polya-methodwhen the decomposition stalls — its specialize/generalize operations and
the "understand the problem" step often unstick a tangled statement.
- If decomposition yields 15+ atomic claims, hand back to
six-eyesto ask the user to
prioritize before continuing.
Scope Boundaries
- In scope: selecting a decomposition method, root vs. symptom tagging, Polya heuristics.
- Out of scope: classifying the problem (→
problem-diagnosis), generating alternative
formulations (→ problem-reframing).
- Cross-domain: atomic-claim extraction proper is
research/claim-decomposer; this director
routes to it via the orchestrator rather than duplicating it.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: npbuilds
- Source: npbuilds/skill-library
- License: MIT
- Homepage: https://skill-library-prod.web.app/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.