bmad-create-epics-and-stories

To break requirements into epics and stories, you provide extracted requirements from PRDs and architecture docs to generate user-value driven epics, detailed stories with acceptance criteria, and validation steps. This decomposes high-level requirements into actionable work for organized delivery.

Generating an epic and story plan requires existing PRDs, architecture docs, and UX specs. These product discovery and planning inputs provide the extracted requirements needed to map business outcomes to user-value driven epics and aligned stories.

Story generation handles acceptance criteria by aligning them to functional requirements, non-functional requirements, and UX considerations. This ensures detailed stories map directly to the extracted requirements and business outcomes defined in your planning documents.

The best way to validate and sequence epics is through a collaborative workflow with approvals and final confirmation. You approve the generated epic structure first, then validate and sequence the detailed stories to ensure organized delivery.

Yes, you can use this requirements decomposition workflow for product discovery and planning. It applies directly to these workflows by translating high-level requirements into structured, actionable work through epic design, story generation, and collaborative validation.

Generated user stories lack alignment with business outcomes when requirements extraction is incomplete or missing PRD inputs. Proper epic design requires extracted requirements to map user-value driven epics to business outcomes and generate aligned acceptance criteria.