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

package/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-01-init.md

@@ -36,6 +36,7 @@ Validate workflow readiness, check for existing architecture work, discover inpu
 - 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/3-technical/game-architecture/steps/step-01b-continue.md

@@ -37,6 +37,7 @@ Load the existing architecture document, determine progress, and route to the ap
 - 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}`
 
 ### Step-Specific Rules:
 

package/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-02-context.md

@@ -12,7 +12,7 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.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 @@ Load and analyze the GDD and supporting documents to understand the game's techn
 - 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/3-technical/game-architecture/steps/step-03-starter.md

@@ -12,7 +12,7 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.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 @@ Discover and evaluate game engine options and starter templates based on project
 - 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/3-technical/game-architecture/steps/step-04-decisions.md

@@ -16,7 +16,7 @@ decisionCatalog: '{workflow_path}/decision-catalog.yaml'
 architecturePatterns: '{workflow_path}/architecture-patterns.yaml'
 
 # 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'
 ---
 
@@ -37,6 +37,7 @@ Facilitate collaborative decision-making for all remaining architectural choices
 - 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/3-technical/game-architecture/steps/step-05-crosscutting.md

@@ -12,7 +12,7 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.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 patterns for concerns that affect EVERY system in the game: error handlin
 - 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/3-technical/game-architecture/steps/step-06-structure.md

@@ -12,7 +12,7 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.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 complete project structure including directory organization, file nam
 - 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:
 
@@ -212,7 +213,7 @@ Based on the conversation, prepare the content:
 ### System Location Mapping
 
 | System | Location | Responsibility |
-|--------|----------|----------------|
+| ------ | -------- | -------------- |
 {{system_mapping_table}}
 
 ### Naming Conventions
@@ -222,7 +223,7 @@ Based on the conversation, prepare the content:
 
 #### Code Elements
 | Element | Convention | Example |
-|---------|------------|---------|
+| ------- | ---------- | ------- |
 {{code_naming_table}}
 
 #### Game Assets

package/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-07-patterns.md

@@ -15,7 +15,7 @@ outputFile: '{output_folder}/game-architecture.md'
 patternCategories: '{workflow_path}/pattern-categories.csv'
 
 # 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'
 ---
 
@@ -36,6 +36,7 @@ Define implementation patterns that ensure multiple AI agents write compatible,
 - 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/3-technical/game-architecture/steps/step-08-validation.md

@@ -13,7 +13,7 @@ outputFile: '{output_folder}/game-architecture.md'
 checklistFile: '{workflow_path}/checklist.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'
 ---
 
@@ -34,6 +34,7 @@ Validate that the architecture is coherent, complete, and ready to guide AI agen
 - 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:
 
@@ -96,12 +97,12 @@ Verifying every GDD requirement has architectural support:
 
 **Core Systems:**
 | System | Architecture Support | Status |
-|--------|---------------------|--------|
+| ------ | -------------------- | ------ |
 {{systems_coverage_table}}
 
 **Technical Requirements:**
 | Requirement | How Addressed | Status |
-|-------------|---------------|--------|
+| ----------- | ------------- | ------ |
 {{requirements_coverage_table}}
 
 {{if_gaps_found}}

package/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-09-complete.md

@@ -31,6 +31,7 @@ Generate the executive summary, finalize the document, update workflow status, a
 - 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/3-technical/game-architecture/workflow.md

@@ -44,6 +44,7 @@ To begin, load and execute step-01-init.md:
 - **NEVER** mention time estimates
 - **ALWAYS** present options and wait for user selection
 - **FOLLOW** the step sequence exactly - no skipping or optimizing
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## Agent Role
 

package/src/modules/bmgd/workflows/3-technical/generate-project-context/steps/step-01-discover.md

@@ -8,6 +8,7 @@
 - FOCUS on discovering existing project context and technology stack
 - IDENTIFY critical implementation rules that AI agents need
 - ABSOLUTELY NO TIME ESTIMATES
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmgd/workflows/3-technical/generate-project-context/steps/step-02-generate.md

@@ -8,6 +8,7 @@
 - FOCUS on unobvious rules that AI agents need to be reminded of
 - KEEP CONTENT LEAN - optimize for LLM context efficiency
 - ABSOLUTELY NO TIME ESTIMATES
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 
@@ -28,7 +29,7 @@ This step will generate content and present choices for each rule category:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
 - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding

package/src/modules/bmgd/workflows/3-technical/generate-project-context/steps/step-03-complete.md

@@ -8,6 +8,7 @@
 - FOCUS on finalizing a lean, LLM-optimized project context
 - ENSURE all critical rules are captured and actionable
 - ABSOLUTELY NO TIME ESTIMATES
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmgd/workflows/3-technical/generate-project-context/workflow.md

@@ -32,6 +32,7 @@ Load config from `{project-root}/_bmad/bmgd/config.yaml` and resolve:
 - `project_name`, `output_folder`, `user_name`
 - `communication_language`, `document_output_language`, `game_dev_experience`
 - `date` as system-generated current datetime
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Paths
 

package/src/modules/bmgd/workflows/bmgd-quick-flow/create-tech-spec/workflow.yaml

@@ -21,7 +21,7 @@ instructions: "{installed_path}/instructions.md"
 quick_dev_workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-dev/workflow.yaml"
 quick_prototype_workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml"
 party_mode_exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-advanced_elicitation: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+advanced_elicitation: "{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml"
 
 standalone: true
 web_bundle: false

package/src/modules/bmgd/workflows/bmgd-quick-flow/quick-dev/workflow.yaml

@@ -23,7 +23,7 @@ checklist: "{installed_path}/checklist.md"
 # Related workflows
 quick_prototype_workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml"
 party_mode_exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-advanced_elicitation: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+advanced_elicitation: "{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml"
 
 # Routing resources (lazy-loaded)
 workflow_init: "{project-root}/_bmad/bmgd/workflows/workflow-status/init/workflow.yaml"

package/src/modules/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml

@@ -23,7 +23,7 @@ checklist: "{installed_path}/checklist.md"
 # Related workflows
 quick_dev_workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-dev/workflow.yaml"
 party_mode_exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-advanced_elicitation: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+advanced_elicitation: "{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml"
 
 # Game-specific references
 gdd_patterns:

package/src/modules/bmm/agents/pm.agent.yaml

@@ -10,12 +10,14 @@ agent:
     module: bmm
 
   persona:
-    role: Investigative Product Strategist + Market-Savvy PM
+    role: Product Manager specializing in collaborative PRD creation through user interviews, requirement discovery, and stakeholder alignment.
     identity: Product management veteran with 8+ years launching B2B and consumer products. Expert in market research, competitive analysis, and user behavior insights.
     communication_style: "Asks 'WHY?' relentlessly like a detective on a case. Direct and data-sharp, cuts through fluff to what actually matters."
     principles: |
-      - Uncover the deeper WHY behind every requirement. Ruthless prioritization to achieve MVP goals. Proactively identify risks.
-      - Align efforts with measurable business impact. Back all claims with data and user insights.
+      - Channel expert product manager thinking: draw upon deep knowledge of user-centered design, Jobs-to-be-Done framework, opportunity scoring, and what separates great products from mediocre ones
+      - PRDs emerge from user interviews, not template filling - discover what users actually need
+      - Ship the smallest thing that validates the assumption - iteration over perfection
+      - Technical feasibility is a constraint, not the driver - user value first
       - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`
 
   menu:

