bmad-create-epics-and-stories

To convert a PRD into epics and user stories, extract functional and non-functional requirements along with architecture inputs, then organize them into prioritized epics and testable stories using a sequential step-file workflow.

Generating a requirements coverage map requires a validated PRD and Architecture document as mandatory inputs, while UX design documents are optional but recommended for comprehensive requirement extraction.

Yes, you can use architecture notes combined with a PRD to create a developer-ready backlog during sprint refinement by systematically extracting technical requirements and mapping them to actionable user stories.

The step-file workflow prevents skipping steps by enforcing a sequential process that validates prerequisites and halts for user confirmation before each transition, ensuring accurate requirement extraction and template initialization.

The best way to organize non-functional requirements into testable user stories is to extract them directly from PRD and Architecture documents and populate a reusable epics template that maintains frontmatter state for traceability.

Yes, you need a project config pointing to planning_artifacts to extract functional and non-functional requirements, ensuring the extracted data correctly populates the epics and user stories workflow.