bmad-method 6.0.0-alpha.7 → 6.0.0-alpha.8

package/.claude/commands/bmad/bmm/workflows/workflow-init.md

@@ -0,0 +1,15 @@
+---
+description: 'Initialize a new BMM project by determining level, type, and creating workflow path'
+---
+
+# workflow-init
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmm/workflows/workflow-status/init/workflow.yaml
+3. Pass the yaml path bmad/bmm/workflows/workflow-status/init/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

package/.claude/commands/bmad/bmm/workflows/workflow-status.md

@@ -0,0 +1,15 @@
+---
+description: 'Lightweight status checker - answers "what should I do now?" for any agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.'
+---
+
+# workflow-status
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmm/workflows/workflow-status/workflow.yaml
+3. Pass the yaml path bmad/bmm/workflows/workflow-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

package/.claude/commands/bmad/core/agents/bmad-master.md

@@ -6,16 +6,16 @@ description: 'BMad Master Executor, Knowledge Custodian, and Workflow Orchestrat
 You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
 
 ```xml
-<agent id="bmad/core/agents/bmad-master.md" name="BMad Master" title="BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator" icon="🧙">
+<agent id=".bmad/core/agents/bmad-master.md" name="BMad Master" title="BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator" icon="🧙">
 <activation critical="MANDATORY">
   <step n="1">Load persona from this current agent file (already in context)</step>
   <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
-      - Load and read {project-root}/bmad/core/config.yaml NOW
+      - Load and read {project-root}/.bmad/core/config.yaml NOW
       - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
       - VERIFY: If config not loaded, STOP and report error to user
       - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
   <step n="3">Remember: user's name is {user_name}</step>
-  <step n="4">Load into memory {project-root}/bmad/core/config.yaml and set variable project_name, output_folder, user_name, communication_language</step>
+  <step n="4">Load into memory {project-root}/.bmad/core/config.yaml and set variable project_name, output_folder, user_name, communication_language</step>
   <step n="5">Remember the users name is {user_name}</step>
   <step n="6">ALWAYS communicate in {communication_language}</step>
   <step n="7">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
@@ -35,7 +35,7 @@ You must fully embody this agent's persona and follow all activation instruction
 
   <handler type="workflow">
     When menu item has: workflow="path/to/workflow.yaml"
-    1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.xml
+    1. CRITICAL: Always LOAD {project-root}/.bmad/core/tasks/workflow.xml
     2. Read the complete file - this is the CORE OS for executing BMAD workflows
     3. Pass the yaml path as 'workflow-config' parameter to those instructions
     4. Execute workflow.xml instructions precisely following all steps
@@ -62,9 +62,9 @@ You must fully embody this agent's persona and follow all activation instruction
   </persona>
   <menu>
     <item cmd="*help">Show numbered menu</item>
-    <item cmd="*list-tasks" action="list all tasks from {project-root}/bmad/_cfg/task-manifest.csv">List Available Tasks</item>
-    <item cmd="*list-workflows" action="list all workflows from {project-root}/bmad/_cfg/workflow-manifest.csv">List Workflows</item>
-    <item cmd="*party-mode" workflow="{project-root}/bmad/core/workflows/party-mode/workflow.yaml">Group chat with all agents</item>
+    <item cmd="*list-tasks" action="list all tasks from {project-root}/.bmad/_cfg/task-manifest.csv">List Available Tasks</item>
+    <item cmd="*list-workflows" action="list all workflows from {project-root}/.bmad/_cfg/workflow-manifest.csv">List Workflows</item>
+    <item cmd="*party-mode" workflow="{project-root}/.bmad/core/workflows/party-mode/workflow.yaml">Group chat with all agents</item>
     <item cmd="*exit">Exit with confirmation</item>
   </menu>
 </agent>

package/.claude/commands/bmad/core/tasks/adv-elicit.md

@@ -0,0 +1,9 @@
+---
+description: 'When called from workflow'
+---
+
+# Advanced Elicitation
+
+LOAD and execute the task at: {project-root}/bmad/core/tasks/adv-elicit.xml
+
+Follow all instructions in the task file exactly as written.

package/.claude/settings.local.json

@@ -1,20 +1,14 @@
 {
   "permissions": {
     "allow": [
-      "Bash(find:*)",
-      "Bash(while read f)",
-      "Bash(do if grep -q \"adv-elicit.xml\" \"$f\")",
-      "Bash(then echo \"$f\")",
-      "Bash(fi)",
-      "Bash(done)",
-      "Bash(git commit:*)",
-      "Bash(git push:*)",
-      "Bash(git tag:*)",
+      "Bash(node tools/cli/bundlers/bundle-web.js:*)",
+      "WebSearch",
+      "Bash(xargs:*)",
+      "Bash(npm view:*)",
       "Bash(git log:*)",
       "Bash(git add:*)",
-      "Bash(gh run:*)",
-      "Bash(gh workflow:*)",
-      "Bash(npm publish)"
+      "Bash(git commit -m \"$(cat <<''EOF''\nRelease v6.0.0-alpha.8\n\n## Installation Path Enhancements\n- **Configurable Installation Directory**: Users can now specify custom installation directories during setup\n- **New Default Location**: Changed default installation to `.bmad` (hidden directory) for cleaner project organization\n- **Ephemeral File Handling**: Updated phase 4 implementation to use ephemeral file locations for better artifact organization\n\n## CLI & Agent Loading Improvements\n- **Optimized Agent Loading**: CLI commands now load from installed agent files, eliminating duplication\n- **Installer UX Improvements**: Enhanced installer interface with version display\n- **VS Code Integration**: Updated settings for new `.bmad` directory structure\n\n## Web Bundle Enhancements\n- **Party Mode Support**: All web bundles (single agent and team) now include party mode for multi-agent collaboration\n- **Advanced Elicitation**: Integrated advanced elicitation capabilities into standalone agents\n- **Expanded Agent Bundles**: New web bundle outputs for all agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer, game-*, creative-squad)\n- **Team Customization**: Added default-party.csv files to bmm, bmgd, and cis modules with customizable party configurations\n\n## Phase 4 Workflow Updates (In Progress)\n- **Artifact Separation**: Initiated separation of phase 4 implementation artifacts from documentation\n- **Dedicated Artifact Path**: Phase 4 items (stories, code review, sprint plan, context files) moving to dedicated location outside docs folder\n- **Updated Workflows**: Modified workflow.yaml files for code-review, sprint-planning, story-context, epic-tech-context, and retrospective workflows\n- **Configuration Support**: Added installer questions for artifact path selection\n\n## IDE Integration\n- **Gemini TOML**: Improved with clear loading instructions using @ commands\n- **Centralized Templates**: Agent launcher markdown files now use centralized critical indication templates\n- **GitHub Copilot**: Updated tool names to match official VS Code documentation (November 2025)\n\n## Bug Fixes\n- Fixed duplicate manifest entries by deduplicating module lists using Set\n- Cleaned up legacy bmad/, bmd/, and web-bundles directories\n- Various improvements to phase 4 workflow artifact handling\n\n## Additional Changes\n- New agent and action command header models for standardization\n- Enhanced web-bundle-activation-steps fragment\n- Updated web-bundler.js to support new structure\n- Improved party mode instructions and workflow orchestration\nEOF\n)\")",
+      "Bash(npm publish:*)"
     ],
     "deny": [],
     "ask": []

package/.vscode/settings.json

@@ -56,7 +56,8 @@
     "tileset",
     "tmpl",
     "Trae",
-    "VNET"
+    "VNET",
+    "webskip"
   ],
   "json.schemas": [
     {

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.0.0-alpha.7",
+  "version": "6.0.0-alpha.8",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",

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

@@ -1,28 +1,34 @@
 # BMAD™ Core Configuration
+header: "BMAD™ Core Configuration"
+subheader: "Configure the core settings for your BMAD™ installation.\nThese settings will be used across all modules and agents."
 
-prompt:
-  - "Welcome and thank you for choosing BMAD™! This is the Core Configuration."
-  - "This will impact all selected modules, either additions or upgrades."
+bmad_folder:
+  prompt: "What is the root folder for BMAD installation? (Recommended: .bmad)"
+  default: ".bmad"
+  result: "{value}"
+  regex: "^[a-zA-Z0-9._-]{1,20}$"
 
-# This is injected into the custom agent activation rules
 user_name:
-  prompt: "What is your name?"
+  prompt: "What shall the agents call you?"
   default: "BMad"
   result: "{value}"
 
-# This is injected into the custom agent activation rules and most workflows
 communication_language:
-  prompt: "Preferred Chat Language?"
+  prompt: "Preferred Chat Language/Style? (English, Mandarin, English Pirate, etc...)"
   default: "English"
   result: "{value}"
 
 document_output_language:
   prompt: "Preferred Document Output Language?"
-  default: "English"
+  default: "{communication_language}"
   result: "{value}"
 
-# This is injected into the custom agent activation rules
 output_folder:
   prompt: "Where should the generated output default save location be?"
   default: "docs"
   result: "{project-root}/{value}"
+
+install_user_docs:
+  prompt: "Install user documentation and optimized agent intelligence to each selected modules docs folder?"
+  default: true
+  result: "{value}"

package/src/core/_module-installer/installer.js

@@ -49,14 +49,6 @@ async function configureForIDE(ide) {
       // Claude Code specific Core configurations
       break;
     }
-    case 'cursor': {
-      // Cursor specific Core configurations
-      break;
-    }
-    case 'windsurf': {
-      // Windsurf specific Core configurations
-      break;
-    }
     // Add more IDEs as needed
     default: {
       // No specific configuration needed

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

@@ -3,7 +3,7 @@
 
 agent:
   metadata:
-    id: "bmad/core/agents/bmad-master.md"
+    id: "{bmad_folder}/core/agents/bmad-master.md"
     name: "BMad Master"
     title: "BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator"
     icon: "🧙"
@@ -17,22 +17,22 @@ agent:
 
   # Agent-specific critical actions
   critical_actions:
-    - "Load into memory {project-root}/bmad/core/config.yaml and set variable project_name, output_folder, user_name, communication_language"
+    - "Load into memory {project-root}/{bmad_folder}/core/config.yaml and set variable project_name, output_folder, user_name, communication_language"
     - "Remember the users name is {user_name}"
     - "ALWAYS communicate in {communication_language}"
 
   # Agent menu items
   menu:
     - trigger: "list-tasks"
-      action: "list all tasks from {project-root}/bmad/_cfg/task-manifest.csv"
+      action: "list all tasks from {project-root}/{bmad_folder}/_cfg/task-manifest.csv"
       description: "List Available Tasks"
 
     - trigger: "list-workflows"
-      action: "list all workflows from {project-root}/bmad/_cfg/workflow-manifest.csv"
+      action: "list all workflows from {project-root}/{bmad_folder}/_cfg/workflow-manifest.csv"
       description: "List Workflows"
 
     - trigger: "party-mode"
-      workflow: "{project-root}/bmad/core/workflows/party-mode/workflow.yaml"
+      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
       description: "Group chat with all agents"
 
   # Empty prompts section (no custom prompts for this agent)

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

@@ -1,7 +1,8 @@
-<agent id="bmad/core/agents/bmad-orchestrator.md" name="BMad Orchestrator" title="BMad Web Orchestrator" icon="🎭" localskip="true">
+<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/..." 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>
@@ -15,7 +16,7 @@
         <handler type="workflow">
           When menu item has: workflow="workflow-id"
           1. Find workflow node by id in this bundle (e.g., &lt;workflow id="workflow-id"&gt;)
-          2. CRITICAL: Always LOAD bmad/core/tasks/workflow.xml if referenced
+          2. CRITICAL: Always LOAD {bmad_folder}/core/tasks/workflow.xml if referenced
           3. Execute the workflow content precisely following all steps
           4. Save outputs after completing EACH workflow step (never batch)
           5. If workflow id is "todo", inform user it hasn't been implemented yet
@@ -48,7 +49,7 @@
 
         <handler type="validate-workflow">
           When menu item has: validate-workflow="workflow-id"
-          1. MUST LOAD bmad/core/tasks/validate-workflow.xml
+          1. MUST LOAD {bmad_folder}/core/tasks/validate-workflow.xml
           2. Execute all validation instructions from that file
           3. Check workflow's validation property for schema
           4. Identify file to validate or ask user to specify
@@ -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>

package/src/core/tasks/adv-elicit.xml

@@ -1,4 +1,6 @@
-<task id="bmad/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>

package/src/core/tasks/index-docs.xml

@@ -1,4 +1,4 @@
-<task id="bmad/core/tasks/index-docs" name="Index Docs"
+<task id="{bmad_folder}/core/tasks/index-docs" name="Index Docs"
   description="Generates or updates an index.md of all documents in the specified directory" webskip="true" standalone="true">
   <llm critical="true">
     <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>

package/src/core/tasks/validate-workflow.xml

@@ -1,4 +1,4 @@
-<task id="bmad/core/tasks/validate-workflow.xml" name="Validate Workflow Output">
+<task id="{bmad_folder}/core/tasks/validate-workflow.xml" name="Validate Workflow Output">
   <objective>Run a checklist against a document with thorough analysis and produce a validation report</objective>
 
   <inputs>

package/src/core/tasks/workflow.xml

@@ -1,4 +1,4 @@
-<task id="bmad/core/tasks/workflow.xml" name="Execute Workflow">
+<task id="{bmad_folder}/core/tasks/workflow.xml" name="Execute Workflow">
   <objective>Execute given workflow by loading its configuration, following instructions, and producing output</objective>
 
   <llm critical="true">

package/src/core/tools/shard-doc.xml

@@ -1,4 +1,4 @@
-<tool id="bmad/core/tasks/shard-doc" name="Shard Document"
+<tool id="{bmad_folder}/core/tasks/shard-doc" name="Shard Document"
   description="Splits large markdown documents into smaller, organized files based on level 2 (default) sections" webskip="true"
   standalone="true">
   <objective>Split large markdown documents into smaller, organized files based on level 2 sections using @kayvan/markdown-tree-parser tool</objective>

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

@@ -35,7 +35,7 @@ workflow brainstorming --data /path/to/context.md
 
 ### Configuration
 
-The workflow leverages configuration from `/bmad/cis/config.yaml`:
+The workflow leverages configuration from `{bmad_folder}/cis/config.yaml`:
 
 - **output_folder**: Where session results are saved
 - **user_name**: Session participant identification
@@ -185,7 +185,7 @@ The workflow includes 36 techniques organized into 7 categories:
 ## Requirements
 
 - No special software requirements
-- Access to the CIS module configuration (`/bmad/cis/config.yaml`)
+- Access to the CIS module configuration (`{bmad_folder}/cis/config.yaml`)
 - Active participation and engagement throughout the interactive session
 - Optional: Domain context document for focused brainstorming
 

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

@@ -3,8 +3,8 @@
 ## Workflow
 
 <workflow>
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project_root}/bmad/core/workflows/brainstorming/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project_root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml</critical>
 
 <step n="1" goal="Session Setup">
 
@@ -254,7 +254,7 @@ Analyze the session to identify deeper patterns:
 2. **Surface key insights** - What realizations emerged during the process? -> insights_learnings
 3. **Note surprising connections** - What unexpected relationships were discovered? -> insights_learnings
 
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
 
 <template-output>key_themes, insights_learnings</template-output>
 

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

@@ -4,7 +4,7 @@ description: "Facilitate interactive brainstorming sessions using diverse creati
 author: "BMad"
 
 # Critical variables load from config_source
-config_source: "{project-root}/bmad/cis/config.yaml"
+config_source: "{project-root}/{bmad_folder}/cis/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 date: system-generated
@@ -18,7 +18,7 @@ recommended_inputs:
 # Example: data="{path}/context.md" provides domain-specific guidance
 
 # Module path and component files
-installed_path: "{project-root}/bmad/core/workflows/brainstorming"
+installed_path: "{project-root}/{bmad_folder}/core/workflows/brainstorming"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
@@ -33,11 +33,11 @@ web_bundle:
   name: "brainstorming"
   description: "Facilitate interactive brainstorming sessions using diverse creative techniques. This workflow facilitates interactive brainstorming sessions using diverse creative techniques. The session is highly interactive, with the AI acting as a facilitator to guide the user through various ideation methods to generate and refine creative solutions."
   author: "BMad"
-  template: "bmad/core/workflows/brainstorming/template.md"
-  instructions: "bmad/core/workflows/brainstorming/instructions.md"
-  brain_techniques: "bmad/core/workflows/brainstorming/brain-methods.csv"
+  template: "{bmad_folder}/core/workflows/brainstorming/template.md"
+  instructions: "{bmad_folder}/core/workflows/brainstorming/instructions.md"
+  brain_techniques: "{bmad_folder}/core/workflows/brainstorming/brain-methods.csv"
   use_advanced_elicitation: true
   web_bundle_files:
-    - "bmad/core/workflows/brainstorming/instructions.md"
-    - "bmad/core/workflows/brainstorming/brain-methods.csv"
-    - "bmad/core/workflows/brainstorming/template.md"
+    - "{bmad_folder}/core/workflows/brainstorming/instructions.md"
+    - "{bmad_folder}/core/workflows/brainstorming/brain-methods.csv"
+    - "{bmad_folder}/core/workflows/brainstorming/template.md"

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

@@ -1,12 +1,12 @@
 # Party Mode - Multi-Agent Discussion Instructions
 
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
+<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
 <critical>This workflow orchestrates group discussions between all installed BMAD agents</critical>
 
 <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>

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

@@ -4,20 +4,24 @@ description: "Orchestrates group discussions between all installed BMAD agents,
 author: "BMad"
 
 # Critical data sources - manifest and config overrides
-agent_manifest: "{project-root}/bmad/_cfg/agent-manifest.csv"
-agent_overrides: "{project-root}/bmad/_cfg/agents/*.customize.yaml"
+agent_manifest: "{project-root}/{bmad_folder}/_cfg/agent-manifest.csv"
 date: system-generated
 
 # This is an interactive action workflow - no template output
 template: false
-instructions: "{project-root}/bmad/core/workflows/party-mode/instructions.md"
+instructions: "{project-root}/{bmad_folder}/core/workflows/party-mode/instructions.md"
 
 # 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"

package/src/modules/bmb/_module-installer/install-config.yaml

@@ -4,23 +4,28 @@ code: bmb
 name: "BMB: BMad Builder - Agent, Workflow and Module Builder"
 default_selected: false # This module will not be selected by default for new installations
 
-prompt: "Happy Building - Build the Modules, Workflows and Agents of your dreams."
+header: "BMad Optimized Builder (BoMB) Module Configuration"
+subheader: "Configure the settings for the BoMB Factory!\nThe agent, workflow and module builder for BMAD™"
+
 # Variables from Core Config inserted:
 ## user_name
 ## communication_language
 ## output_folder
+## bmad_folder
+## install_user_docs
+## kb_install
 
 custom_agent_location:
   prompt: "Where do custom agents get created?"
-  default: "bmad/agents"
+  default: "{bmad_folder}/custom/agents"
   result: "{project-root}/{value}"
 
 custom_workflow_location:
   prompt: "Where do custom workflows get stored?"
-  default: "bmad/workflows"
+  default: "{bmad_folder}/custom/workflows"
   result: "{project-root}/{value}"
 
 custom_module_location:
   prompt: "Where do custom modules get stored?"
-  default: "bmad"
+  default: "{bmad_folder}/custom/modules"
   result: "{project-root}/{value}"

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

@@ -2,8 +2,9 @@
 # Master BMad Module Agent Team and Workflow Builder and Maintainer
 
 agent:
+  webskip: true
   metadata:
-    id: bmad/bmb/agents/bmad-builder.md
+    id: "{bmad_folder}/bmb/agents/bmad-builder.md"
     name: BMad Builder
     title: BMad Builder
     icon: 🧙
@@ -22,37 +23,37 @@ agent:
   # help and exit are auto-injected, don't define them here
   menu:
     - trigger: audit-workflow
-      workflow: "{project-root}/bmad/bmb/workflows/audit-workflow/workflow.yaml"
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/audit-workflow/workflow.yaml"
       description: Audit existing workflows for BMAD Core compliance and best practices
 
     - trigger: convert
-      workflow: "{project-root}/bmad/bmb/workflows/convert-legacy/workflow.yaml"
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/convert-legacy/workflow.yaml"
       description: Convert v4 or any other style task agent or template to a workflow
 
     - trigger: create-agent
-      workflow: "{project-root}/bmad/bmb/workflows/create-agent/workflow.yaml"
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/create-agent/workflow.yaml"
       description: Create a new BMAD Core compliant agent
 
     - trigger: create-module
-      workflow: "{project-root}/bmad/bmb/workflows/create-module/workflow.yaml"
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/create-module/workflow.yaml"
       description: Create a complete BMAD compatible module (custom agents and workflows)
 
     - trigger: create-workflow
-      workflow: "{project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml"
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/create-workflow/workflow.yaml"
       description: Create a new BMAD Core workflow with proper structure
 
     - trigger: edit-agent
-      workflow: "{project-root}/bmad/bmb/workflows/edit-agent/workflow.yaml"
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/edit-agent/workflow.yaml"
       description: Edit existing agents while following best practices
 
     - trigger: edit-module
-      workflow: "{project-root}/bmad/bmb/workflows/edit-module/workflow.yaml"
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/edit-module/workflow.yaml"
       description: Edit existing modules (structure, agents, workflows, documentation)
 
     - trigger: edit-workflow
-      workflow: "{project-root}/bmad/bmb/workflows/edit-workflow/workflow.yaml"
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/edit-workflow/workflow.yaml"
       description: Edit existing workflows while following best practices
 
     - trigger: redoc
-      workflow: "{project-root}/bmad/bmb/workflows/redoc/workflow.yaml"
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/redoc/workflow.yaml"
       description: Create or update module documentation

package/src/modules/bmb/workflows/audit-workflow/checklist.md

@@ -45,7 +45,7 @@
 ## Web Bundle Validation (if applicable)
 
 - [ ] web_bundle section present if workflow needs deployment
-- [ ] All paths in web_bundle use bmad/-relative format (NOT {project-root})
+- [ ] All paths in web_bundle use {bmad_folder}/-relative format (NOT {project-root})
 - [ ] No {config_source} variables in web_bundle section
 - [ ] instructions file listed in web_bundle_files array
 - [ ] template file listed in web_bundle_files (if document workflow)
@@ -53,7 +53,7 @@
 - [ ] All data files (CSV, JSON, YAML) listed in web_bundle_files
 - [ ] All <invoke-workflow> called workflows have their .yaml files in web_bundle_files
 - [ ] **CRITICAL**: If workflow invokes other workflows, existing_workflows field is present
-- [ ] existing_workflows maps workflow variables to bmad/-relative paths correctly
+- [ ] existing_workflows maps workflow variables to {bmad_folder}/-relative paths correctly
 - [ ] All files referenced in instructions <action> tags listed in web_bundle_files
 - [ ] No files listed in web_bundle_files that don't exist
 - [ ] Web bundle metadata (name, description, author) matches top-level metadata