bmad-method 6.0.0-alpha.21 → 6.0.0-alpha.23

package/src/modules/bmgd/agents/game-qa.agent.yaml

@@ -7,6 +7,7 @@ agent:
     title: Game QA Architect
     icon: 🧪
     module: bmgd
+    hasSidecar: false
 
   persona:
     role: Game QA Architect + Test Automation Specialist
@@ -55,6 +56,6 @@ agent:
       description: "[TR] Review test quality and coverage"
 
     - trigger: AE or fuzzy match on advanced-elicitation
-      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml"
       description: "[AE] Advanced elicitation techniques to challenge the LLM to get better results"
       web-only: true

package/src/modules/bmgd/agents/game-scrum-master.agent.yaml

@@ -7,6 +7,7 @@ agent:
     title: Game Dev Scrum Master
     icon: 🎯
     module: bmgd
+    hasSidecar: false
 
   persona:
     role: Game Development Scrum Master + Sprint Orchestrator
@@ -54,6 +55,6 @@ agent:
       description: "[CC] Navigate significant changes during game dev sprint (When implementation is off-track)"
 
     - trigger: AE or fuzzy match on advanced-elicitation
-      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml"
       description: "[AE] Advanced elicitation techniques to challenge the LLM to get better results"
       web-only: true

package/src/modules/bmgd/agents/game-solo-dev.agent.yaml

@@ -7,6 +7,7 @@ agent:
     title: Game Solo Dev
     icon: 🎮
     module: bmgd
+    hasSidecar: false
 
   persona:
     role: Elite Indie Game Developer + Quick Flow Specialist
@@ -35,7 +36,7 @@ agent:
       description: "[QD] Implement features end-to-end solo with game-specific considerations"
 
     - trigger: TS or fuzzy match on tech-spec
-      workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/create-tech-spec/workflow.yaml"
+      workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-spec/workflow.yaml"
       description: "[TS] Architect a technical spec with implementation-ready stories"
 
     - trigger: CR or fuzzy match on code-review
@@ -47,6 +48,6 @@ agent:
       description: "[TF] Set up automated testing for your game engine"
 
     - trigger: AE or fuzzy match on advanced-elicitation
-      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml"
       description: "[AE] Advanced elicitation techniques to challenge the LLM to get better results"
       web-only: true

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

@@ -1,4 +1,4 @@
-<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/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>

package/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-01-init.md

@@ -6,8 +6,8 @@ description: 'Initialize the game brainstorming workflow and validate readiness'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/brainstorm-game'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-01-init.md'
-nextStepFile: '{workflow_path}/steps/step-02-context.md'
+thisStepFile: './step-01-init.md'
+nextStepFile: './step-02-context.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/brainstorming-session-{date}.md'
 
@@ -33,6 +33,7 @@ Validate workflow readiness, check for workflow status tracking, and prepare for
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 
@@ -92,10 +93,11 @@ Handle each scenario appropriately with user prompts.
 **Brainstorming Rules:**
 
 - There are no bad ideas in brainstorming
-- Quantity over quality initially
+- **Quantity over quality:** Our goal is **100+ ideas**. The first 20 are obvious; as brainstorming progresses, quality must grow (the magic happens in ideas 50-100).
 - Build on ideas rather than criticize
 - Wild ideas are welcome
 - Defer judgment until later
+- We will stay in generative mode until you feel we've thoroughly explored the space.
 
 **What we'll do:**
 

package/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-02-context.md

@@ -6,15 +6,15 @@ description: 'Load game-specific brainstorming context and techniques'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/brainstorm-game'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-02-context.md'
-nextStepFile: '{workflow_path}/steps/step-03-ideation.md'
+thisStepFile: './step-02-context.md'
+nextStepFile: './step-03-ideation.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/brainstorming-session-{date}.md'
 
 # Context Files
 gameContext: '{workflow_path}/game-context.md'
 gameBrainMethods: '{workflow_path}/game-brain-methods.csv'
-coreBrainstorming: '{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml'
+coreBrainstorming: '{project-root}/_bmad/core/workflows/brainstorming/workflow.md'
 ---
 
 # Step 2: Load Context
@@ -34,6 +34,7 @@ Load game-specific brainstorming context and techniques to guide the ideation se
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-03-ideation.md

@@ -6,16 +6,16 @@ description: 'Execute the brainstorming session with game-specific techniques'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/brainstorm-game'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-03-ideation.md'
-nextStepFile: '{workflow_path}/steps/step-04-complete.md'
+thisStepFile: './step-03-ideation.md'
+nextStepFile: './step-04-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/brainstorming-session-{date}.md'
 
 # Core Brainstorming Reference
-coreBrainstorming: '{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml'
+coreBrainstorming: '{project-root}/_bmad/core/workflows/brainstorming/workflow.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
@@ -31,11 +31,30 @@ Facilitate the actual brainstorming session using selected techniques. Capture a
 
 ### Universal Rules:
 
+- ✅ YOU ARE A CREATIVE FACILITATOR, engaging in genuine back-and-forth coaching
+- 🎯 AIM FOR 100+ IDEAS before suggesting organization - quantity unlocks quality (quality must grow as we progress)
+- 🔄 DEFAULT IS TO KEEP EXPLORING - only move to organization when user explicitly requests it
+- 🧠 **THOUGHT BEFORE INK (CoT):** Before generating each idea, you must internally reason: "What mechanic/theme haven't we explored yet? What would make this concept 'break the genre'?"
+- 🛡️ **ANTI-BIAS DOMAIN PIVOT:** Every 10 ideas, review existing themes and consciously pivot to an orthogonal domain (e.g., Mechanics -> Monetization -> Lore -> Accessibility).
+- 🌡️ **SIMULATED TEMPERATURE:** Act as if your creativity is set to 0.85 - take wilder leaps and suggest "provocative" game loops.
+- ⏱️ Spend minimum 30-45 minutes in active ideation before offering to conclude
+- 🎯 EXECUTE ONE TECHNIQUE ELEMENT AT A TIME with interactive exploration
+- 📋 RESPOND DYNAMICALLY to user insights and build upon their ideas
+- 🔍 ADAPT FACILITATION based on user engagement and emerging directions
+- 💬 CREATE TRUE COLLABORATION, not question-answer sequences
 - NEVER generate content without user input
 - CRITICAL: Read the complete step file before taking any action
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+## IDEA FORMAT TEMPLATE:
+
+Every idea you capture should follow this structure:
+**[Category #X]**: [Mnemonic Title]
+_Core Loop_: [2-3 sentence description of player action]
+_Novelty_: [What makes this different from generic games]
 
 ### Role Reinforcement:
 
@@ -54,15 +73,17 @@ Facilitate the actual brainstorming session using selected techniques. Capture a
 ## EXECUTION PROTOCOLS:
 
 - Show your analysis before taking any action
-- Present A/P/C menu after ideation session
+- Present the exploration menu after ideation session
 - ONLY proceed when user chooses C (Continue)
 - Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
 
-## COLLABORATION MENUS (A/P/C):
+## EXPLORATION & COLLABORATION MENU:
 
-- **A (Advanced Elicitation)**: Dig deeper into promising ideas
-- **P (Party Mode)**: Get multiple perspectives on concepts
-- **C (Continue)**: Save ideas and complete session
+- [K] **Keep exploring current technique** - Push for more ideas using the current method
+- [T] **Try a different game design technique** - Switch to another method from the library
+- [A] **Advanced Elicitation** - Dig deeper into promising ideas using reasoning techniques
+- [P] **Party Mode** - Get multiple perspectives on concepts from other agents
+- [C] **Continue** - Save ideas and move to organization phase
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
@@ -176,30 +197,16 @@ Your choice:"
 
 ### 7. Generate Ideation Section
 
-Based on all ideas captured, prepare the content:
+Based on all ideas captured, prepare the content using our **IDEA FORMAT TEMPLATE**:
 
 ```markdown
 ## Ideas Generated
 
-### Concept 1: {{concept_name}}
-
-{{full_concept_description}}
-
-**Core Elements:**
+**[Category #X]**: [Mnemonic Title]
+_Core Loop_: [2-3 sentence description of player action]
+_Novelty_: [What makes this different from generic games]
 
-- {{element_1}}
-- {{element_2}}
-
-**Questions to Explore:**
-
-- {{question_1}}
-- {{question_2}}
-
----
-
-### Concept 2: {{concept_name}}
-
-{{repeat_structure}}
+(Repeat for all ideas generated)
 
 ---
 
@@ -210,10 +217,6 @@ Based on all ideas captured, prepare the content:
 ## Promising Combinations
 
 {{combination_ideas}}
-
-## Raw Ideas List
-
-{{all_ideas_bullet_points}}
 ```
 
 ### 8. Present Content and Menu
@@ -228,30 +231,33 @@ Here's everything we captured:
 
 **Session Stats:**
 
-- Ideas generated: {{count}}
-- Concepts developed: {{count}}
-- Themes identified: {{count}}
+- Ideas generated: {{idea_count}}
+- Concepts developed: {{concept_count}}
+- Themes identified: {{theme_count}}
 
 **Select an Option:**
-[A] Advanced Elicitation - Dig deeper into promising ideas
-[P] Party Mode - Get multiple perspectives on concepts
-[C] Continue - Save ideas and complete session (Step 4 of 4)"
+[K] **Keep exploring current technique** - We're just getting warmed up!
+[T] **Try a different game design technique** - Fresh perspective on the same concept
+[A] **Advanced Elicitation** - Go deeper on a specific concept (Dig deeper)
+[P] **Party Mode** - Get multiple perspectives on concepts from other agents
+[C] **Continue to Organization** - Only when you feel we've thoroughly explored (Step 4 of 4)
+
+**Default recommendation:** Unless you feel we've generated at least 100+ ideas, I suggest we keep exploring! The best insights often come after the obvious ideas are exhausted.
 
 ### 9. Handle Menu Selection
 
-#### IF A (Advanced Elicitation):
+#### IF K, T, or A (Keep Exploring):
 
-- Deep dive into selected concepts
-- Ask user: "Accept these additions? (y/n)"
-- If yes: Update content, return to A/P/C menu
-- If no: Keep original, return to A/P/C menu
+- **Restart the ideation loop** based on the chosen path
+- For option A, invoke Advanced Elicitation: `{advancedElicitationTask}`
+- Keep user in generative mode
 
 #### IF P (Party Mode):
 
-- Get diverse perspectives on concepts
+- Get diverse perspectives on concepts using `{partyModeWorkflow}`
 - Ask user: "Accept these perspectives? (y/n)"
-- If yes: Update content, return to A/P/C menu
-- If no: Keep original, return to A/P/C menu
+- If yes: Update content, return to exploration menu
+- If no: Keep original, return to exploration menu
 
 #### IF C (Continue):
 

package/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-04-complete.md

@@ -6,7 +6,7 @@ description: 'Complete the brainstorming session with summary and next steps'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/brainstorm-game'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-04-complete.md'
+thisStepFile: './step-04-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/brainstorming-session-{date}.md'
 
@@ -31,6 +31,7 @@ Finalize the brainstorming session, generate actionable next steps, update workf
 - CRITICAL: Read the complete step file before taking any action
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

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

@@ -28,12 +28,14 @@ stepsCompleted: [1, 2, 3, ...] # Array of completed step numbers
 To begin, load and execute step-01-init.md:
 
 ```
-{workflow_path}/steps/step-01-init.md
+./step-01-init.md
 ```
 
 ## Critical Rules
 
 - This is a meta-workflow that orchestrates CIS brainstorming
+- **Critical Mindset:** Your job is to keep the user in generative exploration mode as long as possible. The best brainstorming sessions feel slightly uncomfortable - like you've pushed past the obvious ideas into truly novel territory. Resist the urge to organize or conclude. When in doubt, ask another question, try another technique, or dig deeper into a promising thread.
+- **Quantity Goal:** Aim for 100+ ideas before any organization. The first 20 ideas are usually obvious - the magic happens in ideas 50-100.
 - Use game-specific techniques from game-brain-methods.csv
 - Apply game-context.md guidance throughout
 - **NEVER** mention time estimates
@@ -43,7 +45,9 @@ To begin, load and execute step-01-init.md:
 
 You are a creative facilitator specializing in game ideation:
 
+- **Generative Facilitator:** Your priority is quantity and exploration over early documentation. Keep the user in "Yes And" mode.
 - Draw out user's game concepts and ideas
 - Apply game-specific brainstorming techniques
 - Help users explore mechanics, themes, and experiences
 - Capture and organize ideas for later refinement
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`

package/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml

@@ -22,7 +22,7 @@ game_context: "{installed_path}/game-context.md"
 game_brain_methods: "{installed_path}/game-brain-methods.csv"
 
 # CORE brainstorming workflow reference (for technique merging)
-core_brainstorming: "{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml"
+core_brainstorming: "{project-root}/_bmad/core/workflows/brainstorming/workflow.md"
 
 # Output configuration
 default_output_file: "{output_folder}/brainstorming-session-{date}.md"
@@ -58,5 +58,5 @@ web_bundle:
     # Context files
     - "_bmad/bmgd/workflows/1-preproduction/brainstorm-game/game-context.md"
     - "_bmad/bmgd/workflows/1-preproduction/brainstorm-game/game-brain-methods.csv"
-  existing_workflows:
-    - core_brainstorming: "_bmad/core/workflows/brainstorming/workflow.yaml"
+dependencies:
+  - "_bmad/core/workflows/brainstorming/workflow.md"

package/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-01-init.md

@@ -6,9 +6,9 @@ description: 'Initialize the Game Brief workflow by detecting continuation state
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-01-init.md'
-nextStepFile: '{workflow_path}/steps/step-02-vision.md'
-continueStepFile: '{workflow_path}/steps/step-01b-continue.md'
+thisStepFile: './step-01-init.md'
+nextStepFile: './step-02-vision.md'
+continueStepFile: './step-01b-continue.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-brief.md'
 
@@ -33,6 +33,7 @@ Initialize the Game Brief workflow by detecting continuation state, discovering
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-01b-continue.md

@@ -6,7 +6,7 @@ description: 'Resume an interrupted Game Brief workflow from the last completed
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+thisStepFile: './step-01b-continue.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-brief.md'
 ---
@@ -25,6 +25,7 @@ Resume the Game Brief workflow from where it was left off, ensuring smooth conti
 - CRITICAL: Read the complete step file before taking any action
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-02-vision.md

@@ -6,13 +6,13 @@ description: 'Define the core game vision including name, concept, pitch, and vi
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-02-vision.md'
-nextStepFile: '{workflow_path}/steps/step-03-market.md'
+thisStepFile: './step-02-vision.md'
+nextStepFile: './step-03-market.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-brief.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
@@ -33,6 +33,7 @@ Capture the core game vision including the working title, one-sentence concept,
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-03-market.md

@@ -6,13 +6,13 @@ description: 'Define target audience and market context'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-03-market.md'
-nextStepFile: '{workflow_path}/steps/step-04-fundamentals.md'
+thisStepFile: './step-03-market.md'
+nextStepFile: './step-04-fundamentals.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-brief.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
@@ -33,6 +33,7 @@ Define the primary and secondary target audiences with specific demographics, an
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-04-fundamentals.md

@@ -6,13 +6,13 @@ description: 'Define core gameplay pillars, mechanics, and player experience goa
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-04-fundamentals.md'
-nextStepFile: '{workflow_path}/steps/step-05-scope.md'
+thisStepFile: './step-04-fundamentals.md'
+nextStepFile: './step-05-scope.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-brief.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
@@ -33,6 +33,7 @@ Define the core gameplay pillars (fundamental design tenets), primary mechanics
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-05-scope.md

@@ -6,13 +6,13 @@ description: 'Define project scope including platforms, constraints, and resourc
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-05-scope.md'
-nextStepFile: '{workflow_path}/steps/step-06-references.md'
+thisStepFile: './step-05-scope.md'
+nextStepFile: './step-06-references.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-brief.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
@@ -33,6 +33,7 @@ Define realistic project constraints including target platforms, budget consider
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-06-references.md

@@ -6,13 +6,13 @@ description: 'Define inspiration games, competitive analysis, and key differenti
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-06-references.md'
-nextStepFile: '{workflow_path}/steps/step-07-content.md'
+thisStepFile: './step-06-references.md'
+nextStepFile: './step-07-content.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-brief.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
@@ -33,6 +33,7 @@ Identify inspiration games (what you're drawing from and NOT taking), analyze co
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-07-content.md

@@ -6,13 +6,13 @@ description: 'Define content framework, art/audio direction, and risk assessment
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-07-content.md'
-nextStepFile: '{workflow_path}/steps/step-08-complete.md'
+thisStepFile: './step-07-content.md'
+nextStepFile: './step-08-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-brief.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
@@ -33,6 +33,7 @@ Define the content framework (world, narrative approach, volume), art and audio
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-08-complete.md

@@ -6,7 +6,7 @@ description: 'Define success criteria and complete the game brief with handoff g
 workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-08-complete.md'
+thisStepFile: './step-08-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-brief.md'
 
@@ -30,6 +30,7 @@ Define MVP scope, success metrics, immediate next steps, and provide clear hando
 - CRITICAL: Read the complete step file before taking any action
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/1-preproduction/game-brief/workflow.md

@@ -56,6 +56,7 @@ Load and read full config from {main_config} and resolve:
 - `project_name`, `output_folder`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
 - `date` as system-generated current datetime
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### 2. First Step EXECUTION
 

package/src/modules/bmgd/workflows/2-design/gdd/steps/step-01-init.md

@@ -6,9 +6,9 @@ description: 'Initialize the GDD workflow by detecting continuation state and se
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/gdd'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-01-init.md'
-nextStepFile: '{workflow_path}/steps/step-02-context.md'
-continueStepFile: '{workflow_path}/steps/step-01b-continue.md'
+thisStepFile: './step-01-init.md'
+nextStepFile: './step-02-context.md'
+continueStepFile: './step-01b-continue.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/gdd.md'
 
@@ -35,6 +35,7 @@ Initialize the GDD workflow by detecting continuation state, discovering input d
 - CRITICAL: Read the complete step file before taking any action
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/2-design/gdd/steps/step-01b-continue.md

@@ -6,7 +6,7 @@ description: 'Resume an interrupted GDD workflow from the last completed step'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/gdd'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+thisStepFile: './step-01b-continue.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/gdd.md'
 ---
@@ -25,6 +25,7 @@ Resume the GDD workflow from where it was left off, ensuring smooth continuation
 - CRITICAL: Read the complete step file before taking any action
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement: