Agent skill

Plan Create Stories

by coleam00 in coleam00/skills

Decomposes a PRD into well-formed, engineer-ready tickets — Jira issues or GitHub issues.

MITAuto-check passedProduct & Project Management

Install Plan Create Stories

skills CLI
$ npx skills add coleam00/skills --skill plan-create-stories -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install coleam00/skills plan-create-stories --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/coleam00/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/plan-create-stories .claude/skills/plan-create-stories && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
plan-create-stories
GitHub stars
674
Token cost
~922 tokens
SKILL.md length
474 words
Files
1
Skills in repo
34
Repo updated
First seen
Licence
MIT

At a glance

Decomposes a PRD into well-formed, engineer-ready tickets — Jira issues or GitHub issues.

  • Works in 4 steps: Read and decompose the PRD → Confirm the plan before creating anything → Create the tickets — branch on --platform → …
  • Tasks that involve PRD writing
  • SKILL.md covers Overview, Arguments, Workflow and Quality Checks, plus 1 more section
  • Calls gh

What it does

Plan Create Stories is an agent skill from coleam00/skills. Decomposes a PRD into well-formed, engineer-ready tickets — Jira issues or GitHub issues. Use after a PRD exists, to turn its phases and user stories into a structured backlog. Works for a new codebase (MVP scope) or an existing one (epic scope).

Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering PRD writing and User stories. It works with GitHub and Jira. The repository describes itself as: The agent skills I actually use to build software with coding agents. The PIV loop, planning, worktrees, and the meta-skills for building your own AI Layer. The licence is MIT.

When your agent uses it

  • Tasks that involve PRD writing
  • Tasks that involve User stories

Example prompts

  • “Use the plan-create-stories skill to decompose a PRD into well-formed, engineer-ready tickets — Jira issues or GitHub issues”
  • “/plan-create-stories”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Read and decompose the PRD
  2. Confirm the plan before creating anything
  3. Create the tickets — branch on --platform
  4. Report

What it can do on your machine

Read from SKILL.md and the folder at commit 847be08. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Plan Create Stories loads about 922 tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 474 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~67
When it runs · the whole SKILL.md, loaded when a task matches
~922

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from coleam00/skills at commit 847be08, republished under its MIT licence (© coleam00). 474 words, ~922 tokens.

