bmad-create-epics-and-stories

To break PRD requirements into developer-ready user stories, you map functional requirements and architecture constraints into user-value epics, then decompose them into independently completable stories with Given/When/Then acceptance criteria.

To structure epics without forward dependencies, you sequence user stories during requirements decomposition so each story is independently completable, ensuring implementation planning moves forward without blocking subsequent dev agent tasks.

Mapping functional requirements to epics for product planning works by validating prerequisite documents, designing epics for user value, and gating story creation through user confirmations to ensure full FR coverage.

Yes, you need an approved architecture document and PRD to generate user stories with acceptance criteria, as the workflow applies prerequisite validation to map architecture constraints and NFRs into the story creation process.

Yes, you can use this requirements decomposition approach for a single dev agent workflow because it specifically sizes each user story to be independently completable by one developer entity.

Story creation must follow a step-file workflow with validation gating to ensure template-based document generation correctly maps functional requirements to epics and enforces quality-focused output before proceeding.