bmad-create-epics-and-stories

To break product requirements down into agile epics and user stories, this Skill decomposes PRDs, architecture docs, and UX designs into a structured backlog with detailed acceptance criteria.

Yes, you can generate user stories with acceptance criteria from architecture documents. This Skill transforms architectural decisions and UX designs into structured stories featuring detailed, testable acceptance criteria.

The best way to create an agile backlog from a new feature requirement is to automate the decomposition process. This Skill ensures comprehensive coverage of functional, non-functional, and UX requirements in the generated epics.

You do not strictly need a full PRD to generate epics and user stories. This Skill can also process architectural decisions and UX designs to produce a structured, actionable backlog for your development team.

Yes, the requirements decomposition process covers non-functional requirements. It ensures comprehensive coverage of functional, non-functional, and UX requirements when creating epics and user stories.

To write technical specifications and product strategy for agile teams, this Skill facilitates collaborative product strategy writing by decomposing technical specifications into structured epics and actionable user stories.