bmad-method 6.0.0-alpha.1 → 6.0.0-alpha.10

package/src/modules/bmb/README.md

@@ -1,132 +1,194 @@
 # BMB - BMad Builder Module
 
-The BMB (BMad Builder Module) provides specialized tools and workflows for creating, customizing, and extending BMad Method components, including custom agents, workflows, and integrations.
+Specialized tools and workflows for creating, customizing, and extending BMad components including agents, workflows, and complete modules.
+
+## Table of Contents
+
+- [Module Structure](#module-structure)
+- [Core Workflows](#core-workflows)
+- [Agent Types](#agent-types)
+- [Quick Start](#quick-start)
+- [Best Practices](#best-practices)
 
 ## Module Structure
 
-### 🤖 `/agents`
+### 🤖 Agents
 
-Builder-specific agents that help create and customize BMad Method components:
+**BMad Builder** - Master builder agent orchestrating all creation workflows with deep knowledge of BMad architecture and conventions.
 
-- Agent creation and configuration specialists
-- Workflow designers
-- Integration builders
+### 📋 Workflows
 
-### 📋 `/workflows`
+Comprehensive suite for building and maintaining BMad components.
 
-Specialized workflows for building and extending BMad Method capabilities:
+## Core Workflows
 
-#### Core Builder Workflows
+### Creation Workflows
 
-- `create-agent` - Design and implement custom agents
-- `create-workflow` - Build new workflow definitions
-- `create-team` - Configure agent teams
-- `bundle-agent` - Package agents for distribution
-- `create-method` - Design custom development methodologies
+**[create-agent](./workflows/create-agent/README.md)** - Build BMad agents
 
-#### Integration Workflows
+- Interactive persona development
+- Command structure design
+- YAML source compilation to .md
 
-- `integrate-tool` - Connect external tools and services
-- `create-adapter` - Build API adapters
-- `setup-environment` - Configure development environments
+**[create-workflow](./workflows/create-workflow/README.md)** - Design workflows
 
-## Key Features
+- Structured multi-step processes
+- Configuration validation
+- Web bundle support
 
-### Agent Builder
+**[create-module](./workflows/create-module/README.md)** - Build complete modules
 
-Create custom agents with:
+- Full module infrastructure
+- Agent and workflow integration
+- Installation automation
 
-- Role-specific instructions
-- Tool configurations
-- Behavior patterns
-- Integration points
+**[module-brief](./workflows/module-brief/README.md)** - Strategic planning
+
+- Module blueprint creation
+- Vision and architecture
+- Comprehensive analysis
+
+### Editing Workflows
+
+**[edit-agent](./workflows/edit-agent/README.md)** - Modify existing agents
+
+- Persona refinement
+- Command updates
+- Best practice compliance
+
+**[edit-workflow](./workflows/edit-workflow/README.md)** - Update workflows
+
+- Structure maintenance
+- Configuration updates
+- Documentation sync
+
+**[edit-module](./workflows/edit-module/README.md)** - Module enhancement
+
+- Component modifications
+- Dependency management
+- Version control
+
+### Maintenance Workflows
+
+**[convert-legacy](./workflows/convert-legacy/README.md)** - Migration tool
 
-### Workflow Designer
+- v4 to v6 conversion
+- Structure compliance
+- Convention updates
 
-Design workflows that:
+**[audit-workflow](./workflows/audit-workflow/README.md)** - Quality validation
 
-- Orchestrate multiple agents
-- Define process flows
-- Handle different project scales
-- Integrate with existing systems
+- Structure verification
+- Config standards check
+- Bloat detection
+- Web bundle completeness
 
-### Team Configuration
+**[redoc](./workflows/redoc/README.md)** - Auto-documentation
 
-Build teams that:
+- Reverse-tree approach
+- Technical writer quality
+- Convention compliance
 
-- Combine complementary agent skills
-- Coordinate on complex tasks
-- Share context effectively
-- Deliver cohesive results
+## Agent Types
+
+BMB creates three agent architectures:
+
+### Full Module Agent
+
+- Complete persona and role definition
+- Command structure with fuzzy matching
+- Workflow integration
+- Module-specific capabilities
+
+### Hybrid Agent
+
+- Shared core capabilities
+- Module-specific extensions
+- Cross-module compatibility
+
+### Standalone Agent
+
+- Independent operation
+- Minimal dependencies
+- Specialized single purpose
 
 ## Quick Start
 
-```bash
-# Create a new custom agent
-bmad bmb create-agent
+1. **Load BMad Builder agent** in your IDE
+2. **Choose creation type:**
+   ```
+   *create-agent     # New agent
+   *create-workflow  # New workflow
+   *create-module    # Complete module
+   ```
+3. **Follow interactive prompts**
 
-# Design a new workflow
-bmad bmb create-workflow
+### Example: Creating an Agent
 
-# Bundle an agent for sharing
-bmad bmb bundle-agent
+```
+User: I need a code review agent
+Builder: *create-agent
 
-# Create a custom team configuration
-bmad bmb create-team
+[Interactive session begins]
+- Brainstorming phase (optional)
+- Persona development
+- Command structure
+- Integration points
 ```
 
 ## Use Cases
 
-### Custom Agent Development
+### Custom Development Teams
 
 Build specialized agents for:
 
-- Domain-specific expertise
-- Company-specific processes
+- Domain expertise (legal, medical, finance)
+- Company processes
 - Tool integrations
 - Automation tasks
 
-### Workflow Customization
+### Workflow Extensions
 
 Create workflows for:
 
-- Unique development processes
 - Compliance requirements
 - Quality gates
 - Deployment pipelines
+- Custom methodologies
 
-### Team Orchestration
+### Complete Solutions
 
-Configure teams for:
+Package modules for:
 
-- Large-scale projects
-- Cross-functional collaboration
-- Specialized domains
-- Custom methodologies
+- Industry verticals
+- Technology stacks
+- Business processes
+- Educational frameworks
 
-## Integration with BMM
+## Best Practices
 
-BMB works alongside BMM to:
+1. **Study existing patterns** - Review BMM/CIS implementations
+2. **Follow conventions** - Use established structures
+3. **Document thoroughly** - Clear instructions essential
+4. **Test iteratively** - Validate during creation
+5. **Consider reusability** - Build modular components
 
-- Extend core BMM capabilities
-- Create custom implementations
-- Build domain-specific solutions
-- Integrate with existing tools
+## Integration
 
-## Best Practices
+BMB components integrate with:
 
-1. **Start with existing patterns** - Study BMM agents and workflows before creating new ones
-2. **Keep it modular** - Build reusable components
-3. **Document thoroughly** - Clear documentation helps others use your creations
-4. **Test extensively** - Validate agents and workflows before production use
-5. **Share and collaborate** - Contribute useful components back to the community
+- **BMad Core** - Framework foundation
+- **BMM** - Extend development capabilities
+- **CIS** - Leverage creative workflows
+- **Custom Modules** - Your domain solutions
 
 ## Related Documentation
 
-- [BMM Module](../bmm/README.md) - Core method implementation
-- [Agent Creation Guide](./workflows/create-agent/README.md) - Detailed agent building instructions
-- [Workflow Design Patterns](./workflows/README.md) - Best practices for workflow creation
+- **[Agent Creation Guide](./workflows/create-agent/README.md)** - Detailed instructions
+- **[Module Structure](./workflows/create-module/module-structure.md)** - Architecture patterns
+- **[BMM Module](../bmm/README.md)** - Reference implementation
+- **[Core Framework](../../core/README.md)** - Foundation concepts
 
 ---
 
-BMB empowers you to extend and customize the BMad Method to fit your specific needs while maintaining the power and consistency of the core framework.
+BMB empowers you to extend BMad Method for your specific needs while maintaining framework consistency and power.

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: 🧙
@@ -18,41 +19,39 @@ agent:
       - Load resources at runtime never pre-load
       - Always present numbered lists for choices
 
-  # Menu items - triggers will be prefixed with * at build time
-  # 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
@@ -125,10 +125,9 @@ _List any cleanup recommendations:_
 
 ## Audit Summary
 
-**Total Checks:** 72
-**Passed:** **\_** / 72
-**Failed:** **\_** / 72
-**Pass Rate:** **\_**%
+**Total Checks:**
+**Passed:** {total}
+**Failed:** {total}
 
 **Recommendation:**
 

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

@@ -1,7 +1,7 @@
 # Audit Workflow - Workflow Quality Audit 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/audit-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/audit-workflow/workflow.yaml</critical>
 
 <workflow>
 
@@ -33,7 +33,7 @@
 
     **Required variables:**
 
-    - `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"`
@@ -161,7 +161,7 @@
     <action if="condition met">Do something</action>
     ```
 
-    <action>Scan instructions.md for nested tag references using pattern: &lt;(action|ask|check|template-output|invoke-workflow|goto|step|elicit-required)&gt; within text content</action>
+    <action>Scan instructions.md for nested tag references using pattern: &lt;(action|ask|check|template-output|invoke-workflow|invoke-task|goto|step)&gt; within text content</action>
     <action>Record any instances of nested tag references with line numbers</action>
     <action>Scan instructions.md for conditional execution antipattern: self-closing check tags</action>
     <action>Detect pattern: `&lt;check&gt;.*&lt;/check&gt;` on single line (self-closing check)</action>
@@ -182,7 +182,7 @@
 
       **Path Validation:**
 
-      - [ ] All paths use bmad/-relative format (NOT {project-root})
+      - [ ] All paths use {bmad_folder}/-relative format (NOT {project-root})
       - [ ] No {config_source} variables in web_bundle section
       - [ ] Paths match actual file locations
 
@@ -200,7 +200,7 @@
       <action>Verify each called workflow.yaml is in web_bundle_files</action>
       <action>**CRITICAL**: Check if existing_workflows field is present when workflows are invoked</action>
       <action>If invoke-workflow calls exist, existing_workflows MUST map workflow variables to paths</action>
-      <action>Example: If instructions use {core_brainstorming}, web_bundle needs: existing_workflows: - core_brainstorming: "bmad/core/workflows/brainstorming/workflow.yaml"</action>
+      <action>Example: If instructions use {core_brainstorming}, web_bundle needs: existing_workflows: - core_brainstorming: "{bmad_folder}/core/workflows/brainstorming/workflow.yaml"</action>
 
       **File Reference Scan:**
       <action>Scan instructions.md for file references in action tags</action>

package/src/modules/bmb/workflows/audit-workflow/workflow.yaml

@@ -4,14 +4,14 @@ description: "Comprehensive workflow quality audit - validates structure, config
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmb/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmb/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 date: system-generated
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmb/workflows/audit-workflow"
+installed_path: "{project-root}/{bmad_folder}/bmb/workflows/audit-workflow"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

package/src/modules/bmb/workflows/convert-legacy/README.md

@@ -84,7 +84,7 @@ convert-legacy/
 - Prompts for target module (bmm, bmb, cis, custom)
 - Determines proper installation paths using v6 conventions
 - Shows target location for user confirmation
-- Ensures all paths use `{project-root}/bmad/` format
+- Ensures all paths use `{project-root}/{bmad_folder}/` format
 
 ### Phase 2: Conversion Strategy (Step 4)
 
@@ -126,7 +126,7 @@ convert-legacy/
 **Template-to-Workflow Conversion (5c)**
 
 - Converts YAML template sections to workflow steps
-- Maps `elicit: true` flags to `<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>` tags
+- Maps `elicit: true` flags to `<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</invoke-task>` tags
 - Transforms conditional sections to flow control
 - Creates proper template.md from content structure
 - Integrates v4 create-doc.md task patterns
@@ -218,7 +218,7 @@ Converted items follow v6 conventions:
 
 **Issue**: Path conversion errors
 
-- **Solution**: Ensure all references use `{project-root}/bmad/` format
+- **Solution**: Ensure all references use `{project-root}/{bmad_folder}/` format
 - **Check**: Review conversion mappings for proper path patterns
 
 **Issue**: Sub-workflow invocation fails
@@ -252,8 +252,8 @@ To customize this workflow:
 
 For issues or questions:
 
-- Review the workflow creation guide at `/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
-- Check conversion mappings at `/bmad/bmb/data/v4-to-v6-mappings.yaml`
+- Review the workflow creation guide at `/{bmad_folder}/bmb/workflows/create-workflow/workflow-creation-guide.md`
+- Check conversion mappings at `/{bmad_folder}/bmb/data/v4-to-v6-mappings.yaml`
 - Validate output using `checklist.md`
 - Consult BMAD v6 documentation for proper conventions
 

package/src/modules/bmb/workflows/convert-legacy/checklist.md

@@ -37,7 +37,7 @@
 - [ ] File paths use {project-root} variables
 - [ ] Config values use {config_source}: pattern
 - [ ] Agent follows naming conventions (kebab-case for files)
-- [ ] ALL paths reference {project-root}/bmad/{{module}}/ locations, NOT src/
+- [ ] ALL paths reference {project-root}/{bmad_folder}/{{module}}/ locations, NOT src/
 - [ ] exec, data, run-workflow commands point to final BMAD installation paths
 
 ### For Template/Workflow Conversions
@@ -48,7 +48,7 @@
 - [ ] All sections converted to workflow steps
 - [ ] Section hierarchy maintained in instructions
 - [ ] Variables ({{var}}) preserved in template.md
-- [ ] Elicitation points (elicit: true) converted to <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+- [ ] Elicitation points (elicit: true) converted to <invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</invoke-task>
 - [ ] Conditional sections preserved with if="" attributes
 - [ ] Repeatable sections converted to repeat="" attributes
 

package/src/modules/bmb/workflows/convert-legacy/instructions.md

@@ -1,7 +1,7 @@
 # Convert Legacy - v4 to v6 Conversion Instructions
 
-<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
-<parameter name="You MUST have already loaded and processed: {project-root}/bmad/bmb/workflows/convert-legacy/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
+<parameter name="You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmb/workflows/convert-legacy/workflow.yaml</critical>
 <critical>Communicate in {communication_language} throughout the conversion process</critical>
 
 <workflow>
@@ -70,8 +70,8 @@ For Modules:
 <action if="custom module"><ask>Enter custom module code (kebab-case):</ask></action>
 <action>Determine installation path based on type and module</action>
 <critical>IMPORTANT: All paths must use final BMAD installation locations, not src paths!</critical>
-<action>Show user the target location: {project-root}/bmad/{{target_module}}/{{item_type}}/{{item_name}}</action>
-<action>Note: Files will be created in bmad/ but all internal paths will reference {project-root}/bmad/ locations</action>
+<action>Show user the target location: {project-root}/{bmad_folder}/{{target_module}}/{{item_type}}/{{item_name}}</action>
+<action>Note: Files will be created in {bmad_folder}/ but all internal paths will reference {project-root}/{bmad_folder}/ locations</action>
 <ask>Proceed with this location? (y/n)</ask>
 </step>
 
@@ -150,16 +150,16 @@ For Modules:
    - Convert task dependencies to workflow references
    - Map template dependencies to v6 workflows
    - Preserve checklist and data file references
-   - CRITICAL: All paths must use {project-root}/bmad/{{module}}/ NOT src/
+   - CRITICAL: All paths must use {project-root}/{bmad_folder}/{{module}}/ NOT src/
 
 <action>Generate the converted v6 agent YAML file (.agent.yaml)</action>
 <action>Example path conversions:
 
-- exec="{project-root}/bmad/{{target_module}}/tasks/task-name.md"
-- run-workflow="{project-root}/bmad/{{target_module}}/workflows/workflow-name/workflow.yaml"
-- data="{project-root}/bmad/{{target_module}}/data/data-file.yaml"
+- exec="{project-root}/{bmad_folder}/{{target_module}}/tasks/task-name.md"
+- run-workflow="{project-root}/{bmad_folder}/{{target_module}}/workflows/workflow-name/workflow.yaml"
+- data="{project-root}/{bmad_folder}/{{target_module}}/data/data-file.yaml"
   </action>
-  <action>Save to: bmad/{{target_module}}/agents/{{agent_name}}.agent.yaml (physical location)</action>
+  <action>Save to: {bmad_folder}/{{target_module}}/agents/{{agent_name}}.agent.yaml (physical location)</action>
   <action>Note: The build process will later compile this to .md with XML format</action>
   <goto step="6">Continue to Validation</goto>
   </step>
@@ -172,7 +172,7 @@ For Modules:
 - Any special behaviors
 
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/create-agent/workflow.yaml
+  workflow: {project-root}/{bmad_folder}/bmb/workflows/create-agent/workflow.yaml
   inputs:
     - agent_name: {{extracted_name}}
     - agent_purpose: {{extracted_purpose}}
@@ -193,7 +193,7 @@ For Modules:
 
 2. Convert template sections to instructions.md:
    - Each YAML section → workflow step
-   - `elicit: true` → `<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>` tag
+   - `elicit: true` → `<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</invoke-task>` tag
    - Conditional sections → `if="condition"` attribute
    - Repeatable sections → `repeat="for-each"` attribute
    - Section instructions → step content
@@ -212,7 +212,7 @@ For Modules:
 
 ```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'
@@ -220,7 +220,7 @@ date: system-generated
 ```
 
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml
+  workflow: {project-root}/{bmad_folder}/bmb/workflows/create-workflow/workflow.yaml
   inputs:
     - workflow_name: {{template_name}}
     - workflow_type: document
@@ -239,7 +239,7 @@ date: system-generated
 <action>Create module blueprint with all components</action>
 
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/create-module/workflow.yaml
+  workflow: {project-root}/{bmad_folder}/bmb/workflows/create-module/workflow.yaml
   inputs:
     - module_name: {{module_name}}
     - components: {{component_list}}
@@ -277,7 +277,7 @@ date: system-generated
    </check>
 
 4. Handle special v4 patterns:
-   - 1-9 elicitation menus → v6 <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+   - 1-9 elicitation menus → v6 <invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</invoke-task>
    - Agent permissions → note in instructions
    - YOLO mode → autonomous flag or optional steps
    - Critical notices → workflow.yaml comments
@@ -286,7 +286,7 @@ date: system-generated
 
 ```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'
@@ -294,7 +294,7 @@ date: system-generated
 ```
 
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml
+  workflow: {project-root}/{bmad_folder}/bmb/workflows/create-workflow/workflow.yaml
   inputs:
     - workflow_name: {{task_name}}
     - workflow_type: {{confirmed_workflow_type}}