bmad-create-epics

Breaking down a PRD into epics and user stories requires extracting functional requirements, structuring them into value-driven epics, and generating detailed stories with acceptance criteria. This ensures development teams receive implementation-ready tasks with full traceability and dependency validation.

Structuring epics based on user value involves analyzing your PRD to group related functional and non-functional requirements logically. You establish dependencies between these epics to ensure a coherent delivery sequence, validating that all architectural decisions are properly represented before generating detailed user stories.

Validating functional requirement coverage involves cross-referencing generated user stories against the original PRD and architecture documents. You must verify that every requirement maps to a specific story with acceptance criteria, check architectural compliance, and confirm that all story dependencies are properly established.

Yes, workflow automation can break down Phase 3 Solutioning tasks by taking your PRD and architecture documents as input and automatically applying validation rules for prerequisites, epic design, and story creation. This outputs comprehensive, implementation-ready user stories organized by user value with full dependency tracking.

Yes, architecture documents are required alongside your PRD to generate accurate user stories. They provide the architectural compliance constraints and technical decisions necessary to validate epic design, ensure proper story dependencies, and confirm that generated stories align with the intended system architecture.