bmad-create-epics-and-stories

To break down a PRD into epics and stories, the Skill extracts functional and non-functional requirements from your PRD, Architecture, and UX docs to generate structured, user-value driven epics with actionable stories.

Mapping architecture and UX requirements to user stories works by pulling specific needs from those documents, organizing them into user-value driven epics, and defining actionable stories complete with acceptance criteria for implementation.

Yes, you can track epic generation progress and approvals. The workflow supports stepwise stakeholder sign-off and records decisions in a markdown file using frontmatter to track planning artifact progress.

The best way to structure epics from non-functional requirements is to map them directly alongside functional requirements into user-value driven epics, ensuring each story has clear acceptance criteria for collaborative development.

To generate planning artifacts step by step, provide your project details, approve the extracted epics structure, and the workflow outputs the finalized epics and stories directly to your planning_artifacts directory.