bmad-create-epics-and-stories

Name: bmad-create-epics-and-stories
Availability: InStock
Author: robotics-playground

Decompose PRD, Architecture, and UX documents into epics and stories.

Updated Mar 18, 2026

Search Tags:#planning #architecture #requirements #story #PRD #ux #epic

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/robotics-playground/skills/tree/main/_bmad/bmm/workflows/3-solutioning/bmad-create-epics-and-stories
Command: npx skills add https://github.com/robotics-playground/skills --skill bmad-create-epics-and-stories-robotics-playground

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform fragmented PRD, Architecture, and UX guidance into a structured, development-ready plan by decomposing requirements into standalone epics and stories with clear acceptance criteria.

Core Features & Use Cases

End-to-end workflow that reads PRD, Architecture, and UX documents, extracts requirements, and composes an evidence-based epic/story structure.
Template-driven planning artifacts with frontmatter-tracked progress and traceability from requirements to stories.
Collaborative UX: stepwise approvals and guided design-review prompts to align with stakeholders.

Quick Start

Begin Step 1 to validate prerequisites and extract requirements from PRD, Architecture, and UX documents using the Step-01 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 product requirements into actionable epics and stories?▼

To decompose product requirements into epics and stories, this Skill applies a stepwise workflow that extracts data from PRD, Architecture, and UX documents to generate executable epics and stories with clear acceptance criteria.

What is the best way to ensure traceability from requirements to stories during planning?▼

Ensuring traceability from requirements to stories is achieved by mapping functional and non-functional requirements directly to epics and stories within a template-driven master document that tracks progress through frontmatter.

How do I generate a development-ready plan from fragmented PRD and UX guidance?▼

Generating a development-ready plan from fragmented PRD and UX guidance requires validating prerequisites and extracting requirements step-by-step, then composing an evidence-based epic and story structure with stakeholder approvals.

Can I enforce epic independence and intra-epic sequencing when structuring my backlog?▼

Yes, you can enforce epic independence and intra-epic sequencing by validating the generated planning artifacts, ensuring that each epic stands alone while maintaining logical story sequencing within each epic.

Do I need separate PRD, Architecture, and UX documents to create epics and stories?▼

You need PRD, Architecture, and UX documents as inputs for the extraction workflow to produce a complete, testable planning artifact that aligns with business goals and ensures end-to-end traceability.