agentmods.dev

create-plan-from-issue

create-plan-from-issue is a command for Claude Code from quay/ai-helpers. It costs 13 tokens per session (3,325 once invoked), scanned A, original, MIT.

A command that analyzes a JIRA bug or feature and produces an actionable implementation plan, including separate paths for user-interface and backend work.

In plain words
What is it for?
It is for classifying issues, reviewing screenshots, diagrams, logs, and test files, and organizing work needed to implement a change.
Why use it?
It gathers issue details, attachments, comments, and context before planning, so important evidence is less likely to be overlooked.

Command for Claude Code

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

Part of the jira plugin — 2 skills, 6 commands shipped together

not rated 3repo 19d ago A scan 13 tokens original MIT

Good fit It is for classifying issues, reviewing screenshots, diagrams, logs, and test files, and organizing work needed to implement a change.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/quay/ai-helpers/create-plan-from-issue
View source ↗ quay/ai-helpers
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/quay/ai-helpers

Made for: Claude Code.

Or install jira, the plugin that ships this one along with the rest of its 2 skills, 6 commands.

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 create-plan-from-issue

README.md
[![agentmods](https://agentmods.dev/badge/commands/quay/ai-helpers/create-plan-from-issue.svg)](https://agentmods.dev/commands/quay/ai-helpers/create-plan-from-issue)
Your own site
<a href="https://agentmods.dev/commands/quay/ai-helpers/create-plan-from-issue"><img src="https://agentmods.dev/badge/commands/quay/ai-helpers/create-plan-from-issue.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,325 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.00013 $0.03325
Opus 5 $0.00006 $0.01663
Sonnet 5 $0.00003 $0.00665
Haiku 4.5 $0.00001 $0.00332

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

Security

Grade A, and why

create-plan-from-issue 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.

plugins/jira/commands/create-plan-from-issue.md · 441 lines

How it starts

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

Create Plan from Issue

Systematically analyze a JIRA issue and create an actionable implementation plan. This command uses a modular phase-based approach that branches based on issue type (UI vs Backend).

Issue Key

The JIRA issue to plan: $ARGUMENTS

Phase 1: Discovery (All Issues)

Step 1: Fetch Issue Details

Retrieve the full issue information from JIRA:

acli jira workitem view $ARGUMENTS

Extract key information:

  • Issue type (Bug, Story, Task, etc.)
  • Summary and description
  • Component (ui, api, data, etc.)
  • Priority
  • Labels
  • Comments with additional context

Step 2: Download Attachments

Download any attachments from the issue:

.claude/scripts/download-jira-attachments.sh $ARGUMENTS

This script will:

  • Check if the issue has attachments
  • Download them to .claude/attachments/$ARGUMENTS/
  • Display file types to help identify their purpose

Common attachment types:

  • Screenshots/Images: Visual bugs or mockups
  • Architecture diagrams: Design documentation
  • Log files: Error traces or debugging information
  • Test files: Reproduction cases or examples

Step 3: Classify the Issue

Analyze the issue to determine if it's UI or Backend, considering both description and attachments:

UI Issue Indicators:

  • Component: ui or web
  • Keywords: rendering, display, UI, interface, button, form, modal, table, layout, styling, visual, PatternFly, React, Angular
  • Issue describes visual or interaction problems
  • Has screenshot/mockup attachments

Backend Issue Indicators:

  • Component: api, data, auth, endpoints, workers, buildman, storage
  • Keywords: API, endpoint, database, authentication, background job, storage, worker, migration, ORM, SQL
  • Has log files or stack traces attached
  • Describes data processing, API behavior, or system operations

Decision Point: Based on classification, proceed to either Phase 2-UI or Phase 2-Backend.

Phase 2: Type-Specific Preparation

Read the full file on GitHub · 441 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 · 441 lines · 13 tokens per session scan A b8fedaaf72bf

Subscribe to this mod's changes

create-plan-from-issue is a command published in the GitHub repository quay/ai-helpers (3 stars, last pushed 19d ago), licensed MIT. It adds 13 tokens to every session and 3,325 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-09-04.

PlanningProject management
Related

Other commands, from other repositories

template

Manage issue templates for streamlined issue creation.

gastownhall/beads · 0 tokens

sync-linear

Sync current work with Linear ticket status.

bybren-llc/safe-agentic-workflow · 0 tokens

add-note

Add an internal or external note to a ConnectWise PSA ticket.

WYRE-AI/msp-claude-plugins · 12 tokens

fest-show

Show festival progression (in-progress tasks, roadmap, and dependency view).

Obedience-Corp/festival · 17 tokens

dispatcher

Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.

Kanevry/session-orchestrator · 0 tokens

workpm

A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.

Dannykkh/skill-olympus · 31 tokens