bmad-create-epics-and-stories

Decompose product requirements into detailed epics and user stories.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/wahabmalik/whatsapp-chatbot --skill bmad-create-epics-and-stories-wahabmalik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/wahabmalik/whatsapp-chatbot/tree/main/.github/skills/bmad-create-epics-and-stories
Command: npx skills add https://github.com/wahabmalik/whatsapp-chatbot --skill bmad-create-epics-and-stories-wahabmalik

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the complex task of breaking down product requirements into actionable epics and stories, streamlining the software development process.

Core Features & Use Cases

  • Requirements Decomposition: Transform Product Requirements Documents (PRD), architecture decisions, and UX design into detailed epics and stories.
  • Collaborative Workflow: Facilitates collaboration between product strategists, technical writers, and product owners.
  • Output Documentation: Generates comprehensive documentation with structured templates for easy reference.

Quick Start

Activate the bmad-create-epics-and-stories skill to start the epic and story creation workflow.

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 decompose a PRD into epics and user stories?

Breaking down product requirements into epics and stories involves transforming PRD, architecture, and UX design documents into actionable development tasks using structured templates and disciplined state tracking.

What documents do I need to create detailed user stories and epics?

Creating detailed user stories and epics requires input documents such as a Product Requirements Document (PRD), architecture decisions, and UX design specifications to accurately decompose high-level product requirements into actionable development tasks.

What is the best way to facilitate collaborative requirements decomposition for software development?

Collaborative requirements decomposition is best facilitated by generating comprehensive documentation with structured templates, allowing product strategists, technical writers, and product owners to coordinate the breakdown of product requirements into epics and stories.

Can I use this approach for product management without existing architecture and UX design specs?

Using this approach for product management without existing architecture and UX design specs is not recommended, as the decomposition workflow explicitly requires these input documents to accurately generate detailed epics and user stories.

How does step-file architecture support epic and story creation?

Step-file architecture supports epic and story creation by enabling disciplined execution and state tracking throughout the requirements decomposition workflow, ensuring structured and traceable transformation of product specifications into development tasks.