bmad-create-epics-and-stories

To break down PRD requirements into epics and user stories, you extract functional and non-functional criteria from planning documents, group them into user-value-focused epics, and draft testable stories with acceptance criteria. This process ensures full coverage mapping and dependency awareness for delivery planning.

Grouping product requirements into epics with dependency checks involves analyzing architecture notes and UX documents to cluster related functional needs. You map coverage to ensure no requirements are missed while identifying dependencies between epic groups for structured validation and iterative approval workflows.

Drafting user stories with acceptance criteria from UX documents requires extracting UX specifications and translating them into testable, implementation-ready story formats. The process includes stepwise story-ready specification generation to satisfy structured validation during iterative approval workflows.

Yes, you can use this approach to extract architecture notes for backlog creation. It pulls architecture requirements from available planning documents and integrates them into the epic grouping and story drafting phases, ensuring technical constraints are included in the delivery planning backlog.