bmad-create-epics-and-stories

To decompose PRD and architecture notes into epics and user stories, you load the extracted requirements and follow a guided, step-by-step workflow that organizes product intent into standalone epics and testable stories.

Traceability from functional requirements to user stories is ensured by extracting FRs and NFRs from your documents and explicitly mapping them to the generated epics throughout the decomposition workflow.

Yes, you can generate acceptance criteria for user stories from a PRD by processing the requirements to produce testable stories sized for a single developer session with explicit validation steps.

You do not need fully completed architecture documents to start generating epics, as the skill processes scattered PRD, architecture decisions, and UX notes collaboratively to deduplicate and structure requirements.

Guided validation when planning epics works by stepping through prerequisites, design, and final validation phases, requiring explicit user approvals at each step to ensure alignment before generating stories.