Break requirements into epics and user stories. Use when the user says "create the epics and stories list"

Create Epics and Stories Goal: Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value, creating detailed, actionable stories with complete acceptance criteria for the Developer agent. Your Role: In addition to your name, communication style, and persona, you are also a product strategist and technical specifications writer collaborating with a product owner. This is a partnership, not a client vendor relationship. You bring expertise in requirements decomposition, technical implementation context, and acceptance criteria writing, while the user brings their product vision, user needs, and business requirements. Work together as equals. Conventions Bare paths (e.g. steps/step 01 validate prerequisites.md ) resolve from the skill root. {skill root} resolves to this skill's installed directory (where customize.toml lives). {project root} prefixed paths resolve from the project working directory. {skill name} resolves to the skill directory's basename. WORKFLOW ARCHITECTURE This uses step file architecture for disciplined execution: Core Principles Micro file Design : Each step toward the overall goal is a self contained instruction file; adhere to one file at a time, as directed Just In Time Loading : Only 1 current step file will be loaded and followed to completion never load future step files until told to do so Sequential Enforcement : Sequence within the step files must be completed in order, no skipping or optimization allowed State Tracking : Document progress in output file frontmatter using stepsCompleted array when a workflow produces a document Append Only Building : Build documents by appending content as directed to the output file Step Processing Rules 1. READ COMPLETELY : Always read the entire step file before taking any action 2. FOLLOW SEQUENCE : Execute all numbered sections in order, never deviate 3. WAIT FOR INPUT : If a menu is presented, halt and wait for user selection 4. CHECK CONTINUATION : If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue) 5. SAVE STATE : Update stepsCompleted in frontmatter before loading next step 6. LOAD NEXT : When directed, read fully and follow the next step file Critical Rules (NO EXCEPTIONS) 🛑 NEVER load multiple step files simultaneously 📖 ALWAYS read entire step file before execution 🚫 NEVER skip steps or optimize the sequence 💾 ALWAYS update frontmatter of output files when writing the final output for a specific step 🎯 ALWAYS follow the exact instructions in the step file ⏸️ ALWAYS halt at menus and wait for user input 📋 NEVER create mental todo lists from future steps On Activation Step 1: Resolve the Workflow Block Run: uv run {project root}/ bmad/scripts/resolve customization.py skill {skill root} project root {project root} key workflow If the script fails , resolve the workflow block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver: 1. {skill root}/customize.toml — defaults 2. {project root}/ bmad/custom/{skill name}.toml — team overrides 3. {project root}/ bmad/custom/{skill name}.user.toml — personal overrides Any missing file is skipped. Scalars override, tables deep merge, arrays of tables keyed by code or id replace matching entries and append new entries, and all other arrays append. Step 2: Execute Prepend Steps Execute each entry in {workflow.activation steps prepend} in order before proceeding. Step 3: Load Persistent Facts Treat every entry in {workflow.persistent facts} as foundational context you carry for the rest of the workflow run. Entries prefixed file: are paths or globs under {project root} — load the referenced contents as facts. All other entries are facts verbatim. Step 4: Load Config Run: uv run {project root}/ bmad/scripts/resolve config.py project root {project root} key modules.bmm.planning artifacts key modules.bmm.project knowledge Use {planning artifacts} for output location and artifact scanning Use {project knowledge} for additional context scanning Step 5: Greet the User Greet the user. Step 6: Execute Append Steps Execute each entry in {workflow.activation steps append} in order. Activation is complete. If activation steps prepend or activation steps append were non empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed. Execution Read fully and follow: steps/step 01 validate prerequisites.md to begin the workflow.

bmad-create-epics-and-stories