bmad-create-epics-and-stories

Break down PRDs into epics and user stories with acceptance criteria.

1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/thavirak-svay/rentify-backend --skill bmad-create-epics-and-stories-thavirak-svay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/thavirak-svay/rentify-backend/tree/main/_bmad/bmm/workflows/3-solutioning/bmad-create-epics-and-stories
Command: npx skills add https://github.com/thavirak-svay/rentify-backend --skill bmad-create-epics-and-stories-thavirak-svay

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps break down Product Requirements Documents (PRDs) into user-centric epics and stories, ensuring that the development team has clear, actionable tasks with complete acceptance criteria.

Core Features & Use Cases

  • Requirement Decomposition: Transforms high-level PRD requirements into detailed user stories.
  • Epic and Story Creation: Organizes stories into epics based on user value and dependencies.
  • Collaborative Workflow: Engages product strategists and technical writers in a collaborative process to create a comprehensive product roadmap.

Quick Start

Run the bmad-create-epics-and-stories skill to begin the epic and story creation process.

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

Requirement decomposition transforms high-level PRD requirements into detailed user stories by organizing them into epics based on user value and dependencies. This process ensures the development team receives clear, actionable tasks with complete acceptance criteria.

What is the best way to organize user stories by user value in a product roadmap?

Organizing user stories by user value involves grouping detailed requirements into epics that reflect dependencies and strategic importance. This collaborative workflow engages product strategists and technical writers to build a comprehensive and actionable product roadmap.

Does epic creation require a specific workflow architecture?

Epic creation requires a step-file architecture for disciplined execution. This structured approach supports the collaborative process between product strategists and technical writers, ensuring comprehensive requirement decomposition and accurate user story generation.

How do I ensure my user stories have complete acceptance criteria?

To ensure user stories have complete acceptance criteria, decompose your PRD requirements through a collaborative workflow involving product strategists and technical writers. This structured approach guarantees actionable tasks organized by user value and dependencies.

Can I use this requirement decomposition process for large product roadmaps?

Yes, requirement decomposition supports large product roadmaps by organizing detailed user stories into epics based on user value and dependencies. The step-file architecture enables disciplined execution across complex, high-level PRD requirements.