bmad-create-epics-and-stories

To decompose product requirements into epics and user stories, you provide PRD and architecture decisions to extract functional and non-functional requirements, which are then mapped into a structured epic and story hierarchy with clear acceptance criteria.

Generating user stories from a PRD involves validating prerequisites and extracting all project requirements first, then transforming those requirements alongside UX considerations into standalone, ready-to-implement stories through iterative collaboration.

Mapping dependencies when designing epics requires analyzing architecture decisions and workflow engineering constraints, ensuring that each generated user story accounts for cross-functional dependencies and validation steps before implementation.

Yes, you can refine epic structure and story scope iteratively during requirement extraction, as the workflow supports collaborative validation steps to adjust functional and non-functional requirements mapping until stories are ready for implementation.

Including UX considerations when generating user stories means integrating user experience constraints directly into the epic design phase, ensuring that the resulting stories reflect both functional needs and UX validation workflows.

Yes, epic design works for both functional and non-functional requirements by mapping each requirement type into standalone epics and stories, ensuring comprehensive coverage of architecture and UX constraints with clear acceptance criteria.