bmad-bmm-create-epics-and-stories

Convert high-level project requirements into detailed epics and user stories.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/rahmatullahboss/multi-store-saas --skill bmad-bmm-create-epics-and-stories-rahmatullahboss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-bmm-create-epics-and-stories
Source: https://github.com/rahmatullahboss/multi-store-saas/tree/main/.agents/skills/bmad-bmm-create-epics-and-stories
Command: npx skills add https://github.com/rahmatullahboss/multi-store-saas --skill bmad-bmm-create-epics-and-stories-rahmatullahboss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps project teams systematically decompose complex requirements into manageable epics and user stories, facilitating Agile planning and alignment.

Core Features & Use Cases

  • Requirement Breakdown: Transform high-level requirements into structured epics and detailed user stories.
  • Use Case: When a product manager specifies a new feature, use this Skill to produce a clear list of epics and associated stories for sprint planning.
  • Scenario Handling: Supports transformation of various requirement formats into consistent Agile artifacts, ensuring traceability.

Quick Start

Use the bmad-bmm-create-epics-and-stories skill to generate epics and stories from the current project requirements document.

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

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

FAQPage Schema
How do I break down project requirements into epics and user stories?

To break down project requirements into epics and user stories, you can use automated workflows that systematically decompose high-level project specifications into structured Agile artifacts for sprint planning and backlog refinement.

How does automated requirement decomposition work for Agile planning?

Automated requirement decomposition works by executing predefined workflows that analyze high-level project requirements and transform them into consistent, traceable epics and detailed user stories, ensuring alignment across product management teams.

Can I convert high-level feature specifications into user stories for sprint planning?

Yes, you can convert high-level feature specifications into user stories for sprint planning. The process transforms various requirement formats into consistent Agile artifacts to facilitate structured backlog refinement and sprint alignment.

What is the best way to structure epics from a complex requirements document?

The best way to structure epics from a complex requirements document is by applying structured requirement analysis workflows that ensure traceability and systematically transform high-level specifications into manageable epics and associated stories.

Do I need a specific requirements format to generate Agile artifacts?

No specific requirements format is strictly needed to generate Agile artifacts. The workflow supports the transformation of various requirement formats into consistent epics and user stories, ensuring traceability throughout the decomposition process.