RAD_framework: Command for Claude Code

.claude/commands/architect/rad-epic-decompose.md

rad-epic-decompose is a command for Claude Code from seanrreid/RAD_framework. It costs 107 tokens per session (1,946 once invoked), scanned A, original, MIT.

An architect-only command that reads a GitHub epic and its child issues, then writes a draft document breaking the epic into smaller shaping stories. An epic is a large piece of planned work made up of related issues.

In plain words
What is it for?
Use it at the first shaping stage of a project to inspect an epic, summarize each child story, create an epic-level overview, and prepare an architect sign-off checklist.
Why use it?
It turns a broad issue into a structured view of the work before detailed research or implementation planning begins. It also checks that the current user has the architect role.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions AGENTS.md.

This is seanrreid/RAD_framework's own configuration. It tells Claude Code how to work on RAD_framework itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything RAD_framework configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node harness/cli.js label [N] draft.

Reuse

Borrowing it

Nothing to install: this file belongs to seanrreid/RAD_framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/seanrreid/RAD_framework/main/.claude/commands/architect/rad-epic-decompose.md
Clone the repo
git clone --depth 1 https://github.com/seanrreid/RAD_framework

Made for: Claude Code.

Wrote 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.

agentmods badge for rad-epic-decompose

README.md
[![agentmods](https://agentmods.dev/badge/commands/seanrreid/rad_framework/rad-epic-decompose/github.svg)](https://agentmods.dev/commands/seanrreid/rad_framework/rad-epic-decompose)
Your own site
<a href="https://agentmods.dev/commands/seanrreid/rad_framework/rad-epic-decompose"><img src="https://agentmods.dev/badge/commands/seanrreid/rad_framework/rad-epic-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.

agentmods 80×15 button for rad-epic-decompose

Your own site · 80×15
<a href="https://agentmods.dev/commands/seanrreid/rad_framework/rad-epic-decompose"><img src="https://agentmods.dev/badge/commands/seanrreid/rad_framework/rad-epic-decompose.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 107 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,946 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00107 $0.01946
Opus 5.5 $0.00043 $0.00778
Sonnet 5.5 $0.00021 $0.00389
Haiku 4.5 $0.00011 $0.00195

Measured 21d ago against content hash fca4d08a271b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

rad-epic-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 21d 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.

.claude/commands/architect/rad-epic-decompose.md · 206 lines

How it starts

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

rad-epic-decompose

Consume a GitHub epic issue and produce a per-child decomposition artifact the architect uses to shape the epic into deliverable work. This sits upstream of the RAD workflow at Gate 0: it shapes; it does not plan, research, or deliver.

The output is a discovery/shaping document — a structured read on each child story plus an epic-level rollup with an architect sign-off checklist. It is written but never auto-committed, never turned into plan files, and never flips any status.

Input

$ARGUMENTS is the epic issue number or URL. Examples: 42, #42, https://github.com/org/repo/issues/42.

If $ARGUMENTS is empty, stop:

✗ /rad-epic-decompose requires an epic issue number or URL.
  Usage: /rad-epic-decompose <issue-number-or-url>

Process

Step 1: Verify authority to decompose

This command is architect-only. Gate on the running user's role before any fetch or context read:

scripts/check-role.sh architect

If the script exits non-zero, stop. Do not fetch the epic, do not read context, do not write anything.

Step 2: Fetch the epic and its children

Only after the role gate passes, call the Wave 1 fetch script with the raw $ARGUMENTS value. The script normalizes a bare number, #NN, or a GitHub issue URL itself, so pass the argument through unchanged:

scripts/fetch-epic.sh "$ARGUMENTS"

The script emits a single JSON object on stdout:

{ "epic": { "number": …, "title": …, "body": …, "url": …, "milestone": …, "labels": […], "state": … },
  "children": [ { "number": …, "title": …, "body": …, "url": …, "milestone": …, "labels": […], "state": … }, … ] }

It is GitHub-only for v1 and exits non-zero with a clear message on any other platform or if gh/jq are missing (set RAD_PLATFORM only when testing). If the script exits non-zero, surface its message and stop — do not fabricate epic or child data.

Read the full file on GitHub · 206 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. 21d ago Changed · -5 lines fca4d08a271b
  2. 23d ago Changed · +1 lines af66b7e95559
  3. 2mo ago First seen · 210 lines · 107 tokens per session scan A 89d8d18d4351

Subscribe to this mod's changes

rad-epic-decompose is a command published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 4d ago), licensed MIT. It adds 107 tokens to every session and 1,946 once invoked, about $0.0004 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.