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

package/README.md

@@ -35,11 +35,15 @@ The **BMad-CORE** powers the **BMad Method** (probably why you're here!), but yo
     - [C.O.R.E. Philosophy](#core-philosophy)
   - [Modules](#modules)
     - [BMad Method (BMM) - AI-Driven Agile Development](#bmad-method-bmm---ai-driven-agile-development)
+      - [v6 Highlights](#v6-highlights)
+  - [🚀 Quick Start](#-quick-start)
     - [BMad Builder (BMB) - Create Custom Solutions](#bmad-builder-bmb---create-custom-solutions)
     - [Creative Intelligence Suite (CIS) - Innovation \& Creativity](#creative-intelligence-suite-cis---innovation--creativity)
-  - [🚀 Quick Start](#-quick-start)
   - [Installation](#installation)
   - [🎯 Working with Agents \& Commands](#-working-with-agents--commands)
+    - [Method 1: Agent Menu (Recommended for Beginners)](#method-1-agent-menu-recommended-for-beginners)
+    - [Method 2: Direct Slash Commands](#method-2-direct-slash-commands)
+    - [Method 3: Party Mode Execution](#method-3-party-mode-execution)
   - [Key Features](#key-features)
     - [🎨 Update-Safe Customization](#-update-safe-customization)
     - [🚀 Intelligent Installation](#-intelligent-installation)
@@ -47,6 +51,10 @@ The **BMad-CORE** powers the **BMad Method** (probably why you're here!), but yo
     - [📄 Document Sharding (Advanced)](#-document-sharding-advanced)
   - [Documentation](#documentation)
   - [Community \& Support](#community--support)
+  - [Development \& Quality Checks](#development--quality-checks)
+    - [Testing \& Validation](#testing--validation)
+    - [Code Quality](#code-quality)
+    - [Build \& Development](#build--development)
   - [Contributing](#contributing)
   - [License](#license)
 
@@ -352,6 +360,56 @@ Optional optimization for large projects (BMad Method and Enterprise tracks):
 
 ---
 
+## Development & Quality Checks
+
+**For contributors working on the BMAD codebase:**
+
+**Requirements:** Node.js 22+ (see `.nvmrc`). Run `nvm use` to switch to the correct version.
+
+### Testing & Validation
+
+```bash
+# Run all quality checks (comprehensive - use before pushing)
+npm test
+
+# Individual test suites
+npm run test:schemas     # Agent schema validation (fixture-based)
+npm run test:install     # Installation component tests (compilation)
+npm run validate:schemas # YAML schema validation
+npm run validate:bundles # Web bundle integrity
+```
+
+### Code Quality
+
+```bash
+# Lint check
+npm run lint
+
+# Auto-fix linting issues
+npm run lint:fix
+
+# Format check
+npm run format:check
+
+# Auto-format all files
+npm run format:fix
+```
+
+### Build & Development
+
+```bash
+# Bundle for web deployment
+npm run bundle
+
+# Test local installation
+npm run install:bmad
+```
+
+**Pre-commit Hook:** Auto-fixes changed files (lint-staged) + validates everything (npm test)
+**CI:** GitHub Actions runs all quality checks in parallel on every PR
+
+---
+
 ## Contributing
 
 We welcome contributions! See **[CONTRIBUTING.md](CONTRIBUTING.md)** for:

package/docs/installers-bundlers/installers-modules-platforms-reference.md

@@ -311,6 +311,66 @@ bmad status -v      # Detailed status
 - Agent references (cross-module)
 - Template dependencies
 - Partial module installation (only required files)
+- Workflow vendoring for standalone module operation
+
+## Workflow Vendoring
+
+**Problem**: Modules that reference workflows from other modules create dependencies, forcing users to install multiple modules even when they only need one.
+
+**Solution**: Workflow vendoring allows modules to copy workflows from other modules during installation, making them fully standalone.
+
+### How It Works
+
+Agents can specify both `workflow` (source location) and `workflow-install` (destination location) in their menu items:
+
+```yaml
+menu:
+  - trigger: create-story
+    workflow: '{project-root}/bmad/bmm/workflows/4-implementation/create-story/workflow.yaml'
+    workflow-install: '{project-root}/bmad/bmgd/workflows/4-production/create-story/workflow.yaml'
+    description: 'Create a game feature story'
+```
+
+**During Installation:**
+
+1. **Vendoring Phase**: Before copying module files, the installer:
+   - Scans source agent YAML files for `workflow-install` attributes
+   - Copies entire workflow folders from `workflow` path to `workflow-install` path
+   - Updates vendored `workflow.yaml` files to reference target module's config
+
+2. **Compilation Phase**: When compiling agents:
+   - If `workflow-install` exists, uses its value for the `workflow` attribute
+   - `workflow-install` is build-time metadata only, never appears in final XML
+   - Compiled agent references vendored workflow location
+
+3. **Config Update**: Vendored workflows get their `config_source` updated:
+
+   ```yaml
+   # Source workflow (in bmm):
+   config_source: "{project-root}/bmad/bmm/config.yaml"
+
+   # Vendored workflow (in bmgd):
+   config_source: "{project-root}/bmad/bmgd/config.yaml"
+   ```
+
+**Result**: Modules become completely standalone with their own copies of needed workflows, configured for their specific use case.
+
+### Example Use Case: BMGD Module
+
+The BMad Game Development module vendors implementation workflows from BMM:
+
+- Game Dev Scrum Master agent references BMM workflows
+- During installation, workflows are copied to `bmgd/workflows/4-production/`
+- Vendored workflows use BMGD's config (with game-specific settings)
+- BMGD can be installed without BMM dependency
+
+### Benefits
+
+✅ **Module Independence** - No forced dependencies
+✅ **Clean Namespace** - Workflows live in their module
+✅ **Config Isolation** - Each module uses its own configuration
+✅ **Customization Ready** - Vendored workflows can be modified independently
+✅ **No User Confusion** - Avoid partial module installations
 
 ### File Processing
 
@@ -318,6 +378,7 @@ bmad status -v      # Detailed status
 - Excludes `_module-installer/` directories
 - Replaces path placeholders at runtime
 - Injects activation blocks
+- Vendors cross-module workflows (see Workflow Vendoring below)
 
 ### Web Bundling
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.0.0-alpha.6",
+  "version": "6.0.0-alpha.8",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",
@@ -39,8 +39,10 @@
     "release:minor": "gh workflow run \"Manual Release\" -f version_bump=minor",
     "release:patch": "gh workflow run \"Manual Release\" -f version_bump=patch",
     "release:watch": "gh run watch",
-    "test": "node test/test-agent-schema.js",
-    "test:coverage": "c8 --reporter=text --reporter=html node test/test-agent-schema.js",
+    "test": "npm run test:schemas && npm run test:install && npm run validate:bundles && npm run validate:schemas && npm run lint && npm run format:check",
+    "test:coverage": "c8 --reporter=text --reporter=html npm run test:schemas",
+    "test:install": "node test/test-installation-components.js",
+    "test:schemas": "node test/test-agent-schema.js",
     "validate:bundles": "node tools/validate-bundles.js",
     "validate:schemas": "node tools/validate-agent-schema.js"
   },

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">
+<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