bmad-create-epics-and-stories

The skill decomposes product requirements by extracting functional and non-functional requirements from your PRD, organizing them into user-outcome epics, and generating detailed user stories with Given/When/Then acceptance criteria. It validates prerequisite planning artifacts before starting the breakdown workflow.

Writing acceptance criteria uses the Given/When/Then format generated automatically for each user story. The skill extracts functional and non-functional requirements from your PRD and translates them into testable conditions, ensuring every backlog item is development-ready and verifiable.

Ensuring no forward dependencies involves validating that every generated user story is sized for single-dev completion and does not require future stories. The skill enforces strict sequencing rules during requirements decomposition to create a clean, sequential development backlog.

Yes, you can use architecture and UX constraints to generate a backlog. The skill extracts architecture-derived and UX-derived requirements when available, combining them with PRD functional requirements to build a comprehensive FR-to-epic coverage map before producing the final user stories.

Yes, an approved epic structure is required before generating user stories. The skill employs multi-step confirmation gates, requiring explicit approval of the FR-to-epic coverage map and epic structure before proceeding to create the detailed story breakdown for the backlog.