Download SKILL.mdSave it as .claude/skills/plan-create-stories/SKILL.md (or your agent's skills folder).
name
plan-create-stories
description
Decomposes a PRD into well-formed, engineer-ready tickets — Jira issues or GitHub issues. Use after a PRD exists, to turn its phases and user stories into a structured backlog. Works for a new codebase (MVP scope) or an existing one (epic scope).
argument-hint
<prd-path> --platform <jira|github> [--project KEY] [--epic KEY] [--milestone NAME]

Create Stories: PRD → Ticket Backlog

Overview

Turn a finished PRD into a backlog of small, well-formed tickets. Each Implementation Phase in the PRD becomes a group of tickets; each User Story becomes one or more tickets with explicit acceptance criteria.

This skill is platform-agnostic by design — the --platform flag decides whether the backlog lands in Jira or in GitHub Issues. Everything before that flag (reading the PRD, decomposing it, writing acceptance criteria) is identical.

Arguments

ArgumentRequiredMeaning
<prd-path>yesPath to the PRD produced by plan-create-prd
--platformyesjira or github — where the tickets are created
--projectjira onlyJira project key (e.g. HELP)
--epicjira onlyJira epic key to parent the tickets under (e.g. HELP-1)
--milestonegithub onlyoptional GitHub milestone to attach issues to

If --platform is missing, stop and ask — do not guess.

Workflow

1. Read and decompose the PRD
  • Read <prd-path> in full.
  • Walk the Implementation Phases section. Each phase is a ticket group.
  • Walk the User Stories section. Each story maps to one ticket (split if it hides more than ~a day of work).
  • For every ticket, draft:
    • Title — imperative, specific (Add token refresh endpoint, not Auth).
    • Description — what and why, linked back to the PRD phase.
    • Acceptance criteria — a checklist a reviewer can verify.
    • Phase label — which PRD phase it belongs to.
  • Keep tickets small. A ticket that can't be described in one screen is two tickets.
2. Confirm the plan before creating anything

Print the proposed ticket list (titles + phase grouping) and the target platform. This is the checkpoint — creating real tickets is not reversible in one click.

Show full SKILL.md (207 more words)Show less
3. Create the tickets — branch on --platform

--platform jira:

  • Use the Atlassian MCP server.
  • Create each ticket under --epic in --project.
  • Map: PRD phase → a label or the epic; acceptance criteria → the description.
  • Capture each created issue key.

--platform github:

  • Use the gh CLI: gh issue create --title "..." --body "..." [--label phase-N] [--milestone "..."].
  • Put acceptance criteria in the issue body as a markdown checklist.
  • Apply a phase-N label per PRD phase (create the label if missing with gh label create).
  • Capture each created issue number/URL.
4. Report
  • A table: ticket title → phase → created key/number/URL.
  • The PRD path the backlog was generated from.
  • Next step: each phase is now ready to run as a PIV loop.

Quality Checks

  • ✅ Every ticket traces back to a PRD phase or user story
  • ✅ Every ticket has verifiable acceptance criteria
  • ✅ Tickets are small (≤ ~1 day of work)
  • ✅ The correct platform was used and every create succeeded
  • ✅ Phase grouping is preserved (labels/epic) so the backlog stays navigable

Notes

  • Greenfield vs brownfield changes the PRD's scope (MVP vs next epic), not this skill — plan-create-stories runs the same either way.
  • Never create tickets without the step-2 confirmation.
  • If a phase is too vague to decompose, stop and flag it — that's a PRD gap, not a ticket-writing problem.

© coleam00, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/plan-create-stories of coleam00/skills.

Open the folder on GitHubat commit 847be08

Compare with similar skills

Plan Create Stories next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Plan Create Stories compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Plan Create Stories this skillcoleam00/skills674—~922Automated safety check: PassMIT
To Prdayoubben18/ab-method192—~615Automated safety check: PassMIT
Create User Storyhuytieu/COG-second-brain1.3k—~2kAutomated safety check: PassMIT
Notion Pmborghei/Claude-Skills886—~1.7kAutomated safety check: PassMIT
To Specsammcj/agentic-coding162—~665Automated safety check: PassApache-2.0
Project Managementseb1n/awesome-ai-agent-skills206—~2.7kAutomated safety check: PassMIT

Similar skills

  • To Prd

    ayoubben18/ab-method

    Turn the current conversation context into a PRD and submit it as a GitHub issue.

    192 GitHub stars~615 tokensUpdated 8 days ago
    Product & Project ManagementAuto-check passed
  • Create User Story

    huytieu/COG-second-brain

    Create user stories with duplicate checking across any project tracker (Linear, GitHub Issues, Jira)

    1.3k GitHub stars~2k tokensUpdated 6 days ago
    Product & Project ManagementAuto-check passed
  • Notion Pm

    borghei/Claude-Skills

    Notion expert for product management workflows. An agent skill from borghei/Claude-Skills.

    886 GitHub stars~1.7k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed
  • To Spec

    sammcj/agentic-coding

    Turn the current conversation context into a spec and submit it as a GitHub issue.

    162 GitHub stars~665 tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Project Management

    seb1n/awesome-ai-agent-skills

    Manages software projects end-to-end — decomposing work into tasks, tracking progress across sprints, generating status reports, and integrating with tools like Jira, Linear, GitHub Issues, and…

    206 GitHub stars~2.7k tokensUpdated 2 mo ago
    Product & Project ManagementAuto-check passed
  • Product Manager

    revfactory/harness-100

    A full PM pipeline where an agent team collaborates to generate roadmaps, PRDs, user stories, sprint plans, and retrospectives in one go.

    1.3k GitHub stars~1.7k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

More from coleam00/skills

All 34 skills in this repo
  • Ablate AI Layer

    coleam00/skills

    Measure whether a repository's AI instructions still earn their place, by running the same real task many times with the layer intact and with it stripped, then grading every rule against what…

    674 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Build Dark Factory

    coleam00/skills

    Take a PRD and build a dark factory around it - a repository that takes work in as an issue and ships validated code out with nobody at the keyboard - one component at a time, into the user's actual…

    674 GitHub stars~12k tokensUpdated yesterday
    Auto-check passed
  • Drive Screen

    coleam00/skills

    Take real control of the desktop - list and focus windows, type, paste, click, scroll, and screenshot - on Windows, macOS or Linux, and drive other coding-agent sessions running in terminals.

    674 GitHub stars~5.4k tokensUpdated yesterday
    Auto-check passed
  • Second Brain Audit

    coleam00/skills

    Audit any second brain, notes folder, or agent memory for facts that have quietly stopped being true, then fix the worst one so it stops recurring.

    674 GitHub stars~4.6k tokensUpdated yesterday
    Auto-check passed
  • Build Signal Engine

    coleam00/skills

    Build a personal signal engine from scratch - a system that reads every source someone cares about each day (changelogs and release notes, communities, feeds, videos, papers), makes a quick decision…

    674 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Worktree Create

    coleam00/skills

    Create one or more git worktrees for parallel development, each on its own branch with gitignored config copied in, dependencies installed, and a health check, by fanning out a setup subagent per…

    674 GitHub stars~958 tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Plan Create Stories

What does Plan Create Stories do?

Decomposes a PRD into well-formed, engineer-ready tickets — Jira issues or GitHub issues. Plan Create Stories is an agent skill from coleam00/skills. Decomposes a PRD into well-formed, engineer-ready tickets — Jira issues or GitHub issues.

When should I use Plan Create Stories?

Plan Create Stories fits situations like: tasks that involve PRD writing; tasks that involve User stories.

How do I install Plan Create Stories in Claude Code?

Run `npx skills add coleam00/skills --skill plan-create-stories -a claude-code`. Or copy the skill folder (.claude/skills/plan-create-stories in coleam00/skills) into .claude/skills/plan-create-stories in your project. Claude Code loads it when a task matches its description.

How do I install Plan Create Stories in Codex?

Run `npx skills add coleam00/skills --skill plan-create-stories -a codex`. Or copy the skill folder (.claude/skills/plan-create-stories in coleam00/skills) into .agents/skills/plan-create-stories in your project. Codex loads it when a task matches its description.

Can I use Plan Create Stories in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add coleam00/skills --skill plan-create-stories -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plan-create-stories, .gemini/skills/plan-create-stories, .github/skills/plan-create-stories and .opencode/skills/plan-create-stories in your project.

What does Plan Create Stories need to run?

Going by SKILL.md and its folder, Plan Create Stories needs the command-line tools its instructions call (gh).

Does Plan Create Stories access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Plan Create Stories safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Plan Create Stories use?

Plan Create Stories is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Plan Create Stories use?

About 922 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Plan Create Stories?

Skills that share tags, products or a category with Plan Create Stories: To Prd (ayoubben18/ab-method, 192 stars), Create User Story (huytieu/COG-second-brain, 1.3k stars), Notion Pm (borghei/Claude-Skills, 886 stars) and To Spec (sammcj/agentic-coding, 162 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Plan Create Stories?

coleam00 (a GitHub user) maintains it in coleam00/skills, which has 674 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on October 7, 2026.

Source: coleam00/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.