# Plan Create Stories

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

- Repository: https://github.com/coleam00/skills (726 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add coleam00/skills --skill plan-create-stories -g -a claude-code -y`
Codex: `npx skills add coleam00/skills --skill plan-create-stories -g -a codex -y`
Cursor: `npx skills add coleam00/skills --skill plan-create-stories -g -a cursor -y`
Gemini CLI: `npx skills add coleam00/skills --skill plan-create-stories -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add coleam00/skills`

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

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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`

The rest: https://github.com/coleam00/skills/blob/HEAD/.claude/skills/plan-create-stories/SKILL.md