Prompt file imported from masterthepixel/maybridgepublishing (.windsurf/workflows/bmad/bmm/workflows/create-epics-and-stories.md). Copyright stays with the author.

Epic and Story Decomposition Workflow

Name: create-epics-and-stories
Author: masterthepixel

name: create-epics-and-stories description: "Transform PRD requirements into bite-sized stories organized into deliverable functional epics. This workflow takes a Product Requirements Document (PRD) and breaks it down into epics and user stories that can be easily assigned to development teams. It ensures that all functional requirements are captured in a structured format, making it easier for teams to understand and implement the necessary features." author: "BMad"

Critical variables from config

config_source: "{project-root}/.bmad/bmm/config.yaml" project_name: "{config_source}:project_name" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" document_output_language: "{config_source}:document_output_language" user_skill_level: "{config_source}:user_skill_level" date: system-generated

Smart input file references - handles both whole docs and sharded docs

Priority: Whole document first, then sharded version

input_file_patterns: prd: description: "Product Requirements Document with FRs and NFRs" whole: "{output_folder}/prd.md" sharded: "{output_folder}/prd/index.md" load_strategy: "INDEX_GUIDED" product_brief: description: "Product vision and goals (optional)" whole: "{output_folder}/productbrief*.md" sharded: "{output_folder}/productbrief*/index.md" load_strategy: "INDEX_GUIDED" domain_brief: description: "Domain-specific requirements and context (optional)" whole: "{output_folder}/domainbrief*.md" sharded: "{output_folder}/domainbrief*/index.md" load_strategy: "INDEX_GUIDED" ux_design: description: "UX design specification for interaction patterns (optional)" whole: "{output_folder}/ux.md" sharded: "{output_folder}/ux/index.md" load_strategy: "FULL_LOAD" architecture: description: "Architecture decisions and technical design (optional)" whole: "{output_folder}/architecture.md" sharded: "{output_folder}/architecture/index.md" load_strategy: "FULL_LOAD"

Module path and component files

installed_path: "{project-root}/.bmad/bmm/workflows/3-solutioning/create-epics-and-stories" instructions: "{installed_path}/instructions.md" template: "{installed_path}/epics-template.md"

Output configuration

default_output_file: "{output_folder}/epics.md"

standalone: true

# Epic and Story Decomposition Workflow name: create-epics-and-stories description: "Transform PRD requirements into bite-sized stories organized into deliverable functional epics. This workflow takes a Product Requirements Document (PRD) and breaks it down into epics and user stories that can be easily assigned to development teams. It ensures that all functional requirements are captured in a structured format, making it easier for teams to understand and implement the necessary features." author: "BMad" # Critical variables from config config_source: "{project-root}/.bmad/bmm/config.yaml" project_name: "{config_source}:project_name" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" document_output_language: "{config_source}:document_output_language" user_skill_level: "{config_source}:user_skill_level" date: system-generated # Smart input file references - handles both whole docs and sharded docs # Priority: Whole document first, then sharded version input_file_patterns: prd: description: "Product Requirements Document with FRs and NFRs" whole: "{output_folder}/*prd*.md" sharded: "{output_folder}/*prd*/index.md" load_strategy: "INDEX_GUIDED" product_brief: description: "Product vision and goals (optional)" whole: "{output_folder}/*product*brief*.md" sharded: "{output_folder}/*product*brief*/index.md" load_strategy: "INDEX_GUIDED" domain_brief: description: "Domain-specific requirements and context (optional)" whole: "{output_folder}/*domain*brief*.md" sharded: "{output_folder}/*domain*brief*/index.md" load_strategy: "INDEX_GUIDED" ux_design: description: "UX design specification for interaction patterns (optional)" whole: "{output_folder}/*ux*.md" sharded: "{output_folder}/*ux*/index.md" load_strategy: "FULL_LOAD" architecture: description: "Architecture decisions and technical design (optional)" whole: "{output_folder}/*architecture*.md" sharded: "{output_folder}/*architecture*/index.md" load_strategy: "FULL_LOAD" # Module path and component files installed_path: "{project-root}/.bmad/bmm/workflows/3-solutioning/create-epics-and-stories" instructions: "{installed_path}/instructions.md" template: "{installed_path}/epics-template.md" # Output configuration default_output_file: "{output_folder}/epics.md" standalone: true

