Borrowing it
Nothing to install: this file belongs to dixus/claudeframework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dixus/claudeframework/main/.claude/skills/decompose/SKILL.mdgit clone --depth 1 https://github.com/dixus/claudeframeworkWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/dixus/claudeframework/decompose)<a href="https://agentmods.dev/skills/dixus/claudeframework/decompose"><img src="https://agentmods.dev/badge/skills/dixus/claudeframework/decompose/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dixus/claudeframework/decompose"><img src="https://agentmods.dev/badge/skills/dixus/claudeframework/decompose.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00036 | $0.01795 |
| Opus 5.5 | $0.00014 | $0.00718 |
| Sonnet 5.5 | $0.00007 | $0.00359 |
| Haiku 4.5 | $0.00004 | $0.00179 |
Grade A, and why
decompose scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decompose concept documents in .claude/input/ into independent, shippable PRDs.
$ARGUMENTS is an optional name or focus hint. The primary source is .claude/input/.
Step 1 — Ingest all input materials
Read every file in .claude/input/ — documents, images, screenshots, PDFs, sketches, markdown, plain text. Treat them collectively as a single concept brief.
Also read:
CLAUDE.mdfor project context, tech stack, and conventions- All files in
.claude/context/for long-lived project references (schemas, API docs, glossaries)
Build a mental model of what the concept describes: the overall goal, the user-facing features, the technical components, and any constraints or priorities mentioned.
Step 2 — Identify feature boundaries
Analyze the concept and identify independent features — units of work that:
- Have a clear, single purpose — each delivers one user-visible capability or one infrastructure change
- Can be implemented without the others existing — no hard runtime dependency on another feature from this decomposition (soft dependencies like "uses the same data model" are fine)
- Can be reviewed and tested in isolation — each has its own validation criteria
- Touch mostly different files — overlap of 1-2 shared files (e.g., a route config, a nav menu) is acceptable, but features that modify the same core logic in conflicting ways should be merged or sequenced
For each candidate feature, note:
- A short name (kebab-case, suitable for filenames)
- Which parts of the concept it covers
- Which specific files it will likely create or modify (list paths —
/fleetuses these for conflict analysis) - Any dependencies on other features from this decomposition
Step 3 — Dependency analysis and ordering
Build a dependency graph between the identified features:
- Independent — can run in any order, no dependency
- Soft dependency — benefits from another feature existing first (e.g., a dashboard that shows data from a new API), but can be implemented with stubs or existing data
- Hard dependency — cannot be implemented until another feature ships (e.g., a feature that extends a new data model created by another feature)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed 56cb81f81641
- 2mo ago First seen · 222 lines · 36 tokens per session scan A c15428fadeee
decompose is a skill published in the GitHub repository dixus/claudeframework (10 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 1,795 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.