write-jira-story

write-jira-story is a skill for Claude Code from bitovi/cascade-mcp. It costs 102 tokens per session (2,118 once invoked), scanned B, original, MIT.

A workflow for writing or refining a Jira story using information from Figma designs, Confluence, Google Docs, and the parent epic. Jira is a tool for tracking work, and a story describes a piece of user-facing work.

In plain words
What is it for?
Use it to create or update a story with a user-story statement, feature scope, Gherkin acceptance criteria, non-functional requirements, and related details.
Why use it?
It brings scattered design and project context together so the story does not depend on incomplete notes from one source.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Part of the cascade-mcp plugin — 13 skills shipped together

Good fit Use it to create or update a story with a user-story statement, feature scope, Gherkin acceptance criteria, non-functional requirements, and related details.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bitovi/cascade-mcp/write-jira-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 bitovi/cascade-mcp --skill write-jira-story
Clone the repo
git clone --depth 1 https://github.com/bitovi/cascade-mcp

Made for: Claude Code.

Or install cascade-mcp, the plugin that ships this one along with the rest of its 13 skills.

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 write-jira-story

README.md
[![agentmods](https://agentmods.dev/badge/skills/bitovi/cascade-mcp/write-jira-story/github.svg)](https://agentmods.dev/skills/bitovi/cascade-mcp/write-jira-story)
Your own site
<a href="https://agentmods.dev/skills/bitovi/cascade-mcp/write-jira-story"><img src="https://agentmods.dev/badge/skills/bitovi/cascade-mcp/write-jira-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 write-jira-story

Your own site · 80×15
<a href="https://agentmods.dev/skills/bitovi/cascade-mcp/write-jira-story"><img src="https://agentmods.dev/badge/skills/bitovi/cascade-mcp/write-jira-story.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,118 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 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.00102 $0.02118
Opus 5 $0.00051 $0.01059
Sonnet 5 $0.00020 $0.00424
Haiku 4.5 $0.00010 $0.00212

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

Security

Grade B, and why

write-jira-story scanned grade B with 2 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 11d 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.

Sends data to an external URLmediumData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

curl -sL "{downloadUrl}" -o /tmp/cascade-figma.zip && unzip -qo /tmp/cascade-figma.zip -d .temp/cascade/figma/ && rm /tmp/cascade-figma.zip

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sL "{downloadUrl}" -o /tmp/cascade-figma.zip && unzip -qo /tmp/cascade-figma.zip -d .temp/cascade/figma/ && rm /tmp/cascade-figma.zip
plugins/cascade-mcp/skills/write-jira-story/SKILL.md · 183 lines

How it starts

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

Write Story

Write or refine a Jira story description using comprehensive context from all linked sources (Figma, Confluence, Google Docs, parent epic).

When to Use

Use when the user wants to:

  • Write a new story description from Figma designs and specs
  • Refine an existing story with newly available context (answered questions, updated designs)
  • Re-run story writing to incorporate inline answers (❓ → 💬 flipping)

Typical triggers:

  • "Write the story for PROJ-456"
  • "Update PROJ-456 with the latest design context"
  • "Refine this story — questions have been answered"

Required Input

  • Jira issue key (e.g., PROJ-456) — the story to write/refine

Procedure

Phase 1: Fetch the Starting Issue

Call MCP tool extract-linked-resources with the Jira issue URL (e.g., https://myco.atlassian.net/browse/PROJ-456).

Save the returned markdown+frontmatter directly to .temp/cascade/context/jira-PROJ-456.md.

Parse discoveredLinks from frontmatter to build .temp/cascade/context/to-load.md.

Phase 2: Iterative Content Loading

For each non-Figma URL in to-load.md (prioritize parent and blocks relationships first):

  1. Call extract-linked-resources with the URL
  2. Save the returned markdown to .temp/cascade/context/{type}-{identifier}.md
  3. Parse discoveredLinks from frontmatter — add any new URLs to to-load.md
  4. Repeat until no unloaded non-Figma URLs remain

Phase 3: Figma Batch Load

For each Figma URL:

  1. Call figma-batch-zip with the URL
    • This returns a downloadUrl and manifest
  2. Try to download and extract:
    curl -sL "{downloadUrl}" -o /tmp/cascade-figma.zip && unzip -qo /tmp/cascade-figma.zip -d .temp/cascade/figma/ && rm /tmp/cascade-figma.zip
    
  3. If curl fails (e.g., DNS blocked in cloud environments):
    • Call figma-batch-cache with the same Figma URLs
    • Note the batchToken and manifest from the response

Phase 4: Parallel Frame Analysis

Choose the matching path based on Phase 3 outcome:

Read the full file on GitHub · 183 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 11d ago First seen · 183 lines · 102 tokens per session scan B 97dfa56736e2

Subscribe to this mod's changes

write-jira-story is a skill published in the GitHub repository bitovi/cascade-mcp (24 stars, last pushed 21d ago), licensed MIT. It adds 102 tokens to every session and 2,118 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

huashu-keynote-black

OpenDesign's all-hands: the year in review, the three priorities, and what every team owns next quarter. Built as a decision-grade corporate strategy deck for whole company.

nexu-io/open-design · 43 tokens

kanban-board

A Kanban board is a visual task list with columns for stages such as To do, In progress, In review, and Done. It can show filters, labels, due dates, assignees, comments, and swimlanes that group cards.

nexu-io/html-anything · 26 tokens

acid-blue-business

A visual presentation style for modern business topics, using electric blue with black, white, and grey, directional layouts, and clear spacing. It is intended for business content rather than traditional data dashboards.

arcsin1/oh-my-ppt · 0 tokens

design-inventory

Use to run the Claude Design to ClosedLoop pipeline against the current web-ui. Stage A inventories a design export zip into schema-validated findings (typed design units - screens, regions like nav bars, standalone components like a chat dialog; UX and behavioral changes; Storybook component reuse mapping; token…

closedloop-ai/claude-plugins · 173 tokens

visual-dashboard

Start a browser-based dashboard that visualizes architecture, implementation plans, and project status. Persists artifacts in .bigpowers/dashboard/. Reads specs/state.yaml, release-plan.yaml, epics, and planning-status via HTTP API or opencode panel.

danielvm-git/bigpowers · 52 tokens

contribution-workflow

Create or document a contribution workflow for a design system — the multi-stage process for evaluating, accepting, and shepherding new contributions through to publication. Trigger when someone says: how should someone contribute, contribution process, adding a new component, contribution guidelines, what's the…

murphytrueman/design-system-ops · 99 tokens