agentmods.dev

scopes: Command for Claude Code

.claude/commands/pm/epic-decompose.md

epic-decompose is a command for Claude Code from kamiazya/scopes. It costs 0 tokens per session (1,905 once invoked), scanned A, original, Apache-2.0.

A command that breaks a large planned feature, called an epic, into smaller task files.

In plain words
What is it for?
Use it to create numbered implementation tasks from an existing epic and check that the epic is valid before proceeding.
Why use it?
It turns a broad piece of work into concrete steps that are easier to assign and complete.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents.

This is kamiazya/scopes's own configuration. It tells Claude Code how to work on scopes 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 scopes configures →

not rated 2repo 11mo ago A scan 0 tokens original Apache-2.0
View source ↗ kamiazya/scopes
Reuse

Borrowing it

Nothing to install: this file belongs to kamiazya/scopes. 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/kamiazya/scopes/main/.claude/commands/pm/epic-decompose.md
Clone the repo
git clone --depth 1 https://github.com/kamiazya/scopes

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 epic-decompose

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/kamiazya/scopes/epic-decompose"><img src="https://agentmods.dev/badge/commands/kamiazya/scopes/epic-decompose.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 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,905 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.00000 $0.01905
Opus 5.5 $0.00000 $0.00762
Sonnet 5.5 $0.00000 $0.00381
Haiku 4.5 $0.00000 $0.00191

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

Security

Grade A, and why

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 2mo 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/pm/epic-decompose.md · 231 lines

How it starts

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

Epic Decompose

Break epic into concrete, actionable tasks.

Usage

/pm:epic-decompose <feature_name>

Required Rules

IMPORTANT: Before executing this command, read and follow:

  • .claude/rules/datetime.md - For getting real current date/time

Preflight Checklist

Before proceeding, complete these validation steps. Do not bother the user with preflight checks progress ("I'm not going to ..."). Just do them and move on.

  1. Verify epic exists:

    • Check if .claude/epics/$ARGUMENTS/epic.md exists
    • If not found, tell user: "❌ Epic not found: $ARGUMENTS. First create it with: /pm:prd-parse $ARGUMENTS"
    • Stop execution if epic doesn't exist

  2. Check for existing tasks:

    • Check if any numbered task files (001.md, 002.md, etc.) already exist in .claude/epics/$ARGUMENTS/
    • If tasks exist, list them and ask: "⚠️ Found {count} existing tasks. Delete and recreate all tasks? (yes/no)"
    • Only proceed with explicit 'yes' confirmation
    • If user says no, suggest: "View existing tasks with: /pm:epic-show $ARGUMENTS"

  3. Validate epic frontmatter:

    • Verify epic has valid frontmatter with: name, status, created, prd
    • If invalid, tell user: "❌ Invalid epic frontmatter. Please check: .claude/epics/$ARGUMENTS/epic.md"

  4. Check epic status:

    • If epic status is already "completed", warn user: "⚠️ Epic is marked as completed. Are you sure you want to decompose it again?"

Instructions

You are decomposing an epic into specific, actionable tasks for: $ARGUMENTS

1. Read the Epic

  • Load the epic from .claude/epics/$ARGUMENTS/epic.md
  • Understand the technical approach and requirements
  • Review the task breakdown preview

2. Analyze for Parallel Creation

Determine if tasks can be created in parallel:

  • If tasks are mostly independent: Create in parallel using Task agents
  • If tasks have complex dependencies: Create sequentially
  • For best results: Group independent tasks for parallel creation

3. Parallel Task Creation (When Possible)

Read the full file on GitHub · 231 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. 2mo ago First seen · 231 lines · 0 tokens per session scan A d6c926aa7388

Subscribe to this mod's changes

epic-decompose is a command published in the GitHub repository kamiazya/scopes (2 stars, last pushed 11mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,905 tokens. 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.

Planninghacktoberfestmcp-servertaskmanagementtodoapp
Related

epic-decompose compared with commands from other repositories

epic-decompose next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
epic-decomposekamiazya/scopesCommand211mo agoApache-2.0A0Claude Code
diagnose-deeptracezscaler/zscaler-mcp-serverCommand5510d agoMITA29Claude Code
troubleshoot-experiencezscaler/zscaler-mcp-serverCommand5510d agoMITA25Claude Code
app-healthzscaler/zscaler-mcp-serverCommand5510d agoMITA16Claude Code
compare-locationszscaler/zscaler-mcp-serverCommand5510d agoMITA20Claude Code
investigate-alertszscaler/zscaler-mcp-serverCommand5510d agoMITA23Claude Code
investigate-sandboxzscaler/zscaler-mcp-serverCommand5510d agoMITA30Claude Code