reqdev:decompose

A command for breaking a system-level component into smaller components and assigning its requirements to them.

In plain words
What is it for?
Use it during requirements engineering to decompose a baselined subsystem before developing requirements for its sub-components.
Why use it?
It turns a broad design into manageable parts and checks that every parent requirement is covered.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/ddunnock/claude-plugins/reqdev.decompose
Clone the repo
git clone --depth 1 https://github.com/ddunnock/claude-plugins
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,245 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00019 $0.01245
Opus 5 $0.00010 $0.00622
Sonnet 5 $0.00004 $0.00249
Haiku 4.5 $0.00002 $0.00125

Measured 2d ago against content hash 4e596f621775, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

reqdev: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 2d 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.

skills/requirements-dev/commands/reqdev.decompose.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/reqdev:decompose - Subsystem Decomposition

Decomposes a baselined system-level block into sub-blocks, allocates parent requirements to sub-blocks, and validates allocation coverage. Sub-blocks then become available for requirements development via /reqdev:requirements.

Approve? (yes/edit/add more) User approves sub-block definitions.

Read the full file on GitHub · 116 lines

Changes

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.

  1. 2d ago First seen · 116 lines · 19 tokens per session scan A 4e596f621775

Subscribe to this mod's changes

reqdev:decompose is a command published in the GitHub repository ddunnock/claude-plugins (12 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 1,245 once invoked, about $0.0001 per session on Opus 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-30.