agentmods.dev

Draft a story markdown from a story tracker or feature description

Draft a story markdown from a story tracker or feature description is a skill for Claude Code from Intai/story-flow. It costs 35 tokens per session (2,864 once invoked), scanned A, original, MIT.

A tool that turns a feature request or work ticket into a draft Markdown document describing the development work. It can examine linked Figma designs and the codebase for relevant details.

In plain words
What is it for?
Use it to prepare draft technical stories from Jira, ClickUp, Azure DevOps, or a written feature description, then review and refine the result.
Why use it?
It gives developers a structured starting point instead of requiring them to gather requirements and plan the work from scratch.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions subagents; names the AskUserQuestion tool.

Part of the junior-flow plugin — 4 skills, 2 commands shipped together

not rated 12repo changed 2d ago A scan SkillSpector: pass 35 tokens original MIT

Good fit Use it to prepare draft technical stories from Jira, ClickUp, Azure DevOps, or a written feature description, then review and refine the result.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/intai/story-flow/draft-story-markdown
View source ↗ Intai/story-flow
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 Intai/story-flow --skill draft-story-markdown
Clone the repo
git clone --depth 1 https://github.com/Intai/story-flow

Made for: Claude Code.

Or install junior-flow, the plugin that ships this one along with the rest of its 4 skills, 2 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 Draft a story markdown from a story tracker or feature description

README.md
[![agentmods](https://agentmods.dev/badge/skills/intai/story-flow/draft-story-markdown/github.svg)](https://agentmods.dev/skills/intai/story-flow/draft-story-markdown)
Your own site
<a href="https://agentmods.dev/skills/intai/story-flow/draft-story-markdown"><img src="https://agentmods.dev/badge/skills/intai/story-flow/draft-story-markdown/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 Draft a story markdown from a story tracker or feature description

Your own site · 80×15
<a href="https://agentmods.dev/skills/intai/story-flow/draft-story-markdown"><img src="https://agentmods.dev/badge/skills/intai/story-flow/draft-story-markdown.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,864 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00035 $0.02864
Opus 5 $0.00017 $0.01432
Sonnet 5 $0.00007 $0.00573
Haiku 4.5 $0.00003 $0.00286

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

Security

Grade A, and why

Draft a story markdown from a story tracker or feature description 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/junior-flow/skills/draft-story-markdown/SKILL.md · 239 lines

How it starts

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

Draft a story markdown from a story tracker or feature description

Overview

This skill helps junior developers create technical story markdown by:

  1. Gathering requirements from a story tracker or a provided feature description
  2. Fetching Figma designs linked in the story (when applicable)
  3. Exploring the codebase to discover relevant files and patterns
  4. Generating a draft story.md for the developer to review and refine

Instructions

Phase 1: Gather Requirements

Option A: Ticket ID provided

When the input is a ticket ID (matching a pattern like PROJ-123, 86d2uf1mh, 4821, AB#4821). A bare integer is always a ticket ID, never a feature description:

  • Use the project's story tracker MCP tools (Jira, ClickUp, Azure DevOps) to fetch the story by its ticket ID and download its attachments. If no story tracker MCP tool is available, tell the developer the project has no story tracker MCP server configured (/mcp to check status) and ask them to paste the story details or provide a feature description instead — never guess at the story content.
  • Extract:
    • Type (Story, Task, Bug/Defect, etc.)
    • Summary (user story statement)
    • Description (context and background)
    • Acceptance criteria (requirements)
    • Subtasks (if any)
    • Figma links (URLs matching figma.com/file/ or figma.com/design/)
    • Steps to reproduce, actual and expected behaviour (bug tickets)
  • Treat the ticket as a bug when its type is Bug, Defect, Incident or equivalent, or when it carries steps to reproduce with actual and expected behaviour.
  • If the ticket is a bug, reproduce it before drafting. Follow its steps to reproduce by driving the app with mcp__plugin_story-flow_playwright__* tools, or mcp__plugin_story-flow_appium__* for a mobile app. Navigate relative to the base URL from BASE_URL, falling back to use.baseURL in the project's @playwright.config.js. Note the failing step, the actual behaviour and any console or network errors, and use them to inform the exploration keywords in Phase 2 and the tasks in Phase 3.
  • If the bug does not reproduce, carry on drafting and highlight it as an assumption in Phase 4 for the developer to confirm the environment, version, account or seed data.
  • If the fetch fails, inform the developer and ask them to verify:
    • The ticket ID is correct
    • The project's .mcp.json defines a story tracker MCP server, and they are logged into it (/mcp to check status)

Read the full file on GitHub · 239 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 Changed 6f845bd3a3c0
  2. 4d ago Changed · +9 lines 9c9e76728eb8
  3. 10d ago First seen · 230 lines · 35 tokens per session scan A de0a010922cb

Subscribe to this mod's changes

Draft a story markdown from a story tracker or feature description is a skill published in the GitHub repository Intai/story-flow (12 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 2,864 once invoked, about $0.0002 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-08-30.

Claude CodePlanningWriting and docsagenticautomationbddclaudeqa
Related

Other skills, from other repositories

automation

Instructions for managing scheduled tasks through the host's structured automation tool, including reminders, delayed work, recurring checks, and result delivery.

nexus-research-lab/nexus · 76 tokens

find-leads

Find qualified B2B leads with OpenOutreach — run openoutreach find N [emails], read the CSV it prints on stdout, and hand the rows to whatever sends. Use when the user wants leads, prospects, an ICP-matched contact list, or asks what a campaign already has. Also covers first-run setup (openoutreach init), openoutreach…

eracle/OpenOutreach · 0 tokens

flame-harness-evaluator

Phase 6 — skeptical QA. Run the game, watch it, then judge against the contract. Default = functional check; --strict adds quality and edge-case passes.

tjdrhs90/flutter-flame-harness · 41 tokens

flame-harness-submit

Phase 10 — upload store text metadata + categories via fastlane, then pause with exact manual steps for the final iOS review submission and Android production promotion.

tjdrhs90/flutter-flame-harness · 38 tokens

flame-harness-design

Phase 3 — define the Flutter designtokens.dart spec (palette, typography, spacing), the game's art/visual concept, and the asset/audio sourcing plan.

tjdrhs90/flutter-flame-harness · 38 tokens

flame-harness-screenshot

Phase 9 — capture store screenshots in the game's configured locales via integrationtest (ads hidden), fill ASO keywords, and upload via fastlane.

tjdrhs90/flutter-flame-harness · 37 tokens