plan-create-stories

Decomposes a PRD into engineer-ready Jira or GitHub issue tickets with acceptance criteria.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/az9713/claude-code-hooks-tutorial --skill plan-create-stories-az9713
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-create-stories
Source: https://github.com/az9713/claude-code-hooks-tutorial/tree/main/skills/.claude/skills/plan-create-stories
Command: npx skills add https://github.com/az9713/claude-code-hooks-tutorial --skill plan-create-stories-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a finished PRD into an actionable backlog is slow and error-prone: tickets end up too large, lack acceptance criteria, or lose traceability to the original requirements. This Skill automates the decomposition of a PRD's implementation phases and user stories into small, verifiable tickets on Jira or GitHub. ## Core Features & Use Cases - PRD Decomposition: Reads a PRD and maps each Implementation Phase to a ticket group and each User Story to one or more tickets with titles, descriptions, and acceptance criteria. - Dual Platform Support: Creates tickets in Jira via the Atlassian MCP server (with project and epic keys) or in GitHub via the gh CLI (with phase labels and optional milestones). - Confirmation Checkpoint: Prints the proposed ticket list for approval before creating anything, since ticket creation is not easily reversible. - Use Case: After writing a PRD for a new authentication feature, run this Skill to generate a backlog where each ticket traces back to a PRD phase, carries a verifiable acceptance checklist, and is small enough to complete in about a day. ## Quick Start Ask the agent to create stories from docs/prd-auth.md on GitHub with a milestone, and it will decompose the PRD, show the ticket plan for confirmation, and create the issues.

Frequently Asked Questions about plan-create-stories

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a PRD into Jira or GitHub tickets?▼

Provide the PRD path and a platform flag (jira or github). The Skill reads the PRD, maps each implementation phase and user story to tickets with acceptance criteria, shows the plan for confirmation, then creates the tickets via the Atlassian MCP server or the gh CLI.

How to create GitHub issues from a PRD with the gh CLI?▼

The Skill runs gh issue create with a title, body containing a markdown acceptance-criteria checklist, a phase-N label per PRD phase, and an optional milestone. It creates missing labels with gh label create and captures each issue number and URL.

Does it support both Jira and GitHub issue creation?▼

Yes, the --platform flag selects the target. Jira mode uses the Atlassian MCP server and requires a project key and epic key; GitHub mode uses the gh CLI with optional milestone. If the flag is missing, the Skill stops and asks rather than guessing.

Will it create tickets without my approval first?▼

No. Step 2 of the workflow prints the proposed ticket list with titles and phase grouping and waits for confirmation, because creating real tickets is not reversible in one click. Tickets are never created without this checkpoint.

What happens if a PRD phase is too vague to decompose?▼

The Skill stops and flags the phase as a PRD gap instead of inventing tickets. Vague phases are treated as a requirements problem to fix in the PRD, not a ticket-writing problem to work around.