create-epics-and-stories

Break down PRDs and specs into epics and user stories with acceptance criteria.

3|1|Updated May 12, 2026
One-click install
npx skills add https://github.com/LumenWipe/lumenwipe --skill create-epics-and-stories-lumenwipe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-epics-and-stories
Source: https://github.com/LumenWipe/lumenwipe/tree/main/.claude/skills/create-epics-and-stories
Command: npx skills add https://github.com/LumenWipe/lumenwipe --skill create-epics-and-stories-lumenwipe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms product requirements, architecture decisions, and UX specifications into a structured, user-value-focused breakdown of epics and actionable user stories, reducing ambiguity for development teams.

Core Features & Use Cases

  • Requirements Extraction: Identify and organize functional, non-functional, technical, and UX requirements from project documents.
  • Epic Design: Group requirements into standalone, user-centric epics with complete coverage mapping.
  • Story Specification: Create implementation-ready user stories with detailed, testable Given/When/Then acceptance criteria.
  • Validation Workflow: Check requirement coverage, architecture alignment, story sizing, dependency flow, and delivery readiness.
  • Use Case: Use this Skill to turn a PRD, architecture document, and UX design specification into a reviewed epics.md backlog that developers can implement sequentially.

Quick Start

Use the create-epics-and-stories skill to analyze the available project requirements and collaboratively produce a validated epic and user story breakdown.

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 down product requirements into actionable user stories?

To break down product requirements into actionable user stories, you extract functional, technical, and UX specifications from project documents, group them into user-centric epics, and specify testable Given/When/Then acceptance criteria for development teams.

What is the best way to group PRD and architecture specifications into epics?

Grouping PRD and architecture specifications into epics involves identifying and organizing project requirements, mapping them for complete coverage, and validating architecture alignment to ensure each epic delivers standalone user value.

How do I write testable acceptance criteria for backlog planning?

Writing testable acceptance criteria for backlog planning requires structuring story specifications into detailed Given/When/Then formats, ensuring implementation readiness by validating story sizing and dependency flow.

Can I use a PRD and UX design to generate a development-ready epics.md file?

Yes, you can use a PRD and UX design to generate a development-ready epics.md file by analyzing the project context documents to collaboratively produce a validated epic and user story breakdown artifact.

How do I validate requirement coverage and architecture alignment before development?

Validating requirement coverage and architecture alignment involves checking requirement inventories, verifying dependency flows, and assessing delivery readiness to reduce ambiguity before development teams implement the epics.md backlog.