bmad-create-epics-and-stories

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

Break down high-level requirements into epics and user stories.

Updated Aug 23, 2026

Search Tags:#product management #epics #agile #user stories #requirements breakdown

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps break down large requirements into manageable epics and user stories, facilitating agile development planning.

Core Features & Use Cases

Epic Creation: Define high-level features or initiatives.
User Story Generation: Create detailed, actionable user stories with acceptance criteria.
Use Case: When a new feature request comes in, use this Skill to first define the overarching epic, then break it down into smaller, implementable user stories for the development team.

Quick Start

Use the bmad-create-epics-and-stories skill to create the epics and stories list.

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 high-level requirements into epics and user stories?▼

To break down requirements into epics and user stories, define the overarching epic for a large feature request, then divide it into smaller, implementable user stories with detailed acceptance criteria for your agile development team.

What is the best way to structure agile epics for product roadmap planning?▼

Structuring agile epics for product roadmap planning involves defining high-level features or initiatives first, then using a structured workflow to break those requirements down into actionable user stories that guide implementation.

Can I generate user stories with acceptance criteria from a new feature request?▼

Yes, you can generate detailed user stories with acceptance criteria from a new feature request by applying a structured breakdown process that translates large requirements into actionable agile development tasks.

Do I need a structured workflow to create user stories for agile project management?▼

Yes, a structured workflow is required to guide the breakdown process, ensuring high-level requirements are systematically translated into manageable epics and implementable user stories for agile project management.

When should I use an epic instead of a user story for software development planning?▼

Use an epic in software development planning when defining a large, high-level feature or initiative, then break that epic down into smaller user stories when the team needs detailed, actionable implementation tasks.