bmad-create-epics-and-stories

Transform product requirements into structured epics and user stories.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/peshay/portfolixir --skill bmad-create-epics-and-stories-peshay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/peshay/portfolixir/tree/main/.claude/skills/bmad-create-epics-and-stories
Command: npx skills add https://github.com/peshay/portfolixir --skill bmad-create-epics-and-stories-peshay

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill aids in breaking down project requirements into manageable epics and user stories, fostering structured project management and clear communication between stakeholders.

Core Features & Use Cases

  • Requirements Decomposition: Breaks down PRD and architecture requirements into actionable epics and stories.
  • Workflow Architecture: Uses step-file architecture for disciplined execution and sequential enforcement.
  • User Interaction: Guides a user through a structured process to define epics and stories based on their requirements.
  • Use Case: For a project manager who needs to translate business requirements into technical user stories for development teams.

Quick Start

Run the skill with the command 'bmad-create-epics-and-stories' and follow the step-by-step guide to define your epics and stories.

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

To break down product requirements into epics and user stories, this Skill transforms your PRD and architecture requirements into a structured, actionable list for project management. It guides you through a collaborative, step-by-step process to define each component clearly.

What is the best way to translate business requirements into technical user stories for development teams?

The best way to translate business requirements into technical user stories is using a structured workflow architecture that enforces sequential execution. This ensures clear communication between stakeholders and delivers actionable stories for development teams.

How does requirement decomposition work for project management workflows?

Requirement decomposition works by taking detailed product requirements and breaking them down into manageable epics and user stories. This structured approach fosters disciplined execution and clear stakeholder communication throughout the project lifecycle.

Do I need a complete PRD to start generating epics and stories?

You need detailed product and architecture requirements as input to generate epics and stories effectively. The Skill uses a collaborative approach to help you define the structured list based on the requirements you provide during the step-by-step process.

Can I use this structured workflow for large scale project requirement analysis?

You can use this structured workflow for large scale project requirement analysis where detailed decomposition is necessary. The step-file architecture enforces sequential execution, ensuring disciplined management of complex requirements across stakeholders.