agentmods.dev

jira-breakdown

jira-breakdown is a command for Claude Code from HigorAlves/orc. It costs 20 tokens per session (2,241 once invoked), scanned A, original, MIT.

A command that turns a feature brief, product requirements document, or existing Jira Epic into a reviewed hierarchy of Jira work items. An Epic is a large body of work, while Stories and Tasks are smaller pieces within it.

In plain words
What is it for?
Use it to draft an Epic with Stories and Tasks, adjust the breakdown for team size, preview the result, or attach child tickets to an existing Epic.
Why use it?
It helps teams prepare a structured backlog for parallel development while keeping control over what gets created.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the orc plugin — 88 skills, 30 commands, 14 agents, 6 hooks shipped together

not rated 7repo changed 9d ago A scan 20 tokens original MIT

Good fit Use it to draft an Epic with Stories and Tasks, adjust the breakdown for team size, preview the result, or attach child tickets to an existing Epic.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/higoralves/orc/jira-breakdown
View source ↗ HigorAlves/orc orc.novacstack.com
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.

Clone the repo
git clone --depth 1 https://github.com/HigorAlves/orc

Made for: Claude Code.

Or install orc, the plugin that ships this one along with the rest of its 88 skills, 30 commands, 14 agents, 6 hooks.

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 jira-breakdown

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/higoralves/orc/jira-breakdown"><img src="https://agentmods.dev/badge/commands/higoralves/orc/jira-breakdown.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,241 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.00020 $0.02241
Opus 5.5 $0.00008 $0.00896
Sonnet 5.5 $0.00004 $0.00448
Haiku 4.5 $0.00002 $0.00224

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

Security

Grade A, and why

jira-breakdown 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 9d 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.

orc/commands/jira-breakdown.md · 149 lines

How it starts

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

/orc:jira-breakdown

A feature is coming and the team needs to swarm it. This command builds the Jira structure that makes that possible — per the orc:jira-hierarchy contract (invoke it first; it defines the levels, the micro-PRD sections, the mandatory child template, and the atomization rules). orc-jira-architect drafts the hierarchy; nothing is created until you approve the preview.

Arguments

  • Free-form input — a feature brief, a docs/prds/NNNN-*.md path, or a plan file. With --epic, input is optional (the epic's own description is the material).
  • --epic <KEY> — attach children to this existing Epic instead of drafting a new one.
  • --project <KEY> — Jira project. Resolution order: this flag → docs/agents/issue-tracker.md (written by /orc:setup) → the bound session ticket's project → ask.
  • --team-size <n> — how many developers will work in parallel (drives atomization aggressiveness; default 3).
  • --dry-run — stop after the preview; create nothing.

Workflow

Phase 0 — Detect + backend preflight

!orc-workspace-detect --banner

Context is injected above (ORC_* vars are exported — do not re-run detection).

Pick the Jira backend:

  1. Jira MCP tools present in the session (tool names matching mcp__*jira* / mcp__*atlassian* with work-item write capability) → prefer them.
  2. Else acli: invoke orc:jira-cli, then acli jira auth status. Non-zero → surface the auth-login hint and stop.
  3. Neither → stop: point at orc install / acli setup and /orc:setup for tracker config. Never fake a creation.

Phase 1 — Resolve project + parent Epic

  1. Resolve the project key per the order above. Validate ^[A-Z][A-Z0-9_]*$.
  2. Resolve the Epic:
    • --epic <KEY> → fetch it (acli jira workitem view <KEY> --json or MCP equivalent). It must exist and be active (status not Done/Closed/Resolved). Inactive or missing → surface and stop; children never attach to a dead Epic.
    • No --epic → search for candidates: JQL project = <KEY> AND issuetype = Epic AND statusCategory != Done filtered by input keywords. Then gate:

Read the full file on GitHub · 149 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. 9d ago Changed · +1 lines · -28 tokens per session b1789c43a925
  2. 24d ago Changed 4407be4a47f4
  3. 2mo ago First seen · 148 lines · 48 tokens per session scan A c57421d068e1

Subscribe to this mod's changes

jira-breakdown is a command published in the GitHub repository HigorAlves/orc (7 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 2,241 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.

Claude CodeProject managementagentic-codingai-agentsanthropicclaudeclaude-code-plugin
Related

Other commands, from other repositories

scout-meta-review

Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.

Raven-Scout/Scout · 61 tokens

scout-work

Interactive work session — walks through today's actionable items one at a time, presents a recommended action with draft content, and executes each one only with explicit approval. Runs in the current conversation (not as a background session).

Raven-Scout/Scout · 47 tokens

ccc-makeover

Score project health with X-Ray, apply the top recommendations in impact order with your OK for each, and show the before and after score. Use when you want the highest-impact project health fixes applied and measured.

KevinZai/commander · 47 tokens

execute

Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.

skullninja/coco-workflow · 28 tokens

dashboard

Compact visual progress dashboard with progress bar, task table, dependency graph, and active/blocked/next status.

skullninja/coco-workflow · 22 tokens

sync

Reconcile coco tracker state with the configured issue tracker. Syncs task statuses and reports mismatches.

skullninja/coco-workflow · 20 tokens