bmad-create-epics-and-stories

To break down product requirements into epics and user stories, you extract functional and non-functional constraints from your PRD and architecture documents to generate a user-value-first epic plan with explicit acceptance criteria. This ensures every story is standalone and developer-ready.

Writing user stories with acceptance criteria for sequential development involves structuring stories sized for single-agent completion and enforcing a “no forward dependencies” constraint within each epic. This template compliance guarantees developers can implement tasks immediately without waiting on future requirements.

Yes, you can integrate UX design requirements into your epic and story breakdown by feeding your UX Design documents alongside your PRD and architecture inputs. The workflow extracts these constraints to ensure the generated user stories align with both functional and design requirements.

The best way to map functional requirements to epics is to structure your epic list around user outcomes while applying explicit FR coverage mapping. This approach transforms raw product strategy into a standalone epic plan that directly ties each user value to a specific functional requirement.

User stories have forward dependencies when the requirements decomposition fails to enforce a “no future dependencies” constraint within epics. Generating standalone stories sized for single-agent completion eliminates these blockers, ensuring developer-ready output for sequential planning.

You need a PRD and architecture document to generate build-ready user stories, as these provide the functional and non-functional requirements required for extraction. An optional UX Design document can also be supplied to further refine the developer-ready output.