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

package/src/modules/bmb/workflows/create-agent/checklist.md

@@ -11,7 +11,7 @@
 
 ### Core Components
 
-- [ ] `metadata.id` points to final compiled path: `bmad/{{module}}/agents/{{agent}}.md`
+- [ ] `metadata.id` points to final compiled path: `{bmad_folder}/{{module}}/agents/{{agent}}.md`
 - [ ] `metadata.module` matches the module folder (e.g., `bmm`, `bmb`, `cis`)
 - [ ] Principles are an array (preferred) or string with clear values
 
@@ -34,12 +34,12 @@
 
 - [ ] `prompts` defined when using `action: "#id"`
 - [ ] `critical_actions` present if custom activation steps are needed
-- [ ] Customize file (if created) located at `{project-root}/bmad/_cfg/agents/{{module}}-{{agent}}.customize.yaml`
+- [ ] Customize file (if created) located at `{project-root}/{bmad_folder}/_cfg/agents/{{module}}-{{agent}}.customize.yaml`
 
 ## Build Verification
 
 - [ ] Run compile to build `.md`: `npm run install:bmad` → "Compile Agents" (or `bmad install` → Compile)
-- [ ] Confirm compiled file exists at `{project-root}/bmad/{{module}}/agents/{{agent}}.md`
+- [ ] Confirm compiled file exists at `{project-root}/{bmad_folder}/{{module}}/agents/{{agent}}.md`
 
 ## Final Quality
 

package/src/modules/bmb/workflows/create-agent/instructions.md

@@ -1,8 +1,8 @@
 # Build Agent - Interactive Agent Builder Instructions
 
-<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/bmb/workflows/create-agent/workflow.yaml</critical>
-<critical>Study YAML agent examples in: {project-root}/bmad/bmm/agents/ for patterns</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}/bmb/workflows/create-agent/workflow.yaml</critical>
+<critical>Study YAML agent examples in: {project-root}/{bmad_folder}/bmm/agents/ for patterns</critical>
 <critical>Communicate in {communication_language} throughout the agent creation process</critical>
 
 <workflow>
@@ -11,7 +11,7 @@
   <ask>Do you want to brainstorm agent ideas first? [y/n]</ask>
 
   <check if="user answered yes">
