skills.rest
allaydesai
allaydesaiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

bmad-create-epics-and-stories

Convert product requirements and architecture documents into Markdown epics and user stories.

2|2|Updated Feb 16, 2025
Search Tags:#workflow#requirements#project planning#epics#agile#stories
One-click install
npx skills add https://github.com/allaydesai/Trading-ntrader --skill bmad-create-epics-and-stories-allaydesai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/allaydesai/Trading-ntrader/tree/main/.cursor/skills/bmad-create-epics-and-stories
Command: npx skills add https://github.com/allaydesai/Trading-ntrader --skill bmad-create-epics-and-stories-allaydesai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps product teams decompose complex requirements into clear, structured epics and stories, enabling efficient Agile planning and development.

Core Features & Use Cases

  • Requirements Decomposition: Converts high-level PRD and architecture documents into detailed epics and stories.
  • Structured Output: Generates Markdown documents with organized, traceable user stories and acceptance criteria.
  • Use Case: Facilitates collaboration between product managers and developers by translating product visions and technical specs into ready-to-implement tasks.

Quick Start

Use the bmad-create-epics-and-stories skill to convert your project requirements documents into a structured set of epics and stories for your backlog.

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 product requirements into Agile epics and stories?▼

You can convert high-level PRD and architecture documents into detailed epics and user stories by analyzing requirements and generating Markdown documents with traceable acceptance criteria for Agile planning.

What documents do I need to generate user stories from requirements?▼

You need markdown templates, requirements documents, and UX specs to generate comprehensive user stories that accurately capture both product vision and technical architecture decisions.

Can I use UX specs and architecture decisions to create Agile acceptance criteria?▼

Yes, UX specs and architecture decisions are explicitly supported as inputs to auto-generate structured acceptance criteria, translating technical specifications into ready-to-implement Agile development tasks.

What is the best way to structure epics and stories for Agile backlog planning?▼

The best way to structure epics and stories for Agile backlog planning is to decompose complex requirements into organized Markdown documents, ensuring traceability between high-level product visions and development tasks.

Does this requirements decomposition approach work for both product managers and developers?▼

Yes, requirements decomposition works for both roles by translating product visions into structured tasks for managers and ready-to-implement technical specifications for development teams.

How are user stories and acceptance criteria formatted in the output?▼

User stories and acceptance criteria are output as structured Markdown documents containing organized, traceable tasks that enable efficient Agile planning and development tracking.

Related Skills

Explore More Product & Management Skills→
Emz1998Emz1998
1

specs-creator

Generate PRD, tech, and UX specs from feature descriptions.

Community
Intermediate
devCharuzudevCharuzu

agile-product-owner

Organize Agile backlog management and sprint execution with user stories and capacity planning.

Community
Advanced
slgoodrichslgoodrich
121

prioritization-methods

Prioritize features using RICE, ICE, MoSCoW, Kano, and weighted scoring frameworks.

Community
Basic
infinith4infinith4
1

requirements

Translate product ideas into structured requirements documentation with traceability matrix.

Community
Advanced