{ "prompt": "# Epic and Story Decomposition Workflow\nname: create-epics-and-stories\ndescription: \"Transform PRD requirements into bite-sized stories organized into deliverable functional epics. This workflow takes a Product Requirements Document (PRD) and breaks it down into epics and user stories that can be easily assigned to development teams. It ensures that all functional requirements are captured in a structured format, making it easier for teams to understand and implement the necessary features.\"\nauthor: \"BMad\"\n\n# Critical variables from config\nconfig_source: \"{project-root}/.bmad/bmm/config.yaml\"\nproject_name: \"{config_source}:project_name\"\noutput_folder: \"{config_source}:output_folder\"\nuser_name: \"{config_source}:user_name\"\ncommunication_language: \"{config_source}:communication_language\"\ndocument_output_language: \"{config_source}:document_output_language\"\nuser_skill_level: \"{config_source}:user_skill_level\"\ndate: system-generated\n\n# Smart input file references - handles both whole docs and sharded docs\n# Priority: Whole document first, then sharded version\ninput_file_patterns:\n prd:\n description: \"Product Requirements Document with FRs and NFRs\"\n whole: \"{output_folder}/*prd*.md\"\n sharded: \"{output_folder}/*prd*/index.md\"\n load_strategy: \"INDEX_GUIDED\"\n product_brief:\n description: \"Product vision and goals (optional)\"\n whole: \"{output_folder}/*product*brief*.md\"\n sharded: \"{output_folder}/*product*brief*/index.md\"\n load_strategy: \"INDEX_GUIDED\"\n domain_brief:\n description: \"Domain-specific requirements and context (optional)\"\n whole: \"{output_folder}/*domain*brief*.md\"\n sharded: \"{output_folder}/*domain*brief*/index.md\"\n load_strategy: \"INDEX_GUIDED\"\n ux_design:\n description: \"UX design specification for interaction patterns (optional)\"\n whole: \"{output_folder}/*ux*.md\"\n sharded: \"{output_folder}/*ux*/index.md\"\n load_strategy: \"FULL_LOAD\"\n architecture:\n description: \"Architecture decisions and technical design (optional)\"\n whole: \"{output_folder}/*architecture*.md\"\n sharded: \"{output_folder}/*architecture*/index.md\"\n load_strategy: \"FULL_LOAD\"\n\n# Module path and component files\ninstalled_path: \"{project-root}/.bmad/bmm/workflows/3-solutioning/create-epics-and-stories\"\ninstructions: \"{installed_path}/instructions.md\"\ntemplate: \"{installed_path}/epics-template.md\"\n\n# Output configuration\ndefault_output_file: \"{output_folder}/epics.md\"\n\nstandalone: true", "variables": [], "notes": "create-epics-and-stories", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/masterthepixel/maybridgepublishing", "path": ".windsurf/workflows/bmad/bmm/workflows/create-epics-and-stories.md", "ref": "b2a98783149d2f08bcc7abacd8a025493270ad1b", "url": "https://github.com/masterthepixel/maybridgepublishing/blob/b2a98783149d2f08bcc7abacd8a025493270ad1b/.windsurf/workflows/bmad/bmm/workflows/create-epics-and-stories.md", "key": "masterthepixel/maybridgepublishing/.windsurf/workflows/bmad/bmm/workflows/create-epics-and-stories.md" } } }

create-epics-and-stories

About

Epic and Story Decomposition Workflow

Critical variables from config

Smart input file references - handles both whole docs and sharded docs

Priority: Whole document first, then sharded version

Module path and component files

Output configuration

Use it

Manifest

Reviews