bmad-create-epics-and-stories

Transform PRD, architecture, and UX inputs into epics and stories with FR coverage mapping.

1|Updated Aug 3, 2025

Search Tags:#workflow #planning #templates #requirements #epics #stories

Ready to run

npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-create-epics-and-stories-mazenmrad

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforming scattered requirements (PRD, Architecture, UX) into a cohesive, executable plan of epics and stories to guide product development and ensure alignment between stakeholders.

Core Features & Use Cases

Automates extraction of FRs, NFRs, and architecture constraints into epics.
Generates an Epic List and FR coverage map to ensure traceability.
Produces story templates with acceptance criteria for developer-ready work.

Quick Start

Run Step 1 (Validate Prerequisites) to begin extracting requirements and initializing the epic plan.

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 turn scattered PRD and UX requirements into actionable epics and stories?▼

To turn scattered requirements into actionable epics and stories, you need a structured planning approach that extracts functional needs from PRD, architecture, and UX inputs to generate an approved epic plan with traceability and testable stories.

What is the best way to map functional requirements to epics for stakeholder approval?▼

The best way to map functional requirements to epics is to generate an FR coverage map alongside an epic list. This ensures complete traceability from PRD constraints to user-value epics, creating a structured plan ready for stakeholder approval.

How do I generate developer-ready user stories with acceptance criteria from architecture constraints?▼

Generating developer-ready user stories from architecture constraints involves transforming NFRs and system limitations into output-ready story templates. These templates include specific acceptance criteria to ensure the development work is fully testable.

How do I structure an epics.md template for product development planning?▼

Structuring an epics.md template involves compiling validated requirements into a markdown format that lists user-value epics, includes an FR coverage map for traceability, and details testable stories to guide product development alignment.

Do I need a complete PRD before extracting epics and stories?▼

You do not need a complete PRD before extracting epics and stories, but you must validate prerequisites first. The process can apply to available PRD, architecture, and UX inputs to begin extracting requirements and initializing the epic plan.