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

package/docs/modules/core/brainstorming.md

@@ -0,0 +1,100 @@
+# Brainstorming
+
+**Facilitate structured creative sessions using 60+ proven ideation techniques.**
+
+The Brainstorming workflow is an interactive facilitation system that helps you unlock your own creativity. The AI acts as coach, guide, and creative partner—using proven techniques to draw out ideas and insights that are already within you.
+
+**Important:** Every idea comes from you. The workflow creates the conditions for your best thinking to emerge through guided exploration, but you are the source.
+
+---
+
+## When to Use It
+
+- Breaking through creative blocks on a specific challenge
+- Generating innovative ideas for products, features, or solutions
+- Exploring a problem from completely new angles
+- Systematically developing ideas from raw concepts to actionable plans
+- Team ideation (with collaborative techniques) or personal creative exploration
+
+---
+
+## How It Works
+
+### 1. Session Setup
+Define your topic, goals, and any constraints.
+
+### 2. Choose Your Approach
+
+| Approach | Description |
+|----------|-------------|
+| **User-Selected** | Browse the full technique library and pick what appeals to you |
+| **AI-Recommended** | Get customized technique suggestions based on your goals |
+| **Random Selection** | Discover unexpected methods through serendipitous technique combinations |
+| **Progressive Flow** | Journey systematically from expansive exploration to focused action planning |
+
+### 3. Interactive Facilitation
+Work through techniques with true collaborative coaching. The AI asks probing questions, builds on your ideas, and helps you think deeper—but your ideas are the source.
+
+### 4. Idea Organization
+All your generated ideas are organized into themes and prioritized.
+
+### 5. Action Planning
+Top ideas get concrete next steps, resource requirements, and success metrics.
+
+---
+
+## What You Get
+
+A comprehensive session document that captures the entire journey:
+
+- Topic, goals, and session parameters
+- Each technique used and how it was applied
+- Your contributions and the ideas you generated
+- Thematic organization connecting related insights
+- Prioritized ideas with action plans
+- Session highlights and key breakthroughs
+
+This document becomes a permanent record of your creative process—valuable for future reference, sharing with stakeholders, or continuing the session later.
+
+---
+
+## Technique Categories
+
+| Category | Focus |
+|----------|-------|
+| **Collaborative** | Team dynamics and inclusive participation |
+| **Creative** | Breakthrough thinking and paradigm shifts |
+| **Deep** | Root cause analysis and strategic insight |
+| **Structured** | Organized frameworks and systematic exploration |
+| **Theatrical** | Playful, radical perspectives |
+| **Wild** | Boundary-pushing, extreme thinking |
+| **Biomimetic** | Nature-inspired solutions |
+| **Quantum** | Quantum principles for innovation |
+| **Cultural** | Traditional knowledge and cross-cultural approaches |
+| **Introspective Delight** | Inner wisdom and authentic exploration |
+
+---
+
+## Key Features
+
+- **Interactive coaching** — Pulls ideas *out* of you, doesn't generate them for you
+- **On-demand loading** — Techniques loaded from a comprehensive library as needed
+- **Session preservation** — Every step, insight, and action plan is documented
+- **Continuation support** — Pause sessions and return later, or extend with additional techniques
+
+---
+
+## Workflow Integration
+
+Brainstorming is a core workflow designed to be invoked and configured by other modules. When called from another workflow, it accepts contextual parameters:
+
+| Parameter | Description |
+|-----------|-------------|
+| **Topic focus** | What the brainstorming should help discover or solve |
+| **Guardrails** | Constraints, boundaries, or must-avoid areas |
+| **Output goals** | What the final output needs to accomplish for the calling workflow |
+| **Context files** | Project-specific guidance to inform technique selection |
+
+### Example
+
+When creating a new module in the BMad Builder workflow, Brainstorming can be invoked with guardrails around the module's purpose and a goal to discover key features, user needs, or architectural considerations. The session becomes focused on producing exactly what the module creation workflow needs.

package/docs/modules/core/core-tasks.md

@@ -0,0 +1,64 @@
+# Core Tasks
+
+Core Tasks are reusable task definitions that can be invoked by any BMAD module, workflow, or agent. These tasks provide standardized functionality for common operations.
+
+## Table of Contents
+
+- [Index Docs](#index-docs) — Generate directory index files
+- [Adversarial Review](#adversarial-review-general) — Critical content review
+- [Shard Document](#shard-document) — Split large documents into sections
+
+---
+
+## Index Docs
+
+**Generates or updates an index.md file documenting all documents in a specified directory.**
+
+This task scans a target directory, reads file contents to understand their purpose, and creates a well-organized index with accurate descriptions. Files are grouped by type, purpose, or subdirectory, and descriptions are generated from actual content rather than guessing from filenames.
+
+**Use it when:** You need to create navigable documentation for a folder of markdown files, or you want to maintain an updated index as content evolves.
+
+**How it works:**
+1. Scan the target directory for files and subdirectories
+2. Group content by type, purpose, or location
+3. Read each file to generate brief (3-10 word) descriptions based on actual content
+4. Create or update index.md with organized listings using relative paths
+
+**Output format:** A markdown index with sections for Files and Subdirectories, each entry containing a relative link and description.
+
+---
+
+## Adversarial Review (General)
+
+**Performs a cynical, skeptical review of any content to identify issues and improvement opportunities.**
+
+This task applies adversarial thinking to content review—approaching the material with the assumption that problems exist. It's designed to find what's missing, not just what's wrong, and produces at least ten specific findings. The reviewer adopts a professional but skeptical tone, looking for gaps, inconsistencies, oversights, and areas that need clarification.
+
+**Use it when:** You need a critical eye on code diffs, specifications, user stories, documentation, or any artifact before finalizing. It's particularly valuable before merging code, releasing documentation, or considering a specification complete.
+
+**How it works:**
+1. Load the content to review (diff, branch, uncommitted changes, document, etc.)
+2. Perform adversarial analysis with extreme skepticism—assume problems exist
+3. Find at least ten issues to fix or improve
+4. Output findings as a markdown list
+
+**Note:** This task is designed to run in a separate subagent/process with read access to the project but no prior context, ensuring an unbiased review.
+
+---
+
+## Shard Document
+
+**Splits large markdown documents into smaller, organized files based on level 2 (##) sections.**
+
+Uses the `@kayvan/markdown-tree-parser` tool to automatically break down large documents into a folder structure. Each level 2 heading becomes a separate file, and an index.md is generated to tie everything together. This makes large documents more maintainable and allows for easier navigation and updates to individual sections.
+
+**Use it when:** A markdown file has grown too large to effectively work with, or you want to break a monolithic document into manageable sections that can be edited independently.
+
+**How it works:**
+1. Confirm source document path and verify it's a markdown file
+2. Determine destination folder (defaults to same location as source, folder named after document)
+3. Execute the sharding command using npx @kayvan/markdown-tree-parser
+4. Verify output files and index.md were created
+5. Handle the original document—delete, move to archive, or keep with warning
+
+**Handling the original:** After sharding, the task prompts you to delete, archive, or keep the original document. Deleting or archiving is recommended to avoid confusion and ensure updates happen in the sharded files only.

package/docs/modules/core/core-workflows.md

@@ -0,0 +1,30 @@
+# Core Workflows
+
+Core Workflows are domain-agnostic workflows that can be utilized by any BMAD-compliant module, workflow, or agent. These workflows are installed by default and available at any time.
+
+## Available Core Workflows
+
+### [Party Mode](party-mode.md)
+
+Orchestrate dynamic multi-agent conversations with your entire BMAD team. Engage with multiple specialized perspectives simultaneously—each agent maintaining their unique personality, expertise, and communication style.
+
+### [Brainstorming](brainstorming.md)
+
+Facilitate structured creative sessions using 60+ proven ideation techniques. The AI acts as coach and guide, using proven creativity methods to draw out ideas and insights that are already within you.
+
+### [Advanced Elicitation](advanced-elicitation.md)
+
+Push the LLM to rethink its work through 50+ reasoning methods—the inverse of brainstorming. The LLM applies sophisticated techniques to re-examine and enhance content it has just generated, essentially "LLM brainstorming" to find better approaches and uncover improvements.
+
+---
+
+## Workflow Integration
+
+Core Workflows are designed to be invoked and configured by other modules. When called from another workflow, they accept contextual parameters to customize the session:
+
+- **Topic focus** — Direct the session toward a specific domain or question
+- **Additional personas** (Party Mode) — Inject expert agents into the roster at runtime
+- **Guardrails** (Brainstorming) — Set constraints and boundaries for ideation
+- **Output goals** — Define what the final output needs to accomplish
+
+This allows modules to leverage these workflows' capabilities while maintaining focus on their specific domain and objectives.

package/docs/modules/core/document-sharding-guide.md

@@ -0,0 +1,133 @@
+# Document Sharding Guide
+
+Comprehensive guide to BMad Method's document sharding system for managing large planning and architecture documents.
+
+## Table of Contents
+
+- [Document Sharding Guide](#document-sharding-guide)
+  - [Table of Contents](#table-of-contents)
+  - [What is Document Sharding?](#what-is-document-sharding)
+    - [Architecture](#architecture)
+  - [When to Use Sharding](#when-to-use-sharding)
+    - [Ideal Candidates](#ideal-candidates)
+  - [How Sharding Works](#how-sharding-works)
+    - [Sharding Process](#sharding-process)
+    - [Workflow Discovery](#workflow-discovery)
+  - [Using the Shard-Doc Tool](#using-the-shard-doc-tool)
+    - [CLI Command](#cli-command)
+    - [Interactive Process](#interactive-process)
+    - [What Gets Created](#what-gets-created)
+  - [Workflow Support](#workflow-support)
+    - [Universal Support](#universal-support)
+
+## What is Document Sharding?
+
+Document sharding splits large markdown files into smaller, organized files based on level 2 headings (`## Heading`). This enables:
+
+- **Selective Loading** - Workflows load only the sections they need
+- **Reduced Token Usage** - Massive efficiency gains for large projects
+- **Better Organization** - Logical section-based file structure
+- **Maintained Context** - Index file preserves document structure
+
+### Architecture
+
+```
+Before Sharding:
+docs/
+└── PRD.md (large 50k token file)
+
+After Sharding:
+docs/
+└── prd/
+    ├── index.md                    # Table of contents with descriptions
+    ├── overview.md                 # Section 1
+    ├── user-requirements.md        # Section 2
+    ├── technical-requirements.md   # Section 3
+    └── ...                         # Additional sections
+```
+
+## When to Use Sharding
+
+### Ideal Candidates
+
+**Large Multi-Epic Projects:**
+
+- Very large complex PRDs
+- Architecture documents with multiple system layers
+- Epic files with 4+ epics (especially for Phase 4)
+- UX design specs covering multiple subsystems
+
+## How Sharding Works
+
+### Sharding Process
+
+1. **Tool Execution**: Run `npx @kayvan/markdown-tree-parser source.md destination/` - this is abstracted with the core shard-doc task which is installed as a slash command or manual task rule depending on your tools.
+2. **Section Extraction**: Tool splits by level 2 headings
+3. **File Creation**: Each section becomes a separate file
+4. **Index Generation**: `index.md` created with structure and descriptions
+
+### Workflow Discovery
+
+BMad workflows use a **dual discovery system**:
+
+1. **Try whole document first** - Look for `document-name.md`
+2. **Check for sharded version** - Look for `document-name/index.md`
+3. **Priority rule** - Whole document takes precedence if both exist - remove the whole document if you want the sharded to be used instead.
+
+## Using the Shard-Doc Tool
+
+### CLI Command
+
+```bash
+/bmad:core:tools:shard-doc 
+```
+
+### Interactive Process
+
+```
+Agent: Which document would you like to shard?
+User: docs/PRD.md
+
+Agent: Default destination: docs/prd/
+       Accept default? [y/n]
+User: y
+
+Agent: Sharding PRD.md...
+       ✓ Created 12 section files
+       ✓ Generated index.md
+       ✓ Complete!
+```
+
+### What Gets Created
+
+**index.md structure:**
+
+```markdown
+# PRD - Index
+
+## Sections
+
+1. [Overview](./overview.md) - Project vision and objectives
+2. [User Requirements](./user-requirements.md) - Feature specifications
+3. [Epic 1: Authentication](./epic-1-authentication.md) - User auth system
+4. [Epic 2: Dashboard](./epic-2-dashboard.md) - Main dashboard UI
+   ...
+```
+
+**Individual section files:**
+
+- Named from heading text (kebab-case)
+- Contains complete section content
+- Preserves all markdown formatting
+- Can be read independently
+
+## Workflow Support
+
+### Universal Support
+
+**All BMM workflows support both formats:**
+
+- ✅ Whole documents
+- ✅ Sharded documents
+- ✅ Automatic detection
+- ✅ Transparent to user

package/docs/modules/core/global-core-config.md

@@ -0,0 +1,11 @@
+# Core Module Global Inheritable Config
+
+The Core Modules module.yaml file defines configuration values that are useful and unique for all other modules to utilize, and by default all other modules installed will clone the values defined in the core module yaml.config into their own. It is possible for other modules to override these values, but the general intent it to accept the core module values and define their own values as needed, or extend the core values.
+
+Currently, the core module.yaml config will define (asking the user upon installation, and recording to the core module config.yaml):
+- `user_name`: string (defaults to the system defined user name)
+- `communication_language`: string (defaults to english)
+- `document_output_language`: string (defaults to english)
+- `output_folder`: string (default `_bmad-output`)
+
+An example of extending one of these values, in the BMad Method module.yaml it defines a planning_artifacts config, which will default to `default: "{output_folder}/planning-artifacts"` thus whatever the output_folder will be, this extended versions default will use the value from this core module and append a new folder onto it. The user can choose to replace this without utilizing the output_folder from the core if they so chose.

package/docs/modules/core/index.md

@@ -0,0 +1,15 @@
+# Core Module
+
+The Core Module is installed with all installations of BMAD modules and provides common functionality that any module, workflow, or agent can take advantage of.
+
+## Core Module Components
+
+- **[Global Core Config](global-core-config.md)** — Inheritable configuration that impacts all modules and custom content
+- **[Core Workflows](core-workflows.md)** — Domain-agnostic workflows usable by any module
+  - [Party Mode](party-mode.md) — Multi-agent conversation orchestration
+  - [Brainstorming](brainstorming.md) — Structured creative sessions with 60+ techniques
+  - [Advanced Elicitation](advanced-elicitation.md) — LLM rethinking with 50+ reasoning methods
+- **[Core Tasks](core-tasks.md)** — Common tasks available across modules
+  - [Index Docs](core-tasks.md#index-docs) — Generate directory index files
+  - [Adversarial Review](core-tasks.md#adversarial-review-general) — Critical content review
+  - [Shard Document](core-tasks.md#shard-document) — Split large documents into sections

package/docs/modules/core/party-mode.md

@@ -0,0 +1,50 @@
+# Party Mode
+
+**Orchestrate dynamic multi-agent conversations with your entire BMAD team.**
+
+Party Mode brings together all your installed BMAD agents for collaborative discussions. Instead of working with a single agent, you can engage with multiple specialized perspectives simultaneously—each agent maintaining their unique personality, expertise, and communication style.
+
+---
+
+## When to Use It
+
+- Exploring complex topics that would benefit from diverse expert perspectives
+- Brainstorming with agents who can build on each other's ideas
+- Getting a comprehensive view across multiple domains (technical, business, creative, strategic)
+- Enjoying dynamic, agent-to-agent conversations where experts challenge and complement each other
+
+---
+
+## How It Works
+
+1. Party Mode loads your complete agent roster and introduces the available team members
+2. You present a topic or question
+3. The facilitator intelligently selects 2-3 most relevant agents based on expertise needed
+4. Agents respond in character, can reference each other, and engage in natural cross-talk
+5. The conversation continues until you choose to exit
+
+---
+
+## Key Features
+
+- **Intelligent agent selection** — The system analyzes your topic and selects the most relevant agents based on their expertise, capabilities, and principles
+- **Authentic personalities** — Each agent maintains their unique voice, communication style, and domain knowledge throughout the conversation
+- **Natural cross-talk** — Agents can reference each other, build on previous points, ask questions, and even respectfully disagree
+- **Optional TTS integration** — Each agent response can be read aloud with voice configurations matching their personalities
+- **Graceful exit** — Sessions conclude with personalized farewells from participating agents
+
+---
+
+## Workflow Integration
+
+Party Mode is a core workflow designed to be invoked and configured by other modules. When called from another workflow, it accepts contextual parameters:
+
+| Parameter | Description |
+|-----------|-------------|
+| **Topic focus** | Prebias the discussion toward a specific domain or question |
+| **Additional personas** | Inject expert agents into the roster at runtime for specialized perspectives |
+| **Participation constraints** | Limit which agents can contribute based on relevance |
+
+### Example
+
+A medical module workflow could invoke Party Mode with expert doctor personas added to the roster, and the conversation pre-focused on a specific diagnosis or treatment decision. The agents would then discuss the medical case with appropriate domain expertise while maintaining their distinct personalities and perspectives.

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.0.0-alpha.20",
+  "version": "6.0.0-alpha.22",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",
@@ -75,7 +75,7 @@
     "fs-extra": "^11.3.0",
     "glob": "^11.0.3",
     "ignore": "^7.0.5",
-    "inquirer": "^8.2.6",
+    "inquirer": "^9.3.8",
     "js-yaml": "^4.1.0",
     "ora": "^5.4.1",
     "semver": "^7.6.3",

package/samples/sample-custom-modules/README.md

@@ -4,7 +4,7 @@ These are quickly put together examples of both a stand alone somewhat cohesive
 
 To try these out, download either or both folders to your local machine, and run the normal bmad installer, and when asked about custom local content, say yes, and give the path to one of these two folders. You can even install both with other regular modules to the same project.
 
-Note - a project is just a folder with \_bmad in the folder - this can be a software project, but it can also be any type of folder on your local computer - such as a markdown notebook, a folder of other files, or just a folder you maintain with useful agents prompts and utilities for any purpose.
+Note - a project is just a folder with `_bmad` in the folder - this can be a software project, but it can also be any type of folder on your local computer - such as a markdown notebook, a folder of other files, or just a folder you maintain with useful agents prompts and utilities for any purpose.
 
 Please remember - these are not optimal or very good examples in their utility or quality control - but they do demonstrate the basics of creating custom content and modules to be able to install for yourself or share with others. This is the groundwork for making very complex modules also such as the full bmad method.
 

package/samples/sample-custom-modules/sample-unitary-module/agents/commit-poet/commit-poet.agent.yaml

@@ -4,7 +4,7 @@ agent:
     name: "Inkwell Von Comitizen"
     title: "Commit Message Artisan"
     icon: "📜"
-    type: simple
+    module: stand-alone
 
   persona:
     role: |

package/samples/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith-sidecar/knowledge/docs.md

@@ -25,10 +25,6 @@
 - @/docs/installers-bundlers/ - Tooling-specific documentation directory
 - @/tools/cli/README.md - CLI usage documentation (comprehensive)
 
-### IDE-Specific Documentation
-
-- @/docs/ide-info/ - IDE-specific setup guides (15+ files)
-
 ### Module Documentation
 
 Each module may have its own docs:
@@ -73,7 +69,6 @@ Follow Keep a Changelog format:
 When code changes, check these docs:
 
 - CLI changes → tools/cli/README.md
-- New IDE support → docs/ide-info/
 - Schema changes → agent-customization-guide.md
 - Bundle changes → web-bundles-gemini-gpt-guide.md
 - Installer changes → installers-bundlers/

package/samples/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith.agent.yaml

@@ -4,7 +4,7 @@ agent:
     name: Vexor
     title: Toolsmith + Guardian of the BMAD Forge
     icon: ⚒️
-    type: expert
+    module: stand-alone
     hasSidecar: true
   persona:
     role: |

package/src/core/agents/bmad-master.agent.yaml

@@ -21,14 +21,10 @@ agent:
     - "ALWAYS communicate in {communication_language}"
 
   menu:
-    - trigger: "list-tasks"
+    - trigger: "LT or fuzzy match on list-tasks"
       action: "list all tasks from {project-root}/_bmad/_config/task-manifest.csv"
-      description: "List Available Tasks"
+      description: "[LT] List Available Tasks"
 
-    - trigger: "list-workflows"
+    - trigger: "LW or fuzzy match on list-workflows"
       action: "list all workflows from {project-root}/_bmad/_config/workflow-manifest.csv"
-      description: "List Workflows"
-
-    - trigger: "party-mode"
-      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "Group chat with all agents"
+      description: "[LW] List Workflows"

package/src/core/tasks/workflow.xml

@@ -74,7 +74,7 @@
           <action>Display generated content</action>
           <ask> [a] Advanced Elicitation, [c] Continue, [p] Party-Mode, [y] YOLO the rest of this document only. WAIT for response. <if
               response="a">
-              <action>Start the advanced elicitation workflow {project-root}/_bmad/core/tasks/advanced-elicitation.xml</action>
+              <action>Start the advanced elicitation workflow {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml</action>
             </if>
             <if
               response="c">

package/src/core/{tasks/advanced-elicitation.xml → workflows/advanced-elicitation/workflow.xml}

@@ -1,5 +1,5 @@
-<task id="_bmad/core/tasks/advanced-elicitation.xml" name="Advanced Elicitation" standalone="true"
-  methods="{project-root}/_bmad/core/tasks/advanced-elicitation-methods.csv"
+<task id="_bmad/core/workflows/advanced-elicitation/workflow.xml" name="Advanced Elicitation" standalone="true"
+  methods="{project-root}/_bmad/core/workflows/advanced-elicitation/methods.csv"
   agent-party="{project-root}/_bmad/_config/agent-manifest.csv">
   <llm critical="true">
     <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
@@ -7,6 +7,7 @@
     <i>HALT immediately when halt-conditions are met</i>
     <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
     <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
+    <i>YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language`</i>
   </llm>
 
   <integration description="When called from workflow">

package/src/core/workflows/brainstorming/steps/step-01-session-setup.md

@@ -7,6 +7,7 @@
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - 💬 FOCUS on session setup and continuation detection only
 - 🚪 DETECT existing workflow state and handle continuation properly
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language`
 
 ## EXECUTION PROTOCOLS:
 

package/src/core/workflows/brainstorming/steps/step-01b-continue.md

@@ -7,6 +7,7 @@
 - 📋 UNDERSTAND PREVIOUS SESSION context and outcomes
 - 🔍 SEAMLESSLY RESUME from where user left off
 - 💬 MAINTAIN CONTINUITY in session flow and rapport
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language`
 
 ## EXECUTION PROTOCOLS:
 

package/src/core/workflows/brainstorming/steps/step-02a-user-selected.md

@@ -7,6 +7,7 @@
 - 📋 PREVIEW TECHNIQUE OPTIONS clearly and concisely
 - 🔍 LET USER EXPLORE and select based on their interests
 - 💬 PROVIDE BACK OPTION to return to approach selection
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language`
 
 ## EXECUTION PROTOCOLS:
 

package/src/core/workflows/brainstorming/steps/step-02b-ai-recommended.md

@@ -7,6 +7,7 @@
 - 📋 LOAD TECHNIQUES ON-DEMAND from brain-methods.csv for recommendations
 - 🔍 MATCH TECHNIQUES to user goals, constraints, and preferences
 - 💬 PROVIDE CLEAR RATIONALE for each recommendation
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language`
 
 ## EXECUTION PROTOCOLS:
 
@@ -141,7 +142,7 @@ Provide deeper insight into each recommended technique:
 
 ### 5. Get User Confirmation
 
-"\*\*This AI-recommended sequence is designed specifically for your [session_topic] goals, considering your [constraints] and focusing on [primary_outcome].
+"This AI-recommended sequence is designed specifically for your [session_topic] goals, considering your [constraints] and focusing on [primary_outcome].
 
 **Does this approach sound perfect for your session?**
 

package/src/core/workflows/brainstorming/steps/step-02c-random-selection.md

@@ -7,6 +7,7 @@
 - 📋 LOAD TECHNIQUES ON-DEMAND from brain-methods.csv
 - 🔍 CREATE EXCITEMENT around unexpected creative methods
 - 💬 EMPHASIZE DISCOVERY over predictable outcomes
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language`
 
 ## EXECUTION PROTOCOLS:
 

package/src/core/workflows/brainstorming/steps/step-02d-progressive-flow.md

@@ -7,6 +7,7 @@
 - 📋 LOAD TECHNIQUES ON-DEMAND from brain-methods.csv for each phase
 - 🔍 MATCH TECHNIQUES to natural creative progression stages
 - 💬 CREATE CLEAR JOURNEY MAP with phase transitions
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language`
 
 ## EXECUTION PROTOCOLS:
 

package/src/core/workflows/brainstorming/steps/step-03-technique-execution.md

@@ -7,6 +7,7 @@
 - 📋 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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language`
 
 ## EXECUTION PROTOCOLS:
 

package/src/core/workflows/brainstorming/steps/step-04-idea-organization.md

@@ -7,6 +7,7 @@
 - 📋 CREATE ACTIONABLE NEXT STEPS from brainstorming outcomes
 - 🔍 FACILITATE CONVERGENT THINKING after divergent exploration
 - 💬 DELIVER COMPREHENSIVE SESSION DOCUMENTATION
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language`
 
 ## EXECUTION PROTOCOLS:
 

package/src/core/workflows/brainstorming/workflow.md

@@ -8,7 +8,7 @@ context_file: '' # Optional context file path for project-specific guidance
 
 **Goal:** Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods
 
-**Your Role:** You are a brainstorming facilitator and creative thinking guide. You bring structured creativity techniques, facilitation expertise, and an understanding of how to guide users through effective ideation processes that generate innovative ideas and breakthrough solutions.
+**Your Role:** You are a brainstorming facilitator and creative thinking guide. You bring structured creativity techniques, facilitation expertise, and an understanding of how to guide users through effective ideation processes that generate innovative ideas and breakthrough solutions. During this entire workflow it is critical that you speak to the user in the config loaded `communication_language`.
 
 ---
 

package/src/core/workflows/party-mode/steps/step-01-agent-loading.md

@@ -7,6 +7,7 @@
 - 📋 LOAD COMPLETE AGENT ROSTER from manifest with merged personalities
 - 🔍 PARSE AGENT DATA for conversation orchestration
 - 💬 INTRODUCE DIVERSE AGENT SAMPLE to kick off discussion
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/core/workflows/party-mode/steps/step-02-discussion-orchestration.md

@@ -7,6 +7,7 @@
 - 📋 MAINTAIN CHARACTER CONSISTENCY using merged agent personalities
 - 🔍 ENABLE NATURAL CROSS-TALK between agents for dynamic conversation
 - 💬 INTEGRATE TTS for each agent response immediately after text
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/core/workflows/party-mode/steps/step-03-graceful-exit.md

@@ -7,6 +7,7 @@
 - 📋 EXPRESS GRATITUDE to user for collaborative participation
 - 🔍 ACKNOWLEDGE SESSION HIGHLIGHTS and key insights gained
 - 💬 MAINTAIN POSITIVE ATMOSPHERE until the very end
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS: