bmad-create-epics-and-stories

Convert PRD, Architecture, and UX documents into epics and stories with FR/NFR mapping.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill bmad-create-epics-and-stories-clovernguyen1010-ship-it
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/clovernguyen1010-ship-it/Clover_Nguyen/tree/main/_bmad/bmm/3-solutioning/bmad-create-epics-and-stories
Command: npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill bmad-create-epics-and-stories-clovernguyen1010-ship-it

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the translation of scattered product requirements (PRD, Architecture, UX) into structured, standalone epics and actionable stories that teams can implement.

Core Features & Use Cases

  • Transform raw requirements into standalone epics that deliver user value.
  • Decompose epics into properly scoped stories with acceptance criteria.
  • Maintain a templated, shareable artifact that tracks FR/NFR mapping and UX considerations.
  • Guided workflow with step-by-step validations ensuring completeness and alignment with product goals.

Quick Start

Initiate by running Step 1 in the workflow to validate prerequisites and extract requirements from available documents.

Frequently Asked Questions about bmad-create-epics-and-stories

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn scattered product requirements into actionable epics and stories?

To turn scattered product requirements into actionable epics and stories, this Skill applies a guided workflow to extract, validate, and map functional requirements from PRD, Architecture, and UX documents into templated planning artifacts.

What is the best way to decompose epics into properly scoped user stories?

The best way to decompose epics into properly scoped user stories is using a guided workflow that applies step-by-step validations, ensuring each story includes acceptance criteria and maintains alignment with overarching product goals.

Can I use PRD and UX documents to generate a ready-to-use planning artifact?

Yes, you can use PRD and UX documents to generate a ready-to-use planning artifact, as the Skill processes these inputs to produce structured epics and stories with FR/NFR mapping and UX considerations included.

Do I need functional and non-functional requirement mapping for product planning?

Functional and non-functional requirement mapping is needed for product planning to ensure completeness, track UX considerations, and maintain a templated, shareable artifact that aligns implementation stories with product goals.

How does the requirement extraction workflow validate product planning prerequisites?

The requirement extraction workflow validates product planning prerequisites by running an initial step that checks available documents, extracts requirements, and ensures completeness and alignment before generating epics and stories.