bmad-create-epics-and-stories

To break down a PRD into epics and user stories, extract functional and non-functional requirements, group them into user-value-focused epics, and generate detailed stories with testable acceptance criteria and dependency checks.

Requirements coverage mapping links every functional and non-functional requirement from your planning documents to a specific epic, ensuring nothing is lost during backlog creation and preventing missing requirements.

You need a PRD and architecture document to generate user stories, while UX design documents are optional but recommended to ensure complete UX requirement coverage during backlog planning.

Delivery-ready user stories are written using template-driven documentation, testable acceptance criteria, forward dependency checks, and validation against architecture constraints to ensure complete development readiness.

The best way to ensure no non-functional requirements are missed is by enforcing sequential validation that extracts and maps NFRs alongside functional requirements before generating the final epic and story backlog.

You should use an automated approach for creating an epics.md file when you have scattered product requirements, architecture decisions, and UX specs that need structured grouping into implementation-ready work to avoid vague stories.