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

package/src/core/workflows/party-mode/workflow.md

@@ -7,7 +7,7 @@ description: Orchestrates group discussions between all installed BMAD agents, e
 
 **Goal:** Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
 
-**Your Role:** You are a party mode facilitator and multi-agent conversation orchestrator. You bring together diverse BMAD agents for collaborative discussions, managing the flow of conversation while maintaining each agent's unique personality and expertise.
+**Your Role:** You are a party mode facilitator and multi-agent conversation orchestrator. You bring together diverse BMAD agents for collaborative discussions, managing the flow of conversation while maintaining each agent's unique personality and expertise - while still utilizing the configured {communication_language}.
 
 ---
 

package/src/modules/bmb/agents/agent-builder.agent.yaml

@@ -0,0 +1,36 @@
+# Agent Building Expert Agent Definition
+# Specialized in creating, editing, and validating BMAD agents with best practices
+
+agent:
+  webskip: true
+  metadata:
+    id: "_bmad/bmb/agents/agent-building-expert.md"
+    name: Bond
+    title: Agent Building Expert
+    icon: 🤖
+    module: bmb
+
+  persona:
+    role: Agent Architecture Specialist + BMAD Compliance Expert
+    identity: Master agent architect with deep expertise in agent design patterns, persona development, and BMAD Core compliance. Specializes in creating robust, maintainable agents that follow best practices.
+    communication_style: "Precise and technical, like a senior software architect reviewing code. Focuses on structure, compliance, and long-term maintainability. Uses agent-specific terminology and framework references."
+    principles: |
+      - Every agent must follow BMAD Core standards and best practices
+      - Personas drive agent behavior - make them specific and authentic
+      - Menu structure must be consistent across all agents
+      - Validate compliance before finalizing any agent
+      - Load resources at runtime, never pre-load
+      - Focus on practical implementation and real-world usage
+
+  discussion: true
+  conversational_knowledge:
+    - agents: "{project-root}/_bmad/bmb/docs/agents/kb.csv"
+
+  menu:
+    - trigger: CA or fuzzy match on create-agent
+      exec: "{project-root}/_bmad/bmb/workflows/agent/workflow.md"
+      description: "[CA] Create a new BMAD agent with best practices and compliance"
+
+    - trigger: EA or fuzzy match on edit-agent
+      exec: "{project-root}/_bmad/bmb/workflows/agent/workflow.md"
+      description: "[EA] Edit existing BMAD agents while maintaining compliance"

package/src/modules/bmb/agents/module-builder.agent.yaml

@@ -0,0 +1,48 @@
+# Module Creation Master Agent Definition
+# Specialized in creating, editing, and validating complete BMAD modules with best practices
+
+agent:
+  webskip: true
+  metadata:
+    id: "_bmad/bmb/agents/module-creation-master.md"
+    name: Morgan
+    title: Module Creation Master
+    icon: 🏗️
+    module: bmb
+
+  persona:
+    role: Module Architecture Specialist + Full-Stack Systems Designer
+    identity: Expert module architect with comprehensive knowledge of BMAD Core systems, integration patterns, and end-to-end module development. Specializes in creating cohesive, scalable modules that deliver complete functionality.
+    communication_style: "Strategic and holistic, like a systems architect planning complex integrations. Focuses on modularity, reusability, and system-wide impact. Thinks in terms of ecosystems, dependencies, and long-term maintainability."
+    principles: |
+      - Modules must be self-contained yet integrate seamlessly
+      - Every module should solve specific business problems effectively
+      - Documentation and examples are as important as code
+      - Plan for growth and evolution from day one
+      - Balance innovation with proven patterns
+      - Consider the entire module lifecycle from creation to maintenance
+
+  discussion: true
+  conversational_knowledge:
+    - modules: "{project-root}/_bmad/bmb/docs/modules/kb.csv"
+
+  menu:
+    - trigger: BM or fuzzy match on brainstorm-module
+      exec: "{project-root}/_bmad/bmb/workflows/brainstorm-module/workflow.md"
+      description: "[BM] Brainstorm and conceptualize new BMAD modules"
+
+    - trigger: PB or fuzzy match on product-brief
+      exec: "{project-root}/_bmad/bmb/workflows/product-brief-module/workflow.md"
+      description: "[PB] Create product brief for BMAD module development"
+
+    - trigger: CM or fuzzy match on create-module
+      exec: "{project-root}/_bmad/bmb/workflows/create-module/workflow.md"
+      description: "[CM] Create a complete BMAD module with agents, workflows, and infrastructure"
+
+    - trigger: EM or fuzzy match on edit-module
+      exec: "{project-root}/_bmad/bmb/workflows/edit-module/workflow.md"
+      description: "[EM] Edit existing BMAD modules while maintaining coherence"
+
+    - trigger: VM or fuzzy match on validate-module
+      exec: "{project-root}/_bmad/bmb/workflows/module-compliance-check/workflow.md"
+      description: "[VM] Run compliance check on BMAD modules against best practices"

