bmad-create-epics-and-stories

To break down high-level requirements, this skill decomposes PRD, architecture, and UX inputs into standalone epics that deliver user value, then generates actionable stories sized for a single developer. It also includes acceptance criteria for each story to ensure testability.

Mapping functional requirements to user stories for traceability is achieved by generating an FR and NFR coverage map alongside the epics and stories. This ensures every requirement is linked to a specific deliverable, providing complete auditability from product strategy to engineering plan.

Writing acceptance criteria for decomposed product epics is handled automatically during the story generation process. The skill co-authors the output with the product owner, validating that each story includes specific acceptance criteria until explicit approval is obtained.

Yes, you can use PRD and architecture documents to generate a complete backlog of stories. The skill transforms these high-level inputs into a concrete, testable set of epics and stories, mapping both functional and non-functional requirements to ensure full backlog coverage.

Yes, this approach validates generated stories with the product owner before finalizing. The skill operates as a co-author, iterating on the epics and stories until the product owner provides explicit approval, ensuring the engineering plan aligns with product strategy.