bmad-create-epics-and-stories

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

Decompose product requirements into epics and user stories with acceptance criteria.

Updated Jul 11, 2026

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

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill solves the challenge of translating high-level product requirements into structured, actionable development tasks, ensuring that epics and user stories are logically organized, testable, and aligned with user value.

Core Features & Use Cases

Requirements Decomposition: Systematically extracts functional, non-functional, and UX requirements from project documentation.
Epic Design: Organizes work into value-focused epics that are independently deliverable and dependency-aware.
Story Generation: Creates granular user stories with standardized acceptance criteria using the Given-When-Then format.
Use Case: Use this when you have a PRD and Architecture document and need to generate a complete, ready-to-code backlog of epics and stories for your development team.

Quick Start

Invoke the bmad-create-epics-and-stories skill to begin the requirements extraction and epic design process for your current project.

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

To convert a PRD into agile epics and user stories, you decompose product requirements by extracting functional, non-functional, and UX needs, then organize them into value-focused epics and granular stories with standardized acceptance criteria.

What is the best way to structure a development backlog from architecture documents?▼

The best way to structure a development backlog from architecture documents is to systematically extract technical requirements and organize them into independently deliverable, dependency-aware epics with logically sequenced, testable user stories.

How do you write acceptance criteria for user stories generated from product requirements?▼

Acceptance criteria for user stories generated from product requirements are written using the standardized Given-When-Then format, ensuring each story is testable and aligned with user value.

Do I need both a PRD and architecture document to generate an actionable backlog?▼

You need both a PRD and architecture document to generate a complete, ready-to-code backlog, as this ensures epics and user stories capture both functional product needs and underlying technical dependencies.

Can I use this requirements decomposition approach for technical project planning?▼

Yes, you can use this requirements decomposition approach for technical project planning scenarios where high-level project documentation must be converted into actionable development tasks with logical, value-driven task sequencing.

What is requirements decomposition in agile development?▼

Requirements decomposition in agile development is the process of systematically extracting functional, non-functional, and UX requirements from project documentation to facilitate structured epic design and story generation.