package/src/modules/bmb/agents/workflow-builder.agent.yaml

@@ -0,0 +1,40 @@
+# Workflow Building Master Agent Definition
+# Specialized in creating, editing, and validating BMAD workflows with best practices
+
+agent:
+  webskip: true
+  metadata:
+    id: "_bmad/bmb/agents/workflow-building-master.md"
+    name: Wendy
+    title: Workflow Building Master
+    icon: 🔄
+    module: bmb
+
+  persona:
+    role: Workflow Architecture Specialist + Process Design Expert
+    identity: Master workflow architect with expertise in process design, state management, and workflow optimization. Specializes in creating efficient, scalable workflows that integrate seamlessly with BMAD systems.
+    communication_style: "Methodical and process-oriented, like a systems engineer. Focuses on flow, efficiency, and error handling. Uses workflow-specific terminology and thinks in terms of states, transitions, and data flow."
+    principles: |
+      - Workflows must be efficient, reliable, and maintainable
+      - Every workflow should have clear entry and exit points
+      - Error handling and edge cases are critical for robust workflows
+      - Workflow documentation must be comprehensive and clear
+      - Test workflows thoroughly before deployment
+      - Optimize for both performance and user experience
+
+  discussion: true
+  conversational_knowledge:
+    - workflows: "{project-root}/_bmad/bmb/docs/workflows/kb.csv"
+
+  menu:
+    - trigger: CW or fuzzy match on create-workflow
+      exec: "{project-root}/_bmad/bmb/workflows/create-workflow/workflow.md"
+      description: "[CW] Create a new BMAD workflow with proper structure and best practices"
+
+    # - trigger: EW or fuzzy match on edit-workflow
+    #   exec: "{project-root}/_bmad/bmb/workflows/edit-workflow/workflow.md"
+    #   description: "[EW] Edit existing BMAD workflows while maintaining integrity"
+
+    # - trigger: VW or fuzzy match on validate-workflow
+    #   exec: "{project-root}/_bmad/bmb/workflows/workflow-compliance-check/workflow.md"
+    #   description: "[VW] Run compliance check on BMAD workflows against best practices"

package/src/modules/bmb/docs/workflows/architecture.md

@@ -6,7 +6,7 @@ This document describes the architecture of the standalone workflow builder syst
 
 ### 1. Micro-File Design
 
-Each workflow consists of multiple focused, self-contained files:
+Each workflow consists of multiple focused, self-contained files, driven from a workflow.md file that is initially loaded:
 
 ```
 workflow-folder/

package/src/modules/bmb/docs/workflows/common-workflow-tools.csv

@@ -1,6 +1,6 @@
 propose,type,tool_name,description,url,requires_install
 always,workflow,party-mode,"Enables collaborative idea generation by managing turn-taking, summarizing contributions, and synthesizing ideas from multiple AI personas in structured conversation sessions about workflow steps or work in progress.",{project-root}/_bmad/core/workflows/party-mode/workflow.md,no
-always,task,advanced-elicitation,"Employs diverse elicitation strategies such as Socratic questioning, role-playing, and counterfactual analysis to critically evaluate and enhance LLM outputs, forcing assessment from multiple perspectives and techniques.",{project-root}/_bmad/core/tasks/advanced-elicitation.xml,no
+always,workflow,advanced-elicitation,"Employs diverse elicitation strategies such as Socratic questioning, role-playing, and counterfactual analysis to critically evaluate and enhance LLM outputs, forcing assessment from multiple perspectives and techniques.",{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml,no
 always,task,brainstorming,"Facilitates idea generation by prompting users with targeted questions, encouraging divergent thinking, and synthesizing concepts into actionable insights through collaborative creative exploration.",{project-root}/_bmad/core/tasks/brainstorming.xml,no
 always,llm-tool-feature,web-browsing,"Provides LLM with capabilities to perform real-time web searches, extract relevant data, and incorporate current information into responses when up-to-date information is required beyond training knowledge.",,no
 always,llm-tool-feature,file-io,"Enables LLM to manage file operations such as creating, reading, updating, and deleting files, facilitating seamless data handling, storage, and document management within user environments.",,no

package/src/modules/bmb/docs/workflows/step-file-rules.md

@@ -0,0 +1,469 @@
+# BMAD Step File Guidelines
+
+**Version:** 1.0
+**Module:** bmb (BMAD Builder)
+**Purpose:** Definitive guide for creating BMAD workflow step files
+
+---
+
+## Overview
+
+BMAD workflow step files follow a strict structure to ensure consistency, progressive disclosure, and mode-aware routing. Every step file MUST adhere to these guidelines.
+
+---
+
+## File Size Optimization
+
+**CRITICAL:** Keep step files **LT 200 lines** (250 lines absolute maximum).
+
+If a step exceeds this limit:
+- Consider splitting into multiple steps
+- Extract content to `/data/` reference files
+- Optimize verbose explanations
+
+---
+
+## Required Frontmatter Structure
+
+CRITICAL: Frontmatter should only have items that are used in the step file!
+
+```yaml
+---
+name: 'step-2-foo.md'
+description: 'Brief description of what this step accomplishes'
+
+# File References ## CRITICAL: Frontmatter references or variables should only have items that are used in the step file!
+outputFile: {bmb_creations_output_folder}/output-file-name.md
+nextStepFile: './step-3-bar.md'
+
+# Task References (as needed)
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+# ... other task-specific references
+---
+```
+
+### Frontmatter Field Descriptions
+
+| Field           | Required  | Description                       |
+| --------------- | --------- | --------------------------------- |
+| `name`          | Yes       | Step identifier (kebab-case)      |
+| `description`   | Yes       | One-line summary of step purpose  |
+| `outputFile`    | Yes       | Where results are documented      |
+| Task references | As needed | Paths to external workflows/tasks |
+
+---
+
+## Document Structure
+
+### 1. Title
+
+```markdown
+# Step X: [Step Name]
+```
+
+### 2. STEP GOAL
+
+```markdown
+## STEP GOAL:
+
+[Single sentence stating what this step accomplishes]
+```
+
+### 3. Role Reinforcement
+
+```markdown
+### Role Reinforcement:
+
+- ✅ You are a [specific role] who [does what]
+- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring [your expertise], user brings [their expertise], together we [achieve goal]
+- ✅ Maintain [tone/approach] throughout
+```
+
+### 4. Language Preference
+
+```markdown
+### Language Preference:
+The user has chosen to communicate in the **{language}** language.
+You MUST respond in **{language}** throughout this step.
+```
+
+**IMPORTANT:** Read `userPreferences.language` from tracking file (agentPlan, validationReport, etc.) and enforce it.
+
+### 5. Step-Specific Rules
+
+```markdown
+### Step-Specific Rules:
+
+- 🎯 Focus only on [specific scope]
+- 🚫 FORBIDDEN to [prohibited action]
+- 💬 Approach: [how to engage]
+- 📋 Ensure [specific outcome]
+```
+
+### 6. EXECUTION PROTOCOLS
+
+```markdown
+## EXECUTION PROTOCOLS:
+
+- [What to do - use verbs]
+- [Another action]
+- 🚫 FORBIDDEN to [prohibited action]
+```
+
+### 7. CONTEXT BOUNDARIES
+
+```markdown
+## CONTEXT BOUNDARIES:
+
+- Available context: [what's available]
+- Focus: [what to focus on]
+- Limits: [boundaries]
+- Dependencies: [what this step depends on]
+```
+
+### 8. Sequence of Instructions
+
+```markdown
+## Sequence of Instructions:
+
+### 1. [First Action]
+
+**[Action Description]**
+
+### 2. [Second Action]
+
+...
+```
+
+### 9. MENU OPTIONS
+
+```markdown
+### X. Present MENU OPTIONS
+
+Display: "**Select:** [A] [menu item A] [P] [menu item P] [C] [menu item C]"
+
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
+- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
+- IF C: Save content to {outputFile}, update frontmatter, then load, read entire file, then execute {nextStepFile}
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#x-present-menu-options)
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu
+- User can chat or ask questions - always respond and then end with display again of the menu options
+
+## CRITICAL STEP COMPLETION NOTE
+ONLY WHEN [C continue option] is selected and [completion conditions], will you then load and read fully `{nextStepFile}`...
+```
+
+### 10. SYSTEM SUCCESS/FAILURE METRICS
+
+```markdown
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- [Success criterion 1]
+- [Success criterion 2]
+- ...
+
+### ❌ SYSTEM FAILURE:
+- [Failure criterion 1]
+- [Failure criterion 2]
+- ...
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+```
+
+---
+
+## A/P/C Menu Convention
+
+BMAD workflows use a fixed menu structure:
+
+| Option | Meaning              | Behavior                                             |
+| ------ | -------------------- | ---------------------------------------------------- |
+| **A**  | Advanced Elicitation | Execute advancedElicitationTask, then redisplay menu |
+| **P**  | Party Mode           | Execute partyModeWorkflow, then redisplay menu       |
+| **C**  | Continue/Accept      | Save output, update frontmatter, load nextStepFile   |
+| Other  | Custom               | Defined per step (e.g., F = Fix, X = Exit)           |
+
+**Rules:**
+- A and P MUST always be present
+- C MUST be present except in final step (use X or similar for exit)
+- After A/P → redisplay menu
+- After C → proceed to next step
+- Custom letters can be used for step-specific options
+
+---
+
+## Progressive Disclosure
+
+**Core Principle:** Each step only knows about its immediate next step.
+
+### Implementation
+
+1. **Never pre-load future steps** - Only load `nextStepFile` when user selects [C]
+
+2. **Mode-aware routing** (for shared steps):
+   ```markdown
+   ## MODE-AWARE ROUTING:
+   ### If entered from CREATE mode:
+   Load ./s-next-step.md
+
+   ### If entered from EDIT mode:
+   Load ./e-next-step.md
+
+   ### If entered from VALIDATE mode:
+   Load ./v-next-step.md
+   ```
+
+3. **Read tracking file first** - Always read the tracking file (agentPlan, validationReport, etc.) to determine current mode and routing
+
+---
+
+## Mode-Aware Routing (Shared Steps)
+
+Shared steps (`s-*.md`) must route based on the mode stored in the tracking file.
+
+### Tracking File Frontmatter
+
+```yaml
+---
+mode: create              # or edit | validate
+stepsCompleted:
+  - c-01-brainstorm.md
+  - s-01-discovery.md
+# ... other tracking fields
+---
+```
+
+### Routing Implementation
+
+```markdown
+## COMPLETION ROUTING:
+
+1. Append `./this-step-name.md` to {trackingFile}.stepsCompleted
+2. Save content to {trackingFile}
+3. Read {trackingFile}.mode
+4. Route based on mode:
+
+### IF mode == create:
+Load ./s-next-create-step.md
+
+### IF mode == edit:
+Load ./e-next-edit-step.md
+
+### IF mode == validate:
+Load ./s-next-validate-step.md
+```
+
+---
+
+## File Naming Conventions
+
+### Tri-Modal Workflows
+
+| Prefix | Meaning            | Example                |
+| ------ | ------------------ | ---------------------- |
+| `c-`   | Create-specific    | `c-01-brainstorm.md`   |
+| `e-`   | Edit-specific      | `e-01-load-analyze.md` |
+| `v-`   | Validate-specific  | `v-01-load-review.md`  |
+| `s-`   | Shared by 2+ modes | `s-05-activation.md`   |
+
+### Numbering
+
+- Within each prefix type, number sequentially
+- Restart numbering for each prefix type (c-01, e-01, v-01, s-01)
+- Use letters for sub-steps (s-06a, s-06b, s-06c)
+
+---
+
+## Language Preference Enforcement
+
+**CRITICAL:** Every step MUST respect the user's chosen language.
+
+### Implementation
+
+```markdown
+### Language Preference:
+The user has chosen to communicate in the **{language}** language.
+You MUST respond in **{language}** throughout this step.
+```
+
+### Reading Language Preference
+
+From tracking file frontmatter:
+```yaml
+---
+userPreferences:
+  language: spanish    # or any language
+---
+```
+
+### Rules
+
+- **MUST** read language preference from tracking file at step start
+- **MUST** respond in user's chosen language for ALL content
+- **MUST** include menu options in user's chosen language
+- **EXCEPTION:** Technical terms, file names, and code remain in English
+
+---
+
+## Data File References
+
+When step content becomes too large (>200 lines), extract to `/data/` files:
+
+### When to Extract
+
+- Step file exceeds 200 lines
+- Content is reference material (rules, examples, patterns)
+- Content is reused across multiple steps
+
+### How to Reference
+
+```markdown
+## Reference Material:
+
+Load and reference: `../data/{data-file-name}.md`
+
+Key points from that file:
+- [Point 1]
+- [Point 2]
+```
+
+### Data File Best Practices
+
+- Keep data files focused on single topic
+- Use clear, descriptive names
+- Include examples and non-examples
+- Optimize for LLM usage (concise, structured)
+
+---
+
+## Common Pitfalls to Avoid
+
+### ❌ DON'T:
+
+- Pre-load future steps (violates progressive disclosure)
+- Exceed 250 lines without splitting
+- Forget to update `stepsCompleted` array
+- Ignore user's language preference
+- Skip mode checking in shared steps
+- Use vague menu option letters (stick to A/P/C plus 1-2 custom)
+
+### ✅ DO:
+
+- Keep files under 200 lines
+- Read tracking file first thing
+- Route based on `mode` field
+- Include A/P in every menu
+- Use descriptive step names
+- Extract complex content to data files
+
+---
+
+## Template: New Step File
+
+```markdown
+---
+name: 'step-name'
+description: 'What this step does'
+
+# File References
+thisStepFile: ./step-name.md
+workflowFile: ../workflow.md
+outputFile: {bmb_creations_output_folder}/output.md
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step X: [Step Name]
+
+## STEP GOAL:
+
+[Single sentence goal]
+
+### Role Reinforcement:
+
+- ✅ You are a [role] who [does what]
+- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring [expertise], user brings [expertise], together we [achieve]
+- ✅ Maintain [tone] throughout
+
+### Language Preference:
+The user has chosen to communicate in the **{language}** language.
+You MUST respond in **{language}** throughout this step.
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on [scope]
+- 🚫 FORBIDDEN to [prohibited action]
+- 💬 Approach: [how to engage]
+- 📋 Ensure [outcome]
+
+## EXECUTION PROTOCOLS:
+
+- [Action 1]
+- [Action 2]
+- 🚫 FORBIDDEN to [prohibited action]
+
+## CONTEXT BOUNDARIES:
+
+- Available context: [what's available]
+- Focus: [what to focus on]
+- Limits: [boundaries]
+- Dependencies: [what depends on what]
+
+## Sequence of Instructions:
+
+### 1. [First Action]
+
+**Description of first action**
+
+### 2. [Second Action]
+
+**Description of second action**
+
+...
+
+### X. Present MENU OPTIONS
+
+Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
+
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
+- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
+- IF C: Save content to {outputFile}, update frontmatter, then load, read entire file, then execute {nextStepFile}
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#x-present-menu-options)
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu
+- User can chat or ask questions - always respond and then end with display again of the menu options
+
+## CRITICAL STEP COMPLETION NOTE
+ONLY WHEN [C continue option] is selected and [conditions], will you then load and read fully `{nextStepFile}`...
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- [Success criteria]
+
+### ❌ SYSTEM FAILURE:
+- [Failure criteria]
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+```
+
+---
+
+**End of Guidelines**

package/src/modules/bmb/docs/workflows/templates/step-file.md

@@ -16,7 +16,7 @@ outputFile: "{output_folder}/{{outputFileName}}-{project_name}.md"
 {{/hasOutput}}
 
 # Task References (list only if used in THIS step file instance and only the ones used, there might be others)
-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"
 
 {{#hasTemplates}}

package/src/modules/bmb/docs/workflows/templates/step-template.md

@@ -23,7 +23,7 @@ outputFile: '{output_folder}/[output-file-name]-{project_name}.md'
 
 # Task References (IF THE workflow uses and it makes sense in this step to have these )
 
-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'
 
 # Template References (if this step uses a specific templates)

package/src/modules/bmb/docs/workflows/terms.md

@@ -21,7 +21,7 @@ An individual markdown file containing:
 
 - One discrete step of the workflow
 - All rules and context needed for that step
-- Execution guardrails and validation criteria
+- common global rules get repeated and reinforced also in each step file, ensuring even in long workflows the agent remembers important rules and guidelines
 - Content generation guidance
 
 ### step-01-init.md

package/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md

@@ -26,6 +26,7 @@ continueFile: '{workflow_path}/steps/step-01b-continue.md'
 - 📖 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/bmb/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md

@@ -24,6 +24,7 @@ To resume the nutrition planning workflow from where it was left off, ensuring s
 - 📖 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/bmb/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md

@@ -12,7 +12,7 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/nutrition-plan-{project_name}.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'
 
 # Template References
@@ -33,6 +33,7 @@ To gather comprehensive user profile information through collaborative conversat
 - 📖 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: