skills.rest
JHAMILCALI
JHAMILCALICOMMUNITY
Explore all skills by this author →
GitHub

create-epics-and-stories

Decompose PRD and architecture requirements into epics and user stories with acceptance criteria.

Updated Sep 6, 2026
Search Tags:#requirements#acceptance criteria#epics#user stories#backlog#prd#agile planning
One-click install
npx skills add https://github.com/JHAMILCALI/Stellar-Build --skill create-epics-and-stories-jhamilcali
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-epics-and-stories
Source: https://github.com/JHAMILCALI/Stellar-Build/tree/main/.claude/skills/create-epics-and-stories
Command: npx skills add https://github.com/JHAMILCALI/Stellar-Build --skill create-epics-and-stories-jhamilcali

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a PRD, architecture document, and UX design into an actionable backlog is slow and error-prone. This Skill guides a structured, step-by-step workflow that extracts every requirement and converts it into user-value-focused epics and developer-ready stories. ## Core Features & Use Cases - Requirements Extraction: Scans PRD, Architecture, and UX Design documents (whole or sharded) to inventory FRs, NFRs, and UX design requirements. - Epic Design: Groups requirements into standalone, user-value-driven epics with a full FR coverage map and file-churn consolidation checks. - Story Generation: Produces Given/When/Then acceptance criteria for each story, sized for a single dev agent with no forward dependencies. - Use Case: After finishing your PRD and architecture docs, run this Skill to produce a validated epics.md file that a developer agent can implement story by story. ## Quick Start Ask the AI to create the epics and stories list from your PRD and architecture documents.

Frequently Asked Questions about create-epics-and-stories

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

FAQPage Schema
How do I break a PRD into epics and user stories?▼

Provide your PRD, architecture, and optional UX design documents, then follow the guided workflow. It extracts all functional and non-functional requirements, groups them into user-value epics, and generates stories with acceptance criteria.

What documents are required to create epics and stories?▼

A PRD and an architecture document are required; a UX design document is optional but recommended. The workflow searches your planning artifacts folder for whole or sharded versions of each document before extraction begins.

How are acceptance criteria written for user stories?▼

Each story uses the Given/When/Then format with independently testable criteria, including edge cases and error conditions. Stories are sized so a single dev agent can complete them without depending on future stories.

Does the workflow validate requirements coverage?▼

Yes, a final validation step checks that every FR maps to at least one story, epics are independently valuable, stories have no forward dependencies, and database entities are created only when needed.

Can I customize the epic creation workflow?▼

Yes, a customize.toml file supports team and user overrides for activation steps, persistent facts, and post-completion behavior. Overrides merge using structural rules where scalars override and arrays append.

Related Skills

Explore More Product & Management Skills→
ultraviollettnymphoultraviollettnympho
1

breakdown-epic-pm

Generates an Epic Product Requirements Document in Markdown from a high-level epic idea.

Community
Basic
cenconq25cenconq25
39

create-stories

Decompose an epic into story files with TR-ID references and ADR governance.

Community
Intermediate
abhilash-nandkumarabhilash-nandkumar

user-story-fundamentals

Capture user requirements into structured user stories with acceptance criteria.

Community
Intermediate
MichaelSolatiMichaelSolati

to-prd

Synthesize conversation and codebase context into structured PRDs and publish them to the issue tracker.

Community
Intermediate