create-epics-and-stories

Name: create-epics-and-stories
Availability: InStock
Author: stellar-zk

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

3|Updated Feb 26, 2026

Search Tags:#requirements #acceptance criteria #epics #user stories #backlog #prd #agile planning

Ready to run

npx skills add https://github.com/stellar-zk/stellar-zk --skill create-epics-and-stories-stellar-zk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-epics-and-stories
Source: https://github.com/stellar-zk/stellar-zk/tree/main/.claude/skills/create-epics-and-stories
Command: npx skills add https://github.com/stellar-zk/stellar-zk --skill create-epics-and-stories-stellar-zk

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 epics and developer-ready stories with testable acceptance criteria. ## 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 user-value-focused epics with an FR coverage map, avoiding technical-layer decomposition and file churn. - Story Generation: Produces stories in As a / I want / So that format with Given/When/Then acceptance criteria, sized for a single dev agent. - Use Case: After finishing a PRD and architecture spec for a new app, run this workflow to produce a complete epics.md backlog where every requirement maps to at least one validated story. ## Quick Start Ask the AI to create the epics and stories list from the PRD and architecture documents in your docs folder.

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 recommended, since its requirements are extracted as first-class inputs for story creation.

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 follow the As a / I want / So that structure and are sized for completion by a single dev agent.

Can stories depend on future stories in the same epic?▼

No. The workflow enforces that each story builds only on previously completed stories, and each epic must deliver standalone value without requiring future epics. A final validation step checks all dependencies before completion.

What happens if requirements are missing from the epic breakdown?▼

The workflow builds an FR coverage map linking every requirement to an epic, and the final validation step verifies each FR and UX design requirement is covered by at least one story before the document is approved.