Create Jira Story

Create Jira Story is a skill for Claude Code, Codex from wangke19/gemini-ai-helpers. It costs 17 tokens per session (5,338 once invoked), scanned A, original, Apache-2.0.

A guide for creating Jira user stories with a clear title, user-focused description, and acceptance criteria. Acceptance criteria are the conditions that must be met for the work to be considered complete.

In plain words
What is it for?
It helps write structured stories describing who needs something, what they need, why they need it, and how completion will be checked.
Why use it?
It helps turn a vague request into an understandable piece of work that developers and reviewers can agree on.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps write structured stories describing who needs something, what they need, why they need it, and how completion will be checked.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wangke19/gemini-ai-helpers/create-story
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.

Any agent
npx skills add wangke19/gemini-ai-helpers --skill create-story
Clone the repo
git clone --depth 1 https://github.com/wangke19/gemini-ai-helpers

Made for: Claude Code, Codex.

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 Jira Story

README.md
[![agentmods](https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/create-story/github.svg)](https://agentmods.dev/skills/wangke19/gemini-ai-helpers/create-story)
Your own site
<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/create-story"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/create-story/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 Create Jira Story

Your own site · 80×15
<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/create-story"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/create-story.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,338 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.00017 $0.05338
Opus 5 $0.00009 $0.02669
Sonnet 5 $0.00003 $0.01068
Haiku 4.5 $0.00002 $0.00534

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

Security

Grade A, and why

Create Jira Story 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 7d 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.

extensions/jira/skills/create-story/SKILL.md · 766 lines

How it starts

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

Create Jira Story

This skill provides implementation guidance for creating well-structured Jira user stories following agile best practices, including proper user story format and comprehensive acceptance criteria.

When to Use This Skill

This skill is automatically invoked by the /jira:create story command to guide the story creation process.

Prerequisites

  • MCP Jira server configured and accessible
  • User has permissions to create issues in the target project
  • Understanding of the user story and acceptance criteria to be created

Reference Documentation:

⚠️ Summary vs Description: CRITICAL DISTINCTION

This is the #1 mistake when creating stories. The summary field and description field serve different purposes:

Summary Field (Issue Title)

  • SHORT, concise title (5-10 words maximum)
  • Action-oriented, describes WHAT will be done
  • Does NOT contain the full "As a... I want... So that..." format
  • Think of it as a newspaper headline

Good summary examples:

  • ✅ "Enable ImageTagMirrorSet configuration in HostedCluster CRs"
  • ✅ "Add automatic node pool scaling for ROSA HCP"
  • ✅ "Implement webhook validation for HostedCluster resources"

Bad summary examples:

  • ❌ "As a cluster admin, I want to configure ImageTagMirrorSet in HostedCluster CRs so that I can enable tag-based image proxying" (Full user story - belongs in description!)
  • ❌ "As a developer, I want to view metrics so that I can debug issues" (User story format - belongs in description!)

Description Field (Issue Body)

  • Contains the FULL user story format: "As a... I want... So that..."
  • Includes acceptance criteria
  • Includes additional context
  • Can be lengthy and detailed

Read the full file on GitHub · 766 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. 7d ago First seen · 766 lines · 17 tokens per session scan A e70441dad8c3

Subscribe to this mod's changes

Create Jira Story is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 5,338 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-03.