-    <action>Invoke brainstorming workflow: {project-root}/bmad/core/workflows/brainstorming/workflow.yaml</action>
+    <action>Invoke brainstorming workflow: {project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml</action>
     <action>Pass context data: {installed_path}/brainstorm-context.md</action>
     <action>Wait for brainstorming session completion</action>
     <action>Use brainstorming output to inform agent identity and persona development in following steps</action>
@@ -51,19 +51,19 @@
   <check if="module agent selected">
     <action>Discover which module system fits best (bmm, bmb, cis, or custom)</action>
     <action>Store as {{target_module}} for path determination</action>
-    <note>Agent will be saved to: bmad/{{target_module}}/agents/</note>
+    <note>Agent will be saved to: {bmad_folder}/{{target_module}}/agents/</note>
   </check>
 
   <check if="standalone agent selected">
     <action>Explain this will be their personal agent, not tied to a module</action>
-    <note>Agent will be saved to: bmad/agents/{{agent-name}}/</note>
+    <note>Agent will be saved to: {bmad_folder}/agents/{{agent-name}}/</note>
     <note>All sidecar files will be in the same folder</note>
   </check>
 
 <critical>Determine agent location:</critical>
 
-- Module Agent → bmad/{{module}}/agents/{{agent-name}}.agent.yaml
-- Standalone Agent → bmad/agents/{{agent-name}}/{{agent-name}}.agent.yaml
+- Module Agent → {bmad_folder}/{{module}}/agents/{{agent-name}}.agent.yaml
+- Standalone Agent → {bmad_folder}/agents/{{agent-name}}/{{agent-name}}.agent.yaml
 
 <note>Keep agent naming/identity details for later - let them emerge naturally through the creation process</note>
 
@@ -186,8 +186,7 @@ Note any interaction preferences for future workflow creation.
 - New workflows needed: Note that they'll be created with intent-based + interactive defaults unless specified
   </action>
 
-<example>
-```yaml
+<example type='yaml'>
 menu:
   # Commands emerge from discussion
   - trigger: [emerging from conversation]
@@ -197,12 +196,10 @@ menu:
 # For cross-module workflow references (advanced):
 
 - trigger: [another capability]
-  workflow: "{project-root}/bmad/SOURCE_MODULE/workflows/path/to/workflow.yaml"
-  workflow-install: "{project-root}/bmad/THIS_MODULE/workflows/vendored/path/workflow.yaml"
+  workflow: "{project-root}/{bmad_folder}/SOURCE_MODULE/workflows/path/to/workflow.yaml"
+  workflow-install: "{project-root}/{bmad_folder}/THIS_MODULE/workflows/vendored/path/workflow.yaml"
   description: [description]
-
-`````
-</example>
+  </example>
 
 <note>**Workflow Vendoring (Advanced):**
 When an agent needs workflows from another module, use both `workflow` (source) and `workflow-install` (destination).
@@ -238,20 +235,20 @@ This is typically used when creating specialized modules that reuse common workf
 <example type="yaml">
   agent:
     metadata:
-      id: bmad/{{target_module}}/agents/{{agent_filename}}.md
+      id: {bmad_folder}/{{target_module}}/agents/{{agent_filename}}.md
       name: {{agent_name}} # The name chosen together
       title: {{agent_title}} # From the role that emerged
       icon: {{agent_icon}} # The perfect emoji
       module: {{target_module}}
 
-persona:
-role: |
-{{The role discovered}}
-identity: |
-{{The background that emerged}}
-communication_style: |
-{{The style they loved}}
-principles: {{The beliefs articulated}}
+    persona:
+      role: |
+      {{The role discovered}}
+      identity: |
+      {{The background that emerged}}
+      communication_style: |
+      {{The style they loved}}
+      principles: {{The beliefs articulated}}
 
 # Features explored
 
@@ -312,7 +309,7 @@ menu: {{The capabilities built}}
 
 **Folder Structure:**
 
-`````
+```text
 
 {{agent_filename}}-sidecar/
 ├── memories.md # Persistent memory
@@ -321,7 +318,7 @@ menu: {{The capabilities built}}
 │ └── README.md
 └── sessions/ # Session notes
 
-````
+```
 
 **File: memories.md**
 
@@ -339,7 +336,7 @@ menu: {{The capabilities built}}
 ## Personal Notes
 
 <!-- My observations and insights -->
-````
+```
 
 **File: instructions.md**
 

package/src/modules/bmb/workflows/create-agent/workflow.yaml

@@ -4,7 +4,7 @@ description: "Interactive workflow to build BMAD Core compliant agents (YAML sou
 author: "BMad"
 
 # Critical variables load from config_source
-config_source: "{project-root}/bmad/bmb/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmb/config.yaml"
 custom_agent_location: "{config_source}:custom_agent_location"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -17,22 +17,22 @@ communication_styles: "{installed_path}/communication-styles.md"
 
 # Optional docs that help understand agent patterns
 recommended_inputs:
-  - example_agents: "{project-root}/bmad/bmm/agents/"
+  - example_agents: "{project-root}/{bmad_folder}/bmm/agents/"
   - agent_activation_rules: "{project-root}/src/utility/models/agent-activation-ide.xml"
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmb/workflows/create-agent"
+installed_path: "{project-root}/{bmad_folder}/bmb/workflows/create-agent"
 template: false # This is an interactive workflow - no template needed
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 
 # Output configuration - YAML agents compiled to .md at install time
-# Module agents: Save to bmad/{{target_module}}/agents/
+# Module agents: Save to {bmad_folder}/{{target_module}}/agents/
 # Standalone agents: Save to custom_agent_location/
-module_output_file: "{project-root}/bmad/{{target_module}}/agents/{{agent_filename}}.agent.yaml"
+module_output_file: "{project-root}/{bmad_folder}/{{target_module}}/agents/{{agent_filename}}.agent.yaml"
 standalone_output_file: "{custom_agent_location}/{{agent_filename}}.agent.yaml"
 # Optional user override file (auto-created by installer if missing)
-config_output_file: "{project-root}/bmad/_cfg/agents/{{target_module}}-{{agent_filename}}.customize.yaml"
+config_output_file: "{project-root}/{bmad_folder}/_cfg/agents/{{target_module}}-{{agent_filename}}.customize.yaml"
 
 standalone: true
 
@@ -41,9 +41,9 @@ web_bundle:
   description: "Interactive workflow to build BMAD Core compliant agents (simple, expert, or module types) with optional brainstorming for agent ideas, proper persona development, activation rules, and command structure"
   author: "BMad"
   web_bundle_files:
-    - "bmad/bmb/workflows/create-agent/instructions.md"
-    - "bmad/bmb/workflows/create-agent/checklist.md"
-    - "bmad/bmb/workflows/create-agent/agent-types.md"
-    - "bmad/bmb/workflows/create-agent/agent-architecture.md"
-    - "bmad/bmb/workflows/create-agent/agent-command-patterns.md"
-    - "bmad/bmb/workflows/create-agent/communication-styles.md"
+    - "{bmad_folder}/bmb/workflows/create-agent/instructions.md"
+    - "{bmad_folder}/bmb/workflows/create-agent/checklist.md"
+    - "{bmad_folder}/bmb/workflows/create-agent/agent-types.md"
+    - "{bmad_folder}/bmb/workflows/create-agent/agent-architecture.md"
+    - "{bmad_folder}/bmb/workflows/create-agent/agent-command-patterns.md"
+    - "{bmad_folder}/bmb/workflows/create-agent/communication-styles.md"

package/src/modules/bmb/workflows/create-module/README.md

@@ -71,7 +71,7 @@ workflow create-module --input module-brief-{name}-{date}.md
 ### Generated Directory
 
 ```
-bmad/{module-code}/
+{bmad_folder}/{module-code}/
 ├── agents/              # Agent definitions
 ├── workflows/           # Workflow processes
 ├── tasks/              # Reusable tasks

package/src/modules/bmb/workflows/create-module/checklist.md

@@ -19,7 +19,7 @@
 
 ## Directory Structure
 
-### Source Directories (bmad/{module-code}/)
+### Source Directories ({bmad_folder}/{module-code}/)
 
 - [ ] `/agents` directory created (even if empty)
 - [ ] `/workflows` directory created (even if empty)
@@ -233,12 +233,3 @@
 - [ ] Alpha (Core functionality works)
 - [ ] Beta (Most features complete, needs testing)
 - [ ] Release (Full functionality, documented)
-
-## Sign-off
-
-**Module Name:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
-**Module Code:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
-**Version:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
-**Validated By:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
-**Date:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
-**Status:** ⬜ Pass / ⬜ Pass with Issues / ⬜ Fail

package/src/modules/bmb/workflows/create-module/installer-templates/install-config.yaml

@@ -80,7 +80,7 @@ prompt:
 
 # EXAMPLE: Static path
 # module_data_path:
-#   result: "{project-root}/bmad/{{MODULE_CODE}}/data"
+#   result: "{project-root}/{bmad_folder}/{{MODULE_CODE}}/data"
 
 # ============================================================================
 # YOUR MODULE CONFIGURATION FIELDS

package/src/modules/bmb/workflows/create-module/instructions.md

@@ -1,8 +1,8 @@
 # Build Module - Interactive Module Builder Instructions
 
-<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/bmb/workflows/create-module/workflow.yaml</critical>
-<critical>Study existing modules in: {project-root}/bmad/ for patterns</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}/bmb/workflows/create-module/workflow.yaml</critical>
+<critical>Study existing modules in: {project-root}/{bmad_folder}/ for patterns</critical>
 <critical>Communicate in {communication_language} throughout the module creation process</critical>
 
 <workflow>
@@ -28,7 +28,7 @@
 <ask>Do you have a module brief or should we create one? [have/create/skip]</ask>
 
 <check if="create">
-  <action>Invoke module-brief workflow: {project-root}/bmad/bmb/workflows/module-brief/workflow.yaml</action>
+  <action>Invoke module-brief workflow: {project-root}/{bmad_folder}/bmb/workflows/module-brief/workflow.yaml</action>
   <action>Wait for module brief completion</action>
   <action>Load the module brief to use as blueprint</action>
 </check>
@@ -64,7 +64,7 @@
 2. **Module code** - Generate kebab-case from name following patterns:
    - Multi-word descriptive names → shortened kebab-case
    - Domain-specific terms → recognizable abbreviations
-   - Present suggested code and confirm it works for paths like bmad/{{code}}/agents/
+   - Present suggested code and confirm it works for paths like {bmad_folder}/{{code}}/agents/
 3. **Module purpose** - Refine their description into 1-2 clear sentences
 4. **Target audience** - Infer from context or ask if unclear
 
@@ -180,7 +180,7 @@
 └── data/                     # User data directory
 ```
 
-**SOURCE MODULE** (\_module-installer is for installation only, not copied to target):
+**SOURCE MODULE** (module-installer is for installation only, not copied to target):
 
 ```
 {{module_code}}/
@@ -268,7 +268,7 @@
 <critical>IMPORTANT: Create install-config.yaml NOT install-config.yaml</critical>
 <critical>This is the STANDARD format that BMAD installer uses</critical>
 
-Create \_module-installer/install-config.yaml:
+Create module-installer/install-config.yaml:
 
 ```yaml
 # {{module_name}} Module Configuration
@@ -322,14 +322,14 @@ prompt:
 
 # EXAMPLE Static path:
 # data_path:
-#   result: "{project-root}/bmad/{{module_code}}/data"
+#   result: "{project-root}/{bmad_folder}/{{module_code}}/data"
 
 {{generated_config_fields_from_step_4}}
 ```
 
 <critical>Save location:</critical>
 
-- Save to {{module_path}}/\_module-installer/install-config.yaml
+- Save to {{module_path}}/module-installer/install-config.yaml
 
 <ask>Does your module need custom installation logic (database setup, API registration, etc.)?</ask>
 
@@ -338,18 +338,13 @@ prompt:
   // {{module_name}} Module Installer
   // Custom installation logic
 
-/\*\*
-
-- Module installation hook
-- Called after files are copied but before IDE configuration
--
 - @param {Object} options - Installation options
 - @param {string} options.projectRoot - Project root directory
 - @param {Object} options.config - Module configuration from install-config.yaml
 - @param {Array} options.installedIDEs - List of IDE codes being configured
 - @param {Object} options.logger - Logger instance (log, warn, error methods)
 - @returns {boolean} - true if successful, false to abort installation
-  \*/
+
   async function install(options) {
   const { projectRoot, config, installedIDEs, logger } = options;
 
@@ -374,7 +369,7 @@ module.exports = { install };
 
 <critical>Save location:</critical>
 
-- Save to {{module_path}}/\_module-installer/installer.js
+- Save to {{module_path}}/module-installer/installer.js
 </check>
 
 <check if="no">
@@ -446,7 +441,7 @@ bmad install {{module_code}}
 
 ## Configuration
 
-The module can be configured in `bmad/{{module_code}}/config.yaml`
+The module can be configured in `{bmad_folder}/{{module_code}}/config.yaml`
 
 Key settings:
 {{configuration_options}}

package/src/modules/bmb/workflows/create-module/module-structure.md

@@ -24,7 +24,7 @@ src/modules/{module-code}/
 └── README.md                      # Module documentation
 
 # INSTALLED MODULE (in target project)
-{project-root}/bmad/{module-code}/
+{project-root}/{bmad_folder}/{module-code}/
 ├── agents/                        # Compiled agent files (.md)
 ├── workflows/                     # Workflow instances
 ├── tasks/                         # Task files
@@ -145,8 +145,8 @@ For modules that need workflows from other modules but want to remain standalone
 ```yaml
 menu:
   - trigger: command-name
-    workflow: '{project-root}/bmad/SOURCE_MODULE/workflows/path/workflow.yaml'
-    workflow-install: '{project-root}/bmad/THIS_MODULE/workflows/vendored/workflow.yaml'
+    workflow: '{project-root}/{bmad_folder}/SOURCE_MODULE/workflows/path/workflow.yaml'
+    workflow-install: '{project-root}/{bmad_folder}/THIS_MODULE/workflows/vendored/workflow.yaml'
     description: 'Command description'
 ```
 
@@ -172,7 +172,7 @@ menu:
 
 ## Installation Infrastructure
 
-### Required: \_module-installer/install-config.yaml
+### Required: module-installer/install-config.yaml
 
 This file defines both installation questions AND static configuration values:
 
@@ -216,7 +216,7 @@ module_version:
   result: '1.0.0'
 
 data_path:
-  result: '{project-root}/bmad/module-code/data'
+  result: '{project-root}/{bmad_folder}/module-code/data'
 ```
 
 **Key Points:**
@@ -226,7 +226,7 @@ data_path:
 - `result` field uses placeholders: `{value}`, `{project-root}`, `{directory_name}`
 - Installer generates final `config.yaml` from this template
 
-### Optional: \_module-installer/installer.js
+### Optional: module-installer/installer.js
 
 For complex installations requiring custom logic:
 
@@ -252,7 +252,7 @@ async function install(options) {
 module.exports = { install };
 ```
 
-### Optional: \_module-installer/assets/
+### Optional: module-installer/assets/
 
 Files to copy during installation:
 

package/src/modules/bmb/workflows/create-module/workflow.yaml

@@ -4,7 +4,7 @@ description: "Interactive workflow to build complete BMAD modules with agents, w
 author: "BMad"
 
 # Critical variables load from config_source
-config_source: "{project-root}/bmad/bmb/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmb/config.yaml"
 custom_module_location: "{config_source}:custom_module_location"
 communication_language: "{config_source}:communication_language"
 user_name: "{config_source}:user_name"
@@ -14,22 +14,22 @@ module_structure_guide: "{installed_path}/module-structure.md"
 installer_templates: "{installed_path}/installer-templates/"
 
 # Use existing build workflows
-agent_builder: "{project-root}/bmad/bmb/workflows/create-agent/workflow.yaml"
-workflow_builder: "{project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml"
-brainstorming_workflow: "{project-root}/bmad/core/workflows/brainstorming/workflow.yaml"
+agent_builder: "{project-root}/{bmad_folder}/bmb/workflows/create-agent/workflow.yaml"
+workflow_builder: "{project-root}/{bmad_folder}/bmb/workflows/create-workflow/workflow.yaml"
+brainstorming_workflow: "{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml"
 brainstorming_context: "{installed_path}/brainstorm-context.md"
 
 # Optional docs that help understand module patterns
 recommended_inputs:
   - module_brief: "{output_folder}/module-brief-*.md"
   - brainstorming_results: "{output_folder}/brainstorming-*.md"
-  - bmm_module: "{project-root}/bmad/bmm/"
-  - cis_module: "{project-root}/bmad/cis/"
-  - existing_agents: "{project-root}/bmad/*/agents/"
-  - existing_workflows: "{project-root}/bmad/*/workflows/"
+  - bmm_module: "{project-root}/{bmad_folder}/bmm/"
+  - cis_module: "{project-root}/{bmad_folder}/cis/"
+  - existing_agents: "{project-root}/{bmad_folder}/*/agents/"
+  - existing_workflows: "{project-root}/{bmad_folder}/*/workflows/"
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmb/workflows/create-module"
+installed_path: "{project-root}/{bmad_folder}/bmb/workflows/create-module"
 template: false # This is an interactive scaffolding workflow
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

package/src/modules/bmb/workflows/create-workflow/README.md

@@ -159,7 +159,7 @@ The brainstorming phase invokes the CIS brainstorming workflow to:
 ### Generated Workflow Folder
 
 Creates a complete workflow folder at:
-`{project-root}/bmad/{{target_module}}/workflows/{{workflow_name}}/`
+`{project-root}/{bmad_folder}/{{target_module}}/workflows/{{workflow_name}}/`
 
 ### Files Created
 
@@ -267,9 +267,9 @@ To modify this workflow:
 
 For issues or questions:
 
-- Review `/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
-- Check existing workflows in `/bmad/bmm/workflows/` for examples
-- Validate against `/bmad/bmb/workflows/create-workflow/checklist.md`
+- Review `/{bmad_folder}/bmb/workflows/create-workflow/workflow-creation-guide.md`
+- Check existing workflows in `/{bmad_folder}/bmm/workflows/` for examples
+- Validate against `/{bmad_folder}/bmb/workflows/create-workflow/checklist.md`
 - Consult BMAD Method v6 documentation
 
 ---

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

@@ -61,7 +61,7 @@
 
 - [ ] web_bundle section present if needed
 - [ ] Name, description, author copied from main config
-- [ ] All file paths converted to bmad/-relative format
+- [ ] All file paths converted to {bmad_folder}/-relative format
 - [ ] NO {config_source} variables in web bundle
 - [ ] NO {project-root} prefixes in paths
 - [ ] Instructions path listed correctly

package/src/modules/bmb/workflows/create-workflow/instructions.md

@@ -1,7 +1,7 @@
 # Build Workflow - Workflow Builder Instructions
 
-<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/bmb/workflows/create-workflow/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}/bmb/workflows/create-workflow/workflow.yaml</critical>
 <critical>You MUST fully understand the workflow creation guide at: {workflow_creation_guide}</critical>
 <critical>Study the guide thoroughly to follow ALL conventions for optimal human-AI collaboration</critical>
 <critical>Communicate in {communication_language} throughout the workflow creation process</critical>
@@ -13,7 +13,7 @@
 
 <action if="user_response == 'y' or user_response == 'yes'">
 Invoke brainstorming workflow to explore ideas and design concepts:
-- Workflow: {project-root}/bmad/core/workflows/brainstorming/workflow.yaml
+- Workflow: {project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml
 - Context data: {installed_path}/brainstorm-context.md
 - Purpose: Generate creative workflow ideas, explore different approaches, and clarify requirements
 
@@ -255,7 +255,7 @@ Include:
 
 ```yaml
 # Critical variables from config
-config_source: '{project-root}/bmad/{{target_module}}/config.yaml'
+config_source: '{project-root}/{bmad_folder}/{{target_module}}/config.yaml'
 output_folder: '{config_source}:output_folder'
 user_name: '{config_source}:user_name'
 communication_language: '{config_source}:communication_language'
@@ -277,13 +277,13 @@ name: 'workflow-name'
 description: 'Clear purpose statement'
 
 # Paths
-installed_path: '{project-root}/bmad/module/workflows/name'
+installed_path: '{project-root}/{bmad_folder}/module/workflows/name'
 template: '{installed_path}/template.md'
 instructions: '{installed_path}/instructions.md'
 validation: '{installed_path}/checklist.md'
 
 # Critical variables from config
-config_source: '{project-root}/bmad/module/config.yaml'
+config_source: '{project-root}/{bmad_folder}/module/config.yaml'
 output_folder: '{config_source}:output_folder'
 user_name: '{config_source}:user_name'
 communication_language: '{config_source}:communication_language'
@@ -314,7 +314,7 @@ Load and use the template at: {template_instructions}
 Generate the instructions.md file following the workflow creation guide:
 
 1. ALWAYS include critical headers:
-   - Workflow engine reference: {project-root}/bmad/core/tasks/workflow.xml
+   - Workflow engine reference: {project-root}/{bmad_folder}/core/tasks/workflow.xml
    - workflow.yaml reference: must be loaded and processed
 
 2. Structure with <workflow> tags containing all steps
@@ -328,7 +328,7 @@ Generate the instructions.md file following the workflow creation guide:
 
 4. Use proper XML tags from guide:
    - Execution: <action>, <check>, <ask>, <goto>, <invoke-workflow>
-   - Output: <template-output>, <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>, <critical>, <example>
+   - Output: <template-output>, <invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</invoke-task>, <critical>, <example>
    - Flow: <loop>, <break>, <continue>
 
 5. Best practices from guide:
@@ -616,15 +616,15 @@ If yes:
 
 - Web bundles are self-contained and cannot use config_source variables
 - All files must be explicitly listed in web_bundle_files
-- File paths use bmad/ root (not {project-root})
+- File paths use {bmad_folder}/ root (not {project-root})
 
 <action>Configure web_bundle section in workflow.yaml:</action>
 
 1. Copy core workflow metadata (name, description, author)
-2. Convert all file paths to bmad/-relative paths:
+2. Convert all file paths to {bmad_folder}/-relative paths:
    - Remove {project-root}/ prefix
    - Remove {config_source} references (use hardcoded values)
-   - Example: "{project-root}/bmad/bmm/workflows/x" → "bmad/bmm/workflows/x"
+   - Example: "{project-root}/{bmad_folder}/bmm/workflows/x" → "{bmad_folder}/bmm/workflows/x"
 
 3. List ALL referenced files by scanning:
 
@@ -642,8 +642,8 @@ If yes:
 
    **Critical: Workflow Dependencies**
    - If instructions call another workflow, that workflow's yaml MUST be in web_bundle_files
-   - Example: `<invoke-workflow>{project-root}/bmad/core/workflows/x/workflow.yaml</invoke-workflow>`
-     → Add "bmad/core/workflows/x/workflow.yaml" to web_bundle_files
+   - Example: `<invoke-workflow>{project-root}/{bmad_folder}/core/workflows/x/workflow.yaml</invoke-workflow>`
+     → Add "{bmad_folder}/core/workflows/x/workflow.yaml" to web_bundle_files
 
 4. Create web_bundle_files array with complete list
 
@@ -654,24 +654,24 @@ web_bundle:
   name: '{workflow_name}'
   description: '{workflow_description}'
   author: '{author}'
-  instructions: 'bmad/{module}/workflows/{workflow}/instructions.md'
-  validation: 'bmad/{module}/workflows/{workflow}/checklist.md'
-  template: 'bmad/{module}/workflows/{workflow}/template.md'
+  instructions: '{bmad_folder}/{module}/workflows/{workflow}/instructions.md'
+  validation: '{bmad_folder}/{module}/workflows/{workflow}/checklist.md'
+  template: '{bmad_folder}/{module}/workflows/{workflow}/template.md'
 
   # Any data files (no config_source)
-  data_file: 'bmad/{module}/workflows/{workflow}/data.csv'
+  data_file: '{bmad_folder}/{module}/workflows/{workflow}/data.csv'
 
   web_bundle_files:
-    - 'bmad/{module}/workflows/{workflow}/instructions.md'
-    - 'bmad/{module}/workflows/{workflow}/checklist.md'
-    - 'bmad/{module}/workflows/{workflow}/template.md'
-    - 'bmad/{module}/workflows/{workflow}/data.csv'
+    - '{bmad_folder}/{module}/workflows/{workflow}/instructions.md'
+    - '{bmad_folder}/{module}/workflows/{workflow}/checklist.md'
+    - '{bmad_folder}/{module}/workflows/{workflow}/template.md'
+    - '{bmad_folder}/{module}/workflows/{workflow}/data.csv'
     # Add every single file referenced anywhere
 
   # CRITICAL: If this workflow invokes other workflows, use existing_workflows
   # This signals the bundler to recursively include those workflows' web_bundles
   existing_workflows:
-    - workflow_variable_name: 'bmad/path/to/workflow.yaml'
+    - workflow_variable_name: '{bmad_folder}/path/to/workflow.yaml'
 ```
 
 **Example with existing_workflows:**
@@ -681,14 +681,14 @@ web_bundle:
   name: 'brainstorm-game'
   description: 'Game brainstorming with CIS workflow'
   author: 'BMad'
-  instructions: 'bmad/bmm/workflows/brainstorm-game/instructions.md'
+  instructions: '{bmad_folder}/bmm/workflows/brainstorm-game/instructions.md'
   template: false
   web_bundle_files:
-    - 'bmad/bmm/workflows/brainstorm-game/instructions.md'
-    - 'bmad/mmm/workflows/brainstorm-game/game-context.md'
-    - 'bmad/core/workflows/brainstorming/workflow.yaml'
+    - '{bmad_folder}/bmm/workflows/brainstorm-game/instructions.md'
+    - '{bmad_folder}/mmm/workflows/brainstorm-game/game-context.md'
+    - '{bmad_folder}/core/workflows/brainstorming/workflow.yaml'
   existing_workflows:
-    - core_brainstorming: 'bmad/core/workflows/brainstorming/workflow.yaml'
+    - core_brainstorming: '{bmad_folder}/core/workflows/brainstorming/workflow.yaml'
 ```
 
 **What existing_workflows does:**
@@ -696,13 +696,13 @@ web_bundle:
 - Tells the bundler this workflow invokes another workflow
 - Bundler recursively includes the invoked workflow's entire web_bundle
 - Essential for meta-workflows that orchestrate other workflows
-- Maps workflow variable names to their bmad/-relative paths
+- Maps workflow variable names to their {bmad_folder}/-relative paths
 
 <action>Validate web bundle completeness:</action>
 
 - Ensure no {config_source} variables remain
 - Verify all file paths are listed
-- Check that paths are bmad/-relative
+- Check that paths are {bmad_folder}/-relative
 - If workflow uses <invoke-workflow>, add to existing_workflows
 
 <template-output>web_bundle_config</template-output>