Plan Create Stories

Community

coleam00

plan-create-stories

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).

Overview

Publisher	coleam00
Repository	`skills`
Skill name	`plan-create-stories`
Stars	678
Forks	184
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by coleam00 on GitHub. Read the source before you install it.

Installation

Install the Plan Create Stories AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/coleam00/skills/tree/main/.claude/skills/plan-create-stories
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/coleam00/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/.claude/skills/plan-create-stories .claude/skills/plan-create-stories

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Plan Create Stories in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Plan Create Stories on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Plan Create Stories is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Argument	Required	Meaning
`<prd-path>`	yes	Path to the PRD produced by `plan-create-prd`
`--platform`	yes	`jira` or `github` — where the tickets are created
`--project`	jira only	Jira project key (e.g. `HELP`)
`--epic`	jira only	Jira epic key to parent the tickets under (e.g. `HELP-1`)
`--milestone`	github only	optional 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.

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.

Frequently asked questions

What does the Plan Create Stories AI skill do?

Why use Plan Create Stories on TypingMind?

Because you install it once and use it with any model. Plan Create Stories is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Plan Create Stories in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/coleam00/skills/tree/main/.claude/skills/plan-create-stories. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Plan Create Stories?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Plan Create Stories?

As many as you like. As long as a model supports skills, you can use Plan Create Stories with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Plan Create Stories AI skill free?

Yes. It is published on GitHub by coleam00 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Bun Runtime

affaan-m

CommunityPopular

Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.

Competitive Report Structure

affaan-m

CommunityPopular

Use after benchmark-methodology has produced scored competitor profile cards. Assembles findings into a decision-grade report: landscape map, competitor profiles, benchmarking matrix, white-space…

Content Engine

Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content…

Crosspost

Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Create Stories: PRD → Ticket Backlog

Overview

Arguments

Workflow

1. Read and decompose the PRD

2. Confirm the plan before creating anything

3. Create the tickets — branch on --platform

4. Report

Quality Checks

Notes

Frequently asked questions

Related AI Skills

Set up your own AI workspace now

3. Create the tickets — branch on `--platform`