How do I trigger this skill?

Say 'create the epics and stories list' or reference the user requirement to start the workflow.

What details should a user story include?

Title, description, acceptance criteria, estimation guidance, and mapping to the epic and original requirement.

How do I validate the output?

Compare the generated epics and stories to the source requirements and checklist to ensure coverage and traceability.

Create Epics And Stories

npx machina-cli add skill PabloLION/bmad-plugin/create-epics-and-stories --openclaw

Files (1)

SKILL.md

426 B

Create Epics And Stories Workflow

Goal: Break requirements into epics and user stories.

Agent: Product Manager (John) Module: CORE

Execution

Read and follow: ./instructions.md

Validation

After completion, verify against: ./checklist.md

Source

git clone https://github.com/PabloLION/bmad-plugin/blob/main/plugins/bmad/skills/create-epics-and-stories/SKILL.mdView on GitHub

Overview

This skill helps you transform product requirements into a structured backlog by creating epics and linked user stories. It provides a clear hierarchy from high-level goals to actionable tasks, improving planning, estimation, and delivery alignment. It also references execution and validation steps to ensure completeness against a checklist.

How This Skill Works

Interpret the user's request to identify themes, group related requirements into epics, and break each epic into individual user stories with acceptance criteria. Each story is crafted to be INVEST-aligned and traceable back to the original requirements, then validated against the project checklist. The process is triggered by the phrase 'create the epics and stories list' and relies on the CORE module and product manager involvement.

When to Use It

You have a set of requirements and need a structured backlog with defined epics and stories
Starting a new feature area that requires clear scope and theme grouping
Preparing for sprint planning with believable story sizes
Ensuring traceability of requirements to deliverables
Collaborating with stakeholders to finalize acceptance criteria and priorities

Quick Start

Step 1: When the user says 'create the epics and stories list', gather the initial requirements
Step 2: Create epics by grouping related requirements into themes
Step 3: Break each epic into user stories with acceptance criteria and map to the original requirements

Best Practices

Start from a concise requirement statement and map to high-level epics
Group related requirements under each epic to maintain scope boundaries
Write user stories using INVEST and include acceptance criteria
Link each story to the source requirement to maintain traceability
Validate final epics and stories against the project checklist before planning

Example Use Cases

Epic: User authentication; Stories: Sign up, Sign in, Password reset, Email verification
Epic: Product search; Stories: Basic search, Filters, Sort, Auto-suggest, Result highlights
Epic: Onboarding flow; Stories: Welcome tour, Account setup, Preference capture
Epic: Checkout and payments; Stories: Cart, Checkout, Payment gateway integration, Order confirmation
Epic: Notifications; Stories: Email alerts, Push notifications, In-app banners

Frequently Asked Questions

Add this skill to your agents