bmad-create-epics-and-stories

Extract functional and non-functional requirements into epics and user stories.

Updated Apr 2, 2026

Search Tags:#workflow #planning #requirements #acceptance criteria #epics #product strategy #user stories

Ready to run

npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-create-epics-and-stories-amitmishra-byldd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/amitmishra-byldd/Bmad-Note-Maker/tree/main/_bmad/bmm/3-solutioning/bmad-create-epics-and-stories
Command: npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-create-epics-and-stories-amitmishra-byldd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts PRD, Architecture, and optional UX inputs into a validated, traceable epic and user story backlog with clear acceptance criteria so teams can plan and deliver work reliably.

Core Features & Use Cases

Requirements Extraction: Systematically extract FRs, NFRs, and architecture/UX-driven technical requirements.
Template Initialization: Populate a reusable epics.md template, maintain frontmatter state, and create a requirements coverage map.
Workflow Enforcement: Enforce a step-file, sequential workflow that validates prerequisites, gains user confirmations, and prevents skipping steps.
Use Case: A product manager provides a PRD and architecture notes and asks the skill to "create the epics and stories list" to produce a developer-ready backlog.

Quick Start

Ask the skill to create the epics and stories list and provide the PRD, Architecture, and optional UX Design documents for analysis.

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 epics and user stories with acceptance criteria?▼

To convert a PRD into epics and user stories, extract functional and non-functional requirements along with architecture inputs, then organize them into prioritized epics and testable stories using a sequential step-file workflow.

What documents do I need to generate a requirements coverage map for my backlog?▼

Generating a requirements coverage map requires a validated PRD and Architecture document as mandatory inputs, while UX design documents are optional but recommended for comprehensive requirement extraction.

Can I use architecture notes to create a developer-ready backlog during sprint refinement?▼

Yes, you can use architecture notes combined with a PRD to create a developer-ready backlog during sprint refinement by systematically extracting technical requirements and mapping them to actionable user stories.

How does the step-file workflow prevent skipping steps when extracting product requirements?▼

The step-file workflow prevents skipping steps by enforcing a sequential process that validates prerequisites and halts for user confirmation before each transition, ensuring accurate requirement extraction and template initialization.

What is the best way to organize non-functional requirements into testable user stories?▼

The best way to organize non-functional requirements into testable user stories is to extract them directly from PRD and Architecture documents and populate a reusable epics template that maintains frontmatter state for traceability.

Do I need a project config to extract functional and non-functional requirements for product planning?▼

Yes, you need a project config pointing to planning_artifacts to extract functional and non-functional requirements, ensuring the extracted data correctly populates the epics and user stories workflow.