create-epics-and-stories

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

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/chrissstellee/Movix --skill create-epics-and-stories-chrissstellee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-epics-and-stories
Source: https://github.com/chrissstellee/Movix/tree/main/.agents/skills/create-epics-and-stories
Command: npx skills add https://github.com/chrissstellee/Movix --skill create-epics-and-stories-chrissstellee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a PRD, architecture document, and UX specification into an actionable backlog is slow and error-prone, often leaving requirements uncovered or stories with unclear acceptance criteria. This Skill guides a structured, step-by-step workflow that extracts every requirement and converts it into validated epics and stories ready for a developer agent. ## Core Features & Use Cases - Requirements Extraction: Scans PRD, Architecture, and UX Design documents to extract functional requirements, non-functional requirements, and UX design requirements into a requirements inventory. - Epic Design with Coverage Mapping: Organizes requirements into user-value-focused epics and builds an FR coverage map so no requirement is missed. - Story Generation and Validation: Creates stories in Given/When/Then acceptance-criteria format, then validates coverage, dependencies, and story sizing before completion. - Use Case: After finishing a PRD and architecture for a new product, run this workflow to produce a complete epics.md document with numbered epics, stories, and testable acceptance criteria for the development team. ## Quick Start Ask the agent 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?▼

Run this workflow after your PRD and architecture documents exist. It extracts all functional and non-functional requirements, groups them into user-value-focused epics, then generates stories with Given/When/Then acceptance criteria saved to an epics.md file.

What documents are required before creating epics and stories?▼

A PRD containing functional and non-functional requirements and an Architecture document are required. A UX Design document is optional but treated as a first-class input, with its requirements extracted as separate UX design requirements.

How are user stories formatted in the output?▼

Each story uses the As a / I want / So that format followed by acceptance criteria written in Given/When/Then style. Stories are numbered per epic, sized for a single dev agent, and must not depend on future stories.

Does the workflow check that all requirements are covered?▼

Yes. Step 2 builds an FR coverage map linking every requirement to an epic, and Step 4 validates that each FR appears in at least one story with acceptance criteria that fully address it.

Can I customize the workflow behavior for my team?▼

Yes. The customize.toml file supports team and user overrides for activation steps, persistent facts loaded from project files, and an on_complete hook, merged using base, team, then user precedence.