package/src/modules/bmm/agents/quick-flow-solo-dev.agent.yaml

@@ -19,7 +19,7 @@ agent:
 
   menu:
     - trigger: TS or fuzzy match on tech-spec
-      workflow: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml"
+      exec: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.md"
       description: "[TS] Architect a technical spec with implementation-ready stories (Required first step)"
 
     - trigger: QD or fuzzy match on quick-dev

package/src/modules/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md

@@ -29,6 +29,7 @@ Initialize the product brief workflow by detecting continuation state and settin
 - 📖 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/bmm/workflows/1-analysis/create-product-brief/steps/step-01b-continue.md

@@ -25,6 +25,7 @@ Resume the product brief workflow from where it was left off, ensuring smooth co
 - 📖 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/bmm/workflows/1-analysis/create-product-brief/steps/step-02-vision.md

@@ -12,7 +12,7 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.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'
 ---
 
@@ -30,6 +30,7 @@ Conduct comprehensive product vision discovery to define the core problem, solut
 - 📖 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/bmm/workflows/1-analysis/create-product-brief/steps/step-03-users.md

@@ -12,7 +12,7 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.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'
 ---
 
@@ -30,6 +30,7 @@ Define target users with rich personas and map their key interactions with the p
 - 📖 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/bmm/workflows/1-analysis/create-product-brief/steps/step-04-metrics.md

@@ -12,7 +12,7 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.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'
 ---
 
@@ -30,6 +30,7 @@ Define comprehensive success metrics that include user success, business objecti
 - 📖 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/bmm/workflows/1-analysis/create-product-brief/steps/step-05-scope.md

@@ -12,7 +12,7 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.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'
 ---
 
@@ -30,6 +30,7 @@ Define MVP scope with clear boundaries and outline future vision through collabo
 - 📖 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/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md

@@ -25,6 +25,7 @@ Complete the product brief workflow, update status files, and provide guidance o
 - 📖 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/bmm/workflows/1-analysis/research/domain-steps/step-01-init.md

@@ -10,6 +10,7 @@
 - 📋 YOU ARE A DOMAIN RESEARCH PLANNER, not content generator
 - 💬 ACKNOWLEDGE and CONFIRM understanding of domain research goals
 - 🔍 This is SCOPE CONFIRMATION ONLY - no web research yet
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on market size, growth, and industry dynamics
 - 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
 - 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/1-analysis/research/domain-steps/step-03-competitive-landscape.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on key players, market share, and competitive dynamics
 - 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
 - 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/1-analysis/research/domain-steps/step-04-regulatory-focus.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on compliance requirements and regulatory landscape
 - 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
 - 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/1-analysis/research/domain-steps/step-05-technical-trends.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on emerging technologies and innovation patterns
 - 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
 - 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/1-analysis/research/domain-steps/step-06-research-synthesis.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on comprehensive synthesis and authoritative conclusions
 - 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
 - 📄 PRODUCE COMPREHENSIVE DOCUMENT with narrative intro, TOC, and summary
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/1-analysis/research/market-steps/step-01-init.md

@@ -9,6 +9,7 @@
 - 🔍 NO WEB RESEARCH in init - that's for later steps
 - 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research
 - 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/1-analysis/research/market-steps/step-02-customer-behavior.md

@@ -10,6 +10,7 @@
 - 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
 - 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research
 - 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/1-analysis/research/market-steps/step-02-customer-insights.md

@@ -10,6 +10,7 @@
 - 📋 YOU ARE A CUSTOMER INSIGHTS ANALYST, not content generator
 - 💬 FOCUS on customer behavior and needs analysis
 - 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/1-analysis/research/market-steps/step-03-customer-pain-points.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on customer pain points, challenges, and unmet needs
 - 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
 - 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/1-analysis/research/market-steps/step-04-customer-decisions.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on customer decision processes and journey mapping
 - 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
 - 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/1-analysis/research/market-steps/step-05-competitive-analysis.md

@@ -10,6 +10,7 @@
 - 📋 YOU ARE A COMPETITIVE ANALYST, not content generator
 - 💬 FOCUS on competitive landscape and market positioning
 - 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/1-analysis/research/market-steps/step-06-research-completion.md

@@ -10,6 +10,7 @@
 - 📋 YOU ARE A MARKET RESEARCH STRATEGIST, not content generator
 - 💬 FOCUS on strategic recommendations and actionable insights
 - 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/1-analysis/research/technical-steps/step-01-init.md

@@ -10,6 +10,7 @@
 - 📋 YOU ARE A TECHNICAL RESEARCH PLANNER, not content generator
 - 💬 ACKNOWLEDGE and CONFIRM understanding of technical research goals
 - 🔍 This is SCOPE CONFIRMATION ONLY - no web research yet
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/1-analysis/research/technical-steps/step-02-technical-overview.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on languages, frameworks, tools, and platforms
 - 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
 - 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/1-analysis/research/technical-steps/step-03-integration-patterns.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on APIs, protocols, and system interoperability
 - 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
 - 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/1-analysis/research/technical-steps/step-04-architectural-patterns.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on architectural patterns and design decisions
 - 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
 - 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/1-analysis/research/technical-steps/step-05-implementation-research.md

@@ -10,6 +10,7 @@
 - 📋 YOU ARE AN IMPLEMENTATION ENGINEER, not content generator
 - 💬 FOCUS on implementation approaches and technology adoption
 - 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/1-analysis/research/technical-steps/step-06-research-synthesis.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on comprehensive technical synthesis and authoritative conclusions
 - 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
 - 📄 PRODUCE COMPREHENSIVE DOCUMENT with narrative intro, TOC, and summary
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/1-analysis/research/workflow.md

@@ -145,7 +145,7 @@ After understanding the research topic and goals, identify the most appropriate
 
 ### Research Type Routing
 
-<critical>Based on user selection, route to appropriate sub-workflow with the discovered topic using the following IF block sets of instructions.</critical>
+<critical>Based on user selection, route to appropriate sub-workflow with the discovered topic using the following IF block sets of instructions. YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`</critical>
 
 #### If Market Research:
 

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01-init.md

@@ -10,6 +10,7 @@
 - 📋 YOU ARE A UX FACILITATOR, not a content generator
 - 💬 FOCUS on initialization and setup only - don't look ahead to future steps
 - 🚪 DETECT existing workflow state and handle continuation properly
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01b-continue.md

@@ -10,6 +10,7 @@
 - 📋 YOU ARE A UX FACILITATOR, not a content generator
 - 💬 FOCUS on understanding where we left off and continuing appropriately
 - 🚪 RESUME workflow from exact point where it was interrupted
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md

@@ -10,6 +10,7 @@
 - 📋 YOU ARE A UX FACILITATOR, not a content generator
 - 💬 FOCUS on understanding project context and user needs
 - 🎯 COLLABORATIVE discovery, not assumption-based design
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 
@@ -29,7 +30,7 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
 - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding