bmad-create-epics-and-stories

Name: bmad-create-epics-and-stories
Availability: InStock
Author: laraxot

Transform product requirements and architectural decisions into structured epics and stories.

26|23|Updated Dec 16, 2025

Search Tags:#product management #requirements analysis #workflows #user story #epic and story creation

Ready to run

npx skills add https://github.com/laraxot/laravelpizza.com --skill bmad-create-epics-and-stories-laraxot

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/laraxot/laravelpizza.com/tree/main/.github/skills/bmad-create-epics-and-stories
Command: npx skills add https://github.com/laraxot/laravelpizza.com --skill bmad-create-epics-and-stories-laraxot

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill transforms product requirements and architectural decisions into actionable user stories and epics, ensuring clarity and structure for development teams.

Core Features & Use Cases

Requirement Decomposition: Break down complex requirements into manageable user stories and epics.
Workflow Automation: Utilize a structured workflow to facilitate collaboration and ensure comprehensive coverage of requirements.
Use Case: A product owner needing to define and prioritize the development work for a new feature can use this Skill to generate a clear set of epics and stories from initial requirements.

Quick Start

Initialize the epic and story creation process by loading the workflow file with 'Follow the instructions in ./workflow.md.'

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 break down product requirements into epics and user stories?▼

To break down product requirements into epics and user stories, you can use a structured workflow that transforms architectural decisions into a clear list of actionable items. This process ensures development teams have comprehensive coverage.

What is the best way to organize dependencies between epics during requirement decomposition?▼

Organizing dependencies between epics during requirement decomposition involves documenting user value and structural links within a collaborative workflow. This approach ensures teams understand structural relationships when generating stories.

Can I automate epic and story creation from initial product requirements?▼

You can automate epic and story creation from initial product requirements by loading a structured workflow file. This workflow guides the transformation of inputs into organized stories, ensuring clarity for development teams.

Does epic and story creation require user collaboration for architectural decisions?▼

Yes, epic and story creation requires user collaboration for architectural decisions. The process depends on user input and decision-making to accurately document user value, specific requirements, and dependencies.

How to start generating user stories from a new feature requirement?▼

To start generating user stories from a new feature requirement, initialize the creation process by loading the workflow file. This action facilitates collaboration to define and prioritize the development work.