bmad-method 6.0.0-alpha.1 → 6.0.0-alpha.11

package/src/modules/{bmm → bmgd}/teams/team-gamedev.yaml

@@ -2,13 +2,17 @@
 bundle:
   name: Team Game Development
   icon: 🎮
-  description: Specialized game development team including Game Designer (creative vision and GDD), Game Developer (implementation and code), and Game Architect (technical systems and infrastructure). Perfect for game projects across all scales and platforms.
+  description: Specialized game development team including Game Designer (creative vision and GDD), Game Developer (implementation and code), Game Architect (technical systems and infrastructure), and Game Dev Scrum Master (sprint coordination). Perfect for game projects across all scales and platforms.
 agents:
   - game-designer
   - game-dev
   - game-architect
+  - game-scrum-master
 
 workflows:
   - brainstorm-game
   - game-brief
   - gdd
+  - narrative
+
+party: "./default-party.csv"

package/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md

@@ -0,0 +1,130 @@
+<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
+<critical>Communicate all responses in {communication_language}</critical>
+<critical>This is a meta-workflow that orchestrates the CIS brainstorming workflow with game-specific context and additional game design techniques</critical>
+<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
+<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>
+
+<workflow>
+
+  <step n="1" goal="Validate workflow readiness" tag="workflow-status">
+    <action>Check if {output_folder}/bmm-workflow-status.yaml exists</action>
+
+    <check if="status file not found">
+      <output>No workflow status file found. Game brainstorming is optional - you can continue without status tracking.</output>
+      <action>Set standalone_mode = true</action>
+    </check>
+
+    <check if="status file found">
+      <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
+      <action>Parse workflow_status section</action>
+      <action>Check status of "brainstorm-game" workflow</action>
+      <action>Get project_level from YAML metadata</action>
+      <action>Find first non-completed workflow (next expected workflow)</action>
+
+      <check if="project_type != 'game'">
+        <output>Note: This is a {{project_type}} project. Game brainstorming is designed for game projects.</output>
+        <ask>Continue with game brainstorming anyway? (y/n)</ask>
+        <check if="n">
+          <action>Exit workflow</action>
+        </check>
+      </check>
+
+      <check if="brainstorm-game status is file path (already completed)">
+        <output>⚠️ Game brainstorming session already completed: {{brainstorm-game status}}</output>
+        <ask>Re-running will create a new session. Continue? (y/n)</ask>
+        <check if="n">
+          <output>Exiting. Use workflow-status to see your next step.</output>
+          <action>Exit workflow</action>
+        </check>
+      </check>
+
+      <check if="brainstorm-game is not the next expected workflow (latter items are completed already in the list)">
+        <output>⚠️ Next expected workflow: {{next_workflow}}. Game brainstorming is out of sequence.</output>
+        <ask>Continue with game brainstorming anyway? (y/n)</ask>
+        <check if="n">
+          <output>Exiting. Run {{next_workflow}} instead.</output>
+          <action>Exit workflow</action>
+        </check>
+      </check>
+
+      <action>Set standalone_mode = false</action>
+    </check>
+
+  </step>
+
+  <step n="2" goal="Load game brainstorming context and techniques">
+    <action>Read the game context document from: {game_context}</action>
+    <action>This context provides game-specific guidance including:
+      - Focus areas for game ideation (mechanics, narrative, experience, etc.)
+      - Key considerations for game design
+      - Recommended techniques for game brainstorming
+      - Output structure guidance
+    </action>
+    <action>Load game-specific brain techniques from: {game_brain_methods}</action>
+    <action>These additional techniques supplement the standard CIS brainstorming methods with game design-focused approaches like:
+      - MDA Framework exploration
+      - Core loop brainstorming
+      - Player fantasy mining
+      - Genre mashup
+      - And other game-specific ideation methods
+    </action>
+  </step>
+
+  <step n="3" goal="Invoke CIS brainstorming with game context">
+    <action>Execute the CIS brainstorming workflow with game context and additional techniques</action>
+    <invoke-workflow path="{core_brainstorming}" data="{game_context}" techniques="{game_brain_methods}">
+      The CIS brainstorming workflow will:
+      - Merge game-specific techniques with standard techniques
+      - Present interactive brainstorming techniques menu
+      - Guide the user through selected ideation methods
+      - Generate and capture brainstorming session results
+      - Save output to: {output_folder}/brainstorming-session-results-{{date}}.md
+    </invoke-workflow>
+  </step>
+
+  <step n="4" goal="Update status and complete" tag="workflow-status">
+    <check if="standalone_mode != true">
+      <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
+      <action>Find workflow_status key "brainstorm-game"</action>
+      <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
+      <action>Update workflow_status["brainstorm-game"] = "{output_folder}/bmm-brainstorming-session-{{date}}.md"</action>
+      <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
+
+      <action>Find first non-completed workflow in workflow_status (next workflow to do)</action>
+      <action>Determine next agent from path file based on next workflow</action>
+    </check>
+
+    <output>**✅ Game Brainstorming Session Complete, {user_name}!**
+
+**Session Results:**
+
+- Game brainstorming results saved to: {output_folder}/bmm-brainstorming-session-{{date}}.md
+
+{{#if standalone_mode != true}}
+**Status Updated:**
+
+- Progress tracking updated: brainstorm-game marked complete
+- Next workflow: {{next_workflow}}
+  {{else}}
+  **Note:** Running in standalone mode (no progress tracking)
+  {{/if}}
+
+**Next Steps:**
+
+{{#if standalone_mode != true}}
+
+- **Next workflow:** {{next_workflow}} ({{next_agent}} agent)
+- **Optional:** You can run other analysis workflows (research, game-brief) before proceeding
+
+Check status anytime with: `workflow-status`
+{{else}}
+Since no workflow is in progress:
+
+- Refer to the BMM workflow guide if unsure what to do next
+- Or run `workflow-init` to create a workflow path and get guided next steps
+  {{/if}}
+  </output>
+  </step>
+
+</workflow>

package/src/modules/{bmm/workflows/1-analysis → bmgd/workflows/1-preproduction}/brainstorm-game/workflow.yaml

@@ -4,16 +4,16 @@ description: "Facilitate game brainstorming sessions by orchestrating the CIS br
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
 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"
+game_dev_experience: "{config_source}:game_dev_experience"
 date: system-generated
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmm/workflows/1-analysis/brainstorm-game"
+installed_path: "{project-root}/{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game"
 template: false
 instructions: "{installed_path}/instructions.md"
 
@@ -22,7 +22,7 @@ game_context: "{installed_path}/game-context.md"
 game_brain_methods: "{installed_path}/game-brain-methods.csv"
 
 # CORE brainstorming workflow to invoke
-core_brainstorming: "{project-root}/bmad/core/workflows/brainstorming/workflow.yaml"
+core_brainstorming: "{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml"
 
 standalone: true
 
@@ -30,12 +30,12 @@ web_bundle:
   name: "brainstorm-game"
   description: "Facilitate game brainstorming sessions by orchestrating the CIS brainstorming workflow with game-specific context, guidance, and additional game design techniques."
   author: "BMad"
-  instructions: "bmad/bmm/workflows/1-analysis/brainstorm-game/instructions.md"
+  instructions: "{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md"
   template: false
   web_bundle_files:
-    - "bmad/bmm/workflows/1-analysis/brainstorm-game/instructions.md"
-    - "bmad/bmm/workflows/1-analysis/brainstorm-game/game-context.md"
-    - "bmad/bmm/workflows/1-analysis/brainstorm-game/game-brain-methods.csv"
-    - "bmad/core/workflows/brainstorming/workflow.yaml"
+    - "{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md"
+    - "{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game/game-context.md"
+    - "{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game/game-brain-methods.csv"
+    - "{bmad_folder}/core/workflows/brainstorming/workflow.yaml"
   existing_workflows:
-    - core_brainstorming: "bmad/core/workflows/brainstorming/workflow.yaml"
+    - core_brainstorming: "{bmad_folder}/core/workflows/brainstorming/workflow.yaml"

package/src/modules/{bmm/workflows/1-analysis → bmgd/workflows/1-preproduction}/game-brief/instructions.md

@@ -1,28 +1,30 @@
 # Game Brief - Interactive Workflow Instructions
 
-<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
 <critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
 <critical>Generate all documents in {document_output_language}</critical>
+<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
 
 <critical>DOCUMENT OUTPUT: Concise, professional, game-design focused. Use tables/lists over prose. User skill level ({user_skill_level}) affects conversation style ONLY, not document content.</critical>
+<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>
 
 <workflow>
 
-<step n="0" goal="Validate workflow readiness">
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
-  <param>mode: validate</param>
-  <param>calling_workflow: game-brief</param>
-</invoke-workflow>
+<step n="0" goal="Validate workflow readiness" tag="workflow-status">
+<action>Check if {output_folder}/bmm-workflow-status.yaml exists</action>
 
-<check if="status_exists == false">
-  <output>{{suggestion}}</output>
-  <output>Note: Game brief is optional. Continuing without progress tracking.</output>
+<check if="status file not found">
+  <output>No workflow status file found. Game brief is optional - you can continue without status tracking.</output>
   <action>Set standalone_mode = true</action>
 </check>
 
-<check if="status_exists == true">
-  <action>Store {{status_file_path}} for later updates</action>
+<check if="status file found">
+  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
+  <action>Parse workflow_status section</action>
+  <action>Check status of "game-brief" workflow</action>
+  <action>Get project_level from YAML metadata</action>
+  <action>Find first non-completed workflow (next expected workflow)</action>
 
   <check if="project_type != 'game'">
     <output>Note: This is a {{project_type}} project. Game brief is designed for game projects.</output>
@@ -32,10 +34,25 @@
     </check>
   </check>
 
-  <check if="warning != ''">
-    <output>{{warning}}</output>
-    <output>Note: Game brief can provide valuable vision clarity at any stage.</output>
+  <check if="game-brief status is file path (already completed)">
+    <output>⚠️ Game Brief already completed: {{game-brief status}}</output>
+    <ask>Re-running will overwrite the existing brief. Continue? (y/n)</ask>
+    <check if="n">
+      <output>Exiting. Use workflow-status to see your next step.</output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
+
+  <check if="game-brief is not the next expected workflow (latter items are completed already in the list)">
+    <output>⚠️ Next expected workflow: {{next_workflow}}. Game Brief is out of sequence.</output>
+    <ask>Continue with Game Brief anyway? (y/n)</ask>
+    <check if="n">
+      <output>Exiting. Run {{next_workflow}} instead.</output>
+      <action>Exit workflow</action>
+    </check>
   </check>
+
+<action>Set standalone_mode = false</action>
 </check>
 </step>
 
@@ -309,17 +326,16 @@ This brief will serve as the primary input for creating the Game Design Document
 <template-output>executive_brief</template-output>
 </step>
 
-<step n="16" goal="Update status and complete">
+<step n="16" goal="Update status and complete" tag="workflow-status">
 <check if="standalone_mode != true">
-  <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
-    <param>mode: update</param>
-    <param>action: complete_workflow</param>
-    <param>workflow_name: game-brief</param>
-  </invoke-workflow>
-
-  <check if="success == true">
-    <output>Status updated! Next: {{next_workflow}}</output>
-  </check>
+  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
+  <action>Find workflow_status key "game-brief"</action>
+  <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
+  <action>Update workflow_status["game-brief"] = "{output_folder}/bmm-game-brief-{{game_name}}-{{date}}.md"</action>
+  <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
+
+<action>Find first non-completed workflow in workflow_status (next workflow to do)</action>
+<action>Determine next agent from path file based on next workflow</action>
 </check>
 
 <output>**✅ Game Brief Complete, {user_name}!**
@@ -331,17 +347,17 @@ This brief will serve as the primary input for creating the Game Design Document
 {{#if standalone_mode != true}}
 **Status Updated:**
 
-- Progress tracking updated
+- Progress tracking updated: game-brief marked complete
+- Next workflow: {{next_workflow}}
   {{else}}
-  Note: Running in standalone mode (no status file).
-  To track progress across workflows, run `workflow-init` first.
+  **Note:** Running in standalone mode (no progress tracking)
   {{/if}}
 
 **Next Steps:**
 
 {{#if standalone_mode != true}}
 
-- **Next required:** {{next_workflow}} ({{next_agent}} agent)
+- **Next workflow:** {{next_workflow}} ({{next_agent}} agent)
 - **Optional:** Consider creating a prototype of core mechanic or validating assumptions with target players before proceeding
 
 Check status anytime with: `workflow-status`

package/src/modules/{bmm/workflows/1-analysis → bmgd/workflows/1-preproduction}/game-brief/workflow.yaml

@@ -4,24 +4,16 @@ description: "Interactive game brief creation workflow that guides users through
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
 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"
+game_dev_experience: "{config_source}:game_dev_experience"
 date: system-generated
 
-# Optional input documents
-recommended_inputs:
-  - market_research: "Market research document (optional)"
-  - brainstorming_results: "Brainstorming session outputs (optional)"
-  - competitive_analysis: "Competitive game analysis (optional)"
-  - initial_ideas: "Initial game ideas or notes (optional)"
-  - reference_games: "List of inspiration games (optional)"
-
 # Module path and component files
-installed_path: "{project-root}/bmad/bmm/workflows/1-analysis/game-brief"
+installed_path: "{project-root}/{bmad_folder}/bmgd/workflows/1-preproduction/game-brief"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
@@ -35,10 +27,10 @@ web_bundle:
   name: "game-brief"
   description: "Interactive game brief creation workflow that guides users through defining their game vision with multiple input sources and conversational collaboration"
   author: "BMad"
-  instructions: "bmad/bmm/workflows/1-analysis/game-brief/instructions.md"
-  validation: "bmad/bmm/workflows/1-analysis/game-brief/checklist.md"
-  template: "bmad/bmm/workflows/1-analysis/game-brief/template.md"
+  instructions: "{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/instructions.md"
+  validation: "{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/checklist.md"
+  template: "{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/template.md"
   web_bundle_files:
-    - "bmad/bmm/workflows/1-analysis/game-brief/instructions.md"
-    - "bmad/bmm/workflows/1-analysis/game-brief/checklist.md"
-    - "bmad/bmm/workflows/1-analysis/game-brief/template.md"
+    - "{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/instructions.md"
+    - "{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/checklist.md"
+    - "{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/template.md"

package/src/modules/{bmm/workflows/2-plan-workflows → bmgd/workflows/2-design}/gdd/instructions-gdd.md

@@ -2,7 +2,7 @@
 
 <workflow>
 
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
+<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
 <critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
 <critical>Generate all documents in {document_output_language}</critical>
@@ -13,10 +13,29 @@
 <critical>If users mention technical details, append to technical_preferences with timestamp</critical>
 
 <critical>DOCUMENT OUTPUT: Concise, clear, actionable game design specs. Use tables/lists over prose. User skill level ({user_skill_level}) affects conversation style ONLY, not document content.</critical>
+<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>
+
+## Input Document Discovery
+
+This workflow requires: game brief, and may reference market research or brownfield project documentation.
+
+**Discovery Process** (execute for each referenced document):
+
+1. **Search for whole document first** - Use fuzzy file matching to find the complete document
+2. **Check for sharded version** - If whole document not found, look for `{doc-name}/index.md`
+3. **If sharded version found**:
+   - Read `index.md` to understand the document structure
+   - Read ALL section files listed in the index
+   - Treat the combined content as if it were a single document
+4. **Brownfield projects**: The `document-project` workflow always creates `{output_folder}/index.md`
+
+**Priority**: If both whole and sharded versions exist, use the whole document.
+
+**Fuzzy matching**: Be flexible with document names - users may use variations in naming conventions.
 
 <step n="0" goal="Validate workflow and extract project configuration">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
+<invoke-workflow path="{project-root}/{bmad_folder}/bmm/workflows/workflow-status">
   <param>mode: data</param>
   <param>data_request: project_config</param>
 </invoke-workflow>
@@ -67,19 +86,27 @@ Use: `prd`
 </check>
 </step>
 
-<step n="0.5" goal="Validate workflow sequencing">
+<step n="0.5" goal="Validate workflow sequencing" tag="workflow-status">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
-  <param>mode: validate</param>
-  <param>calling_workflow: gdd</param>
-</invoke-workflow>
+<check if="standalone_mode != true">
+  <action>Check status of "gdd" workflow in loaded status file</action>
+
+  <check if="gdd status is file path (already completed)">
+    <output>⚠️ GDD already completed: {{gdd status}}</output>
+    <ask>Re-running will overwrite the existing GDD. Continue? (y/n)</ask>
+    <check if="n">
+      <output>Exiting. Use workflow-status to see your next step.</output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
 
-<check if="warning != ''">
-  <output>{{warning}}</output>
-  <ask>Continue with GDD anyway? (y/n)</ask>
-  <check if="n">
-    <output>{{suggestion}}</output>
-    <action>Exit workflow</action>
+  <check if="gdd is not the next expected workflow (latter items are completed already in the list)">
+    <output>⚠️ Next expected workflow: {{next_workflow}}. GDD is out of sequence.</output>
+    <ask>Continue with GDD anyway? (y/n)</ask>
+    <check if="n">
+      <output>Exiting. Run {{next_workflow}} instead.</output>
+      <action>Exit workflow</action>
+    </check>
   </check>
 </check>
 </step>
@@ -195,7 +222,6 @@ Get core game concept and vision.
 <action>Guide user to define the primary game mechanics that players will interact with throughout the game</action>
 
 <template-output>primary_mechanics</template-output>
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 <action>Guide user to describe their control scheme and input method (keyboard/mouse, gamepad, touchscreen, etc.), including key bindings or button layouts if known</action>
 
@@ -213,8 +239,6 @@ For each {{placeholder}} in the fragment, elicit and capture that information.
 
 <template-output file="GDD.md">GAME_TYPE_SPECIFIC_SECTIONS</template-output>
 
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
-
 </step>
 
 <step n="7" goal="Progression and balance">
@@ -278,7 +302,6 @@ For each {{placeholder}} in the fragment, elicit and capture that information.
 <action>Work with user to translate game features into development epics, following level-appropriate guidelines (Level 1: 1 epic/1-10 stories, Level 2: 1-2 epics/5-15 stories, Level 3: 2-5 epics/12-40 stories, Level 4: 5+ epics/40+ stories)</action>
 
 <template-output>epics</template-output>
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -298,8 +321,7 @@ For each {{placeholder}} in the fragment, elicit and capture that information.
 
 <for-each epic="epic_list">
 
-<template-output file="epics.md">epic\_{{epic_number}}\_details</template-output>
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<template-output file="epics.md">epic*{{epic_number}}*details</template-output>
 
 </for-each>
 
@@ -328,18 +350,23 @@ For each {{placeholder}} in the fragment, elicit and capture that information.
 
 </step>
 
-<step n="15" goal="Update status and populate story sequence">
+<step n="15" goal="Update status and populate story sequence" tag="workflow-status">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
-  <param>mode: update</param>
-  <param>action: complete_workflow</param>
-  <param>workflow_name: gdd</param>
-  <param>populate_stories_from: {epics_output_file}</param>
-</invoke-workflow>
+<check if="standalone_mode != true">
+  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
+  <action>Find workflow_status key "gdd"</action>
+  <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
+  <action>Update workflow_status["gdd"] = "{output_folder}/bmm-gdd-{{game_name}}-{{date}}.md"</action>
+  <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
+
+<action>Parse {epics_output_file} to extract all stories</action>
+<action>Populate story_sequence section in status file with story IDs</action>
+<action>Set each story status to "not-started"</action>
+<output>Loaded {{total_stories}} stories from epics into story sequence.</output>
 
-<check if="success == true">
-  <output>Status updated! Next: {{next_workflow}} ({{next_agent}} agent)</output>
-  <output>Loaded {{total_stories}} stories from epics.</output>
+<action>Find first non-completed workflow in workflow_status (next workflow to do)</action>
+<action>Determine next agent from path file based on next workflow</action>
+<output>Next workflow: {{next_workflow}} ({{next_agent}} agent)</output>
 </check>
 
 </step>
@@ -372,7 +399,7 @@ Your choice:</ask>
 </check>
 
 <check if="user selects option 1 or fuzzy indicates wanting to create the narrative design document">
-  <invoke-workflow>{project-root}/bmad/bmm/workflows/2-plan-workflows/narrative/workflow.yaml</invoke-workflow>
+  <invoke-workflow>{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/narrative/workflow.yaml</invoke-workflow>
   <action>Pass GDD context to narrative workflow</action>
   <action>Exit current workflow (narrative will hand off to solutioning when done)</action>
 
@@ -466,7 +493,7 @@ Which would you like to proceed with?</ask>
 </check>
 
 <check if="user selects narrative option">
-  <invoke-workflow>{project-root}/bmad/bmm/workflows/2-plan-workflows/narrative/workflow.yaml</invoke-workflow>
+  <invoke-workflow>{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/narrative/workflow.yaml</invoke-workflow>
   <action>Pass GDD context to narrative workflow</action>
 </check>
 

package/src/modules/bmgd/workflows/2-design/gdd/workflow.yaml

@@ -0,0 +1,81 @@
+# Game Design Document (GDD) Workflow
+name: gdd
+description: "Game Design Document workflow for all game project levels - from small prototypes to full AAA games. Generates comprehensive GDD with game mechanics, systems, progression, and implementation guidance."
+author: "BMad"
+
+# Critical variables from config
+config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
+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"
+game_dev_experience: "{config_source}:game_dev_experience"
+date: system-generated
+
+# Workflow components
+installed_path: "{project-root}/{bmad_folder}/bmgd/workflows/2-design/gdd"
+instructions: "{installed_path}/instructions-gdd.md"
+template: "{installed_path}/gdd-template.md"
+game_types_csv: "{installed_path}/game-types.csv"
+
+# Output configuration
+default_output_file: "{output_folder}/GDD.md"
+
+# Game type references (loaded based on game type selection)
+game_type_guides: "{installed_path}/game-types/"
+
+# Smart input file references - handles both whole docs and sharded docs
+# Priority: Whole document first, then sharded version
+input_file_patterns:
+  game_brief:
+    description: "Game vision and core concept (optional)"
+    whole: "{output_folder}/*game-brief*.md"
+    sharded: "{output_folder}/*game-brief*/index.md"
+    load_strategy: "INDEX_GUIDED"
+
+  research:
+    description: "Market or domain research (optional)"
+    whole: "{output_folder}/*research*.md"
+    sharded: "{output_folder}/*research*/index.md"
+    load_strategy: "FULL_LOAD"
+
+  document_project:
+    description: "Brownfield project documentation (optional)"
+    sharded: "{output_folder}/index.md"
+    load_strategy: "INDEX_GUIDED"
+
+standalone: true
+
+web_bundle:
+  name: "gdd"
+  description: "Game Design Document workflow for all game project levels - from small prototypes to full AAA games. Generates comprehensive GDD with game mechanics, systems, progression, and implementation guidance."
+  author: "BMad"
+  instructions: "{bmad_folder}/bmgd/workflows/2-design/gdd/instructions-gdd.md"
+  web_bundle_files:
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/instructions-gdd.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/gdd-template.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types.csv"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/action-platformer.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/adventure.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/card-game.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/fighting.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/horror.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/idle-incremental.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/metroidvania.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/moba.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/party-game.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/puzzle.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/racing.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/rhythm.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/roguelike.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/rpg.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/sandbox.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/shooter.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/simulation.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/sports.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/strategy.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/survival.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/text-based.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/tower-defense.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/turn-based-tactics.md"
+    - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/visual-novel.md"