Major Enhancements:

- Installation path is now fully configurable, allowing users to specify custom installation directories during setup
  - Default installation location changed to .bmad (hidden directory) for cleaner project root organization

    Web Bundle Improvements:

    - All web bundles (single agent and team) now include party mode support for multi-agent collaboration!
    - Advanced elicitation capabilities integrated into standalone agents
    - All bundles enhanced with party mode agent manifests
    - Added default-party.csv files to bmm, bmgd, and cis module teams
    - The default party file is what will be used with single agent bundles. teams can customize for different party configurations before web bundling through a setting in the team yaml file
    - New web bundle outputs for all agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer, game-*, creative-squad)

    Phase 4 Workflow Updates (In Progress):

    - Initiated shift to separate phase 4 implementation artifacts from documentation
        - Phase 4 implementation artifacts (stories, code review, sprint plan, context files) will move to dedicated location outside docs folder
        - Installer questions and configuration added for artifact path selection
        - Updated workflow.yaml files for code-review, sprint-planning, story-context, epic-tech-context, and retrospective workflows to support this, but still might require some udpates

    Additional Changes:

    - New agent and action command header models for standardization
    - Enhanced web-bundle-activation-steps fragment
    - Updated web-bundler.js to support new structure
    - VS Code settings updated for new .bmad directory
    - Party mode instructions and workflow enhanced for better orchestration

   IDE Installer Updates:

    - Show version number of installer in cli
    - improved Installer UX
    - Gemini TOML Improved to have clear loading instructions with @ commands
    - All tools agent launcher mds improved to use a central file template critical indication isntead of hardcoding in 2 different locations.

src/core/_module-installer/install-config.yaml

@@ -1,8 +1,6 @@
 # BMAD™ Core Configuration
-
-prompt:
-  - "Welcome and thank you for choosing BMAD™! This is the Core Configuration."
-  - "This will impact all selected modules, either additions or upgrades."
+header: "BMAD™ Core Configuration"
+subheader: "Configure the core settings for your BMAD™ installation.\nThese settings will be used across all modules and agents."
 
 bmad_folder:
   prompt: "What is the root folder for BMAD installation? (Recommended: .bmad)"

src/core/agents/bmad-web-orchestrator.agent.xml

@@ -1,7 +1,8 @@
 <agent id="{bmad_folder}/core/agents/bmad-orchestrator.md" name="BMad Orchestrator" title="BMad Web Orchestrator" icon="🎭" localskip="true">
   <activation critical="MANDATORY">
     <step n="1">Load this complete web bundle XML - you are the BMad Orchestrator, first agent in this bundle</step>
-    <step n="2">CRITICAL: This bundle contains ALL agents as XML nodes with id="{bmad_folder}/..." and ALL workflows/tasks as nodes findable by type
+    <step n="2">CRITICAL: This bundle contains ALL agents as XML nodes with id="{bmad_folder}/..." and ALL workflows/tasks as nodes findable
+      by type
       and id</step>
     <step n="3">Greet user as BMad Orchestrator and display numbered list of ALL menu items from menu section below</step>
     <step n="4">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
@@ -69,18 +70,6 @@
         5. On *exit: Confirm, then return to BMad Orchestrator persona
       </agent-transformation>
 
-      <party-mode critical="true">
-        When user selects *party-mode:
-        1. Enter group chat simulation mode
-        2. Load ALL agent personas from this bundle
-        3. Simulate each agent distinctly with their name and emoji
-        4. Create engaging multi-agent conversation
-        5. Each agent contributes based on their expertise
-        6. Format: "[emoji] Name: message"
-        7. Maintain distinct voices and perspectives for each agent
-        8. Continue until user types *exit-party
-      </party-mode>
-
       <list-agents critical="true">
         When user selects *list-agents:
         1. Scan all agent nodes in this bundle
@@ -116,7 +105,9 @@
     <item cmd="*help">Show numbered command list</item>
     <item cmd="*list-agents">List all available agents with their capabilities</item>
     <item cmd="*agents [agent-name]">Transform into a specific agent</item>
-    <item cmd="*party-mode">Enter group chat with all agents simultaneously</item>
+    <item cmd="*party-mode" workflow="bmad/bmm/workflows/1-analysis/product-brief/workflow.yaml">Enter group chat with all agents
+      simultaneously</item>
+    <item cmd="*adv-elicit" task="bmad/core/tasks/adv-elict.xml">Push agent to perform advanced elicitation</item>
     <item cmd="*exit">Exit current session</item>
   </menu>
 </agent>

src/core/tasks/adv-elicit.xml

@@ -1,4 +1,6 @@
-<task id="{bmad_folder}/core/tasks/adv-elicit.xml" name="Advanced Elicitation" standalone="true">
+<task id="{bmad_folder}/core/tasks/adv-elicit.xml" name="Advanced Elicitation" standalone="true"
+  methods="{project-root}/{bmad_folder}/core/tasks/adv-elicit-methods.csv"
+  agent-party="{project-root}/{bmad_folder}/_cfg/agent-manifest.csv">
   <llm critical="true">
     <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
     <i>DO NOT skip steps or change the sequence</i>
@@ -9,7 +11,7 @@
 
   <integration description="When called from workflow">
     <desc>When called during template workflow processing:</desc>
-    <i>1. Receive the current section content that was just generated</i>
+    <i>1. Receive or review the current section content that was just generated or</i>
     <i>2. Apply elicitation methods iteratively to enhance that specific content</i>
     <i>3. Return the enhanced version back when user selects 'x' to proceed and return back</i>
     <i>4. The enhanced content replaces the original section content in the output document</i>
@@ -17,7 +19,7 @@
 
   <flow>
     <step n="1" title="Method Registry Loading">
-      <action>Load and read {project-root}/core/tasks/adv-elicit-methods.csv</action>
+      <action>Load and read {{methods}} and {{agent-party}}</action>
 
       <csv-structure>
         <i>category: Method grouping (core, structural, risk, etc.)</i>

src/core/workflows/party-mode/instructions.md

@@ -6,7 +6,7 @@
 <workflow>
 
 <step n="1" goal="Load Agent Manifest and Configurations">
-  <action>Load the agent manifest CSV from {{manifest}}</action>
+  <action>Load the agent manifest CSV from {{agent_manifest}}</action>
   <action>Parse CSV to extract all agent entries with their condensed information:</action>
     - name (agent identifier)
     - displayName (agent's persona name)
@@ -19,11 +19,6 @@
     - module (source module)
     - path (file location)
 
-<action>For each agent found in manifest:</action>
-<check>Look for config override at {{agent_overrides}}[module]-[agent-name].customize.yaml</check>
-<action if="agent override exists">Load the override configuration</action>
-<action>MERGE override data with manifest data (overrides take precedence):</action> - Override role replaces manifest role if present - Override identity replaces manifest identity if present - Override communicationStyle replaces manifest communicationStyle if present - Override principles replace manifest principles if present - Any additional persona elements from override are added
-
 <action>Build complete agent roster with merged personalities</action>
 <action>Store agent data for use in conversation orchestration</action>
 </step>

src/core/workflows/party-mode/workflow.yaml

@@ -5,7 +5,6 @@ author: "BMad"
 
 # Critical data sources - manifest and config overrides
 agent_manifest: "{project-root}/{bmad_folder}/_cfg/agent-manifest.csv"
-agent_overrides: "{project-root}/{bmad_folder}/_cfg/agents/*.customize.yaml"
 date: system-generated
 
 # This is an interactive action workflow - no template output
@@ -15,9 +14,14 @@ instructions: "{project-root}/{bmad_folder}/core/workflows/party-mode/instructio
 # Exit conditions
 exit_triggers:
   - "*exit"
-  - "end party mode"
-  - "stop party mode"
 
 standalone: true
 
-web_bundle: false
+web_bundle:
+  name: "party-mode"
+  description: "Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations"
+  author: "BMad"
+  instructions: "bmad/core/workflows/party-mode/instructions.md"
+  agent_manifest: "bmad/_cfg/agent-manifest.csv"
+  web_bundle_files:
+    - "{bmad_folder}/core/workflows/party-mode/workflow.xml"