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

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">
@@ -62,17 +62,33 @@
           <tag>ask xml tag → Prompt user and WAIT for response</tag>
           <tag>invoke-workflow xml tag → Execute another workflow with given inputs</tag>
           <tag>invoke-task xml tag → Execute specified task</tag>
+          <tag>invoke-protocol name="protocol_name" xml tag → Execute reusable protocol from protocols section</tag>
           <tag>goto step="x" → Jump to specified step</tag>
         </execute-tags>
       </substep>
 
-      <substep n="2c" title="Handle Special Output Tags">
+      <substep n="2c" title="Handle template-output Tags">
         <if tag="template-output">
           <mandate>Generate content for this section</mandate>
           <mandate>Save to file (Write first time, Edit subsequent)</mandate>
           <action>Show checkpoint separator: ━━━━━━━━━━━━━━━━━━━━━━━</action>
           <action>Display generated content</action>
-          <ask>Continue [c] or Edit [e]? WAIT for response</ask>
+          <ask> [a] Advanced Elicitation, [c] Continue, [p] Party-Mode, [y] YOLO the rest of this document only. WAIT for response. <if
+              response="a">
+              <action>Start the advanced elicitation workflow {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</action>
+            </if>
+            <if
+              response="c">
+              <action>Continue to next step</action>
+            </if>
+            <if response="p">
+              <action>Start the party-mode workflow {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml</action>
+            </if>
+            <if
+              response="y">
+              <action>Enter #yolo mode for the rest of the workflow</action>
+            </if>
+          </ask>
         </if>
       </substep>
 
@@ -92,7 +108,8 @@
 
   <execution-modes>
     <mode name="normal">Full user interaction at all decision points</mode>
-    <mode name="#yolo">Skip optional sections, skip all elicitation, minimize prompts</mode>
+    <mode name="#yolo">Skip all confirmations and elicitation, minimize prompts and try to produce all of the workflow automatically by
+      simulating the remaining discussions with an simulated expert user</mode>
   </execution-modes>
 
   <supported-tags desc="Instructions can use these tags">
@@ -111,6 +128,7 @@
       <tag>goto - Jump to another step</tag>
       <tag>invoke-workflow - Call another workflow</tag>
       <tag>invoke-task - Call a task</tag>
+      <tag>invoke-protocol - Execute a reusable protocol (e.g., discover_inputs)</tag>
     </execution>
     <output>
       <tag>template-output - Save content checkpoint</tag>
@@ -130,24 +148,120 @@
     <pattern type="multi-action-block">
       <use-case>Multiple actions/tags under same condition</use-case>
       <syntax>&lt;check if="condition"&gt;
-  &lt;action&gt;First action&lt;/action&gt;
-  &lt;action&gt;Second action&lt;/action&gt;
-&lt;/check&gt;</syntax>
+        &lt;action&gt;First action&lt;/action&gt;
+        &lt;action&gt;Second action&lt;/action&gt;
+        &lt;/check&gt;</syntax>
       <example>&lt;check if="validation fails"&gt;
-  &lt;action&gt;Log error&lt;/action&gt;
-  &lt;goto step="1"&gt;Retry&lt;/goto&gt;
-&lt;/check&gt;</example>
+        &lt;action&gt;Log error&lt;/action&gt;
+        &lt;goto step="1"&gt;Retry&lt;/goto&gt;
+        &lt;/check&gt;</example>
       <rationale>Explicit scope boundaries prevent ambiguity</rationale>
     </pattern>
 
     <pattern type="nested-conditions">
       <use-case>Else/alternative branches</use-case>
       <syntax>&lt;check if="condition A"&gt;...&lt;/check&gt;
-&lt;check if="else"&gt;...&lt;/check&gt;</syntax>
+        &lt;check if="else"&gt;...&lt;/check&gt;</syntax>
       <rationale>Clear branching logic with explicit blocks</rationale>
     </pattern>
   </conditional-execution-patterns>
 
+  <protocols desc="Reusable workflow protocols that can be invoked via invoke-protocol tag">
+    <protocol name="discover_inputs" desc="Smart file discovery and loading based on input_file_patterns">
+      <objective>Intelligently load project files (whole or sharded) based on workflow's input_file_patterns configuration</objective>
+
+      <critical>Only execute if workflow.yaml contains input_file_patterns section</critical>
+
+      <flow>
+        <step n="1" title="Parse Input File Patterns">
+          <action>Read input_file_patterns from loaded workflow.yaml</action>
+          <action>For each pattern group (prd, architecture, epics, etc.), note the load_strategy if present</action>
+        </step>
+
+        <step n="2" title="Load Files Using Smart Strategies">
+          <iterate>For each pattern in input_file_patterns:</iterate>
+
+          <substep n="2a" title="Try Whole Document First">
+            <action>Attempt glob match on 'whole' pattern (e.g., "{output_folder}/*prd*.md")</action>
+            <check if="matches found">
+              <action>Load ALL matching files completely (no offset/limit)</action>
+              <action>Store content in variable: {pattern_name_content} (e.g., {prd_content})</action>
+              <action>Mark pattern as RESOLVED, skip to next pattern</action>
+            </check>
+          </substep>
+
+          <substep n="2b" title="Try Sharded Document if Whole Not Found">
+            <check if="no whole matches AND sharded pattern exists">
+              <action>Determine load_strategy from pattern config (defaults to FULL_LOAD if not specified)</action>
+
+              <strategy name="FULL_LOAD">
+                <desc>Load ALL files in sharded directory - used for PRD, Architecture, UX, brownfield docs</desc>
+                <action>Use glob pattern to find ALL .md files (e.g., "{output_folder}/*architecture*/*.md")</action>
+                <action>Load EVERY matching file completely</action>
+                <action>Concatenate content in logical order (index.md first if exists, then alphabetical)</action>
+                <action>Store in variable: {pattern_name_content}</action>
+              </strategy>
+
+              <strategy name="SELECTIVE_LOAD">
+                <desc>Load specific shard using template variable - example: used for epics with {{epic_num}}</desc>
+                <action>Check for template variables in sharded_single pattern (e.g., {{epic_num}})</action>
+                <action>If variable undefined, ask user for value OR infer from context</action>
+                <action>Resolve template to specific file path</action>
+                <action>Load that specific file</action>
+                <action>Store in variable: {pattern_name_content}</action>
+              </strategy>
+
+              <strategy name="INDEX_GUIDED">
+                <desc>Load index.md, analyze structure and description of each doc in the index, then intelligently load relevant docs</desc>
+                <mandate>DO NOT BE LAZY - use best judgment to load documents that might have relevant information, even if only a 5% chance</mandate>
+                <action>Load index.md from sharded directory</action>
+                <action>Parse table of contents, links, section headers</action>
+                <action>Analyze workflow's purpose and objective</action>
+                <action>Identify which linked/referenced documents are likely relevant</action>
+                <example>If workflow is about authentication and index shows "Auth Overview", "Payment Setup", "Deployment" → Load auth
+                  docs, consider deployment docs, skip payment</example>
+                <action>Load all identified relevant documents</action>
+                <action>Store combined content in variable: {pattern_name_content}</action>
+                <note>When in doubt, LOAD IT - context is valuable, being thorough is better than missing critical info</note>
+              </strategy>
+            </check>
+          </substep>
+
+          <substep n="2c" title="Handle Not Found">
+            <check if="no matches for whole OR sharded">
+              <action>Set {pattern_name_content} to empty string</action>
+              <action>Note in session: "No {pattern_name} files found" (not an error, just unavailable, offer use change to provide)</action>
+            </check>
+          </substep>
+        </step>
+
+        <step n="3" title="Report Discovery Results">
+          <action>List all loaded content variables with file counts</action>
+          <example>
+            ✓ Loaded {prd_content} from 1 file: PRD.md
+            ✓ Loaded {architecture_content} from 5 sharded files: architecture/index.md, architecture/system-design.md, ...
+            ✓ Loaded {epics_content} from selective load: epics/epic-3.md
+            ○ No ux_design files found
+          </example>
+          <note>This gives workflow transparency into what context is available</note>
+        </step>
+      </flow>
+
+      <usage-in-instructions>
+        <example desc="Typical usage in workflow instructions.md">
+          &lt;step n="0" goal="Discover and load project context"&gt;
+          &lt;invoke-protocol name="discover_inputs" /&gt;
+          &lt;/step&gt;
+
+          &lt;step n="1" goal="Analyze requirements"&gt;
+          &lt;action&gt;Review {prd_content} for functional requirements&lt;/action&gt;
+          &lt;action&gt;Cross-reference with {architecture_content} for technical constraints&lt;/action&gt;
+          &lt;/step&gt;
+        </example>
+      </usage-in-instructions>
+    </protocol>
+  </protocols>
+
   <llm final="true">
     <mandate>This is the complete workflow execution engine</mandate>
     <mandate>You MUST Follow instructions exactly as written and maintain conversation context between steps</mandate>

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>
@@ -57,6 +57,50 @@
       <i>- Any tool output or warnings</i>
       <action>Inform user that sharding completed successfully</action>
     </step>
+
+    <step n="6" title="Handle Original Document">
+      <critical>Keeping both the original and sharded versions defeats the purpose of sharding and can cause confusion</critical>
+      <action>Present user with options for the original document:</action>
+
+      <ask>What would you like to do with the original document `[source-document-name]`?
+
+Options:
+[d] Delete - Remove the original (recommended - shards can always be recombined)
+[m] Move to archive - Move original to a backup/archive location
+[k] Keep - Leave original in place (NOT recommended - defeats sharding purpose)
+
+Your choice (d/m/k):</ask>
+
+      <check if="user selects 'd' (delete)">
+        <action>Delete the original source document file</action>
+        <action>Confirm deletion to user: "✓ Original document deleted: [source-document-path]"</action>
+        <note>The document can be reconstructed from shards by concatenating all section files in order</note>
+      </check>
+
+      <check if="user selects 'm' (move)">
+        <action>Determine default archive location: same directory as source, in an "archive" subfolder</action>
+        <action>Example: /path/to/architecture.md → /path/to/archive/architecture.md</action>
+        <ask>Archive location ([y] to use default: [default-archive-path], or provide custom path):</ask>
+        <action if="user accepts default">Use default archive path</action>
+        <action if="user provides custom path">Use custom archive path</action>
+        <action>Create archive directory if it doesn't exist</action>
+        <action>Move original document to archive location</action>
+        <action>Confirm move to user: "✓ Original document moved to: [archive-path]"</action>
+      </check>
+
+      <check if="user selects 'k' (keep)">
+        <action>Display warning to user:</action>
+        <output>⚠️ WARNING: Keeping both original and sharded versions is NOT recommended.
+
+This creates confusion because:
+- The discover_inputs protocol may load the wrong version
+- Updates to one won't reflect in the other
+- You'll have duplicate content taking up space
+
+Consider deleting or archiving the original document.</output>
+        <action>Confirm user choice: "Original document kept at: [source-document-path]"</action>
+      </check>
+    </step>
   </flow>
 
   <halt-conditions critical="true">

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

@@ -20,26 +20,16 @@ The brainstorming workflow facilitates interactive brainstorming sessions using
 
 ## Usage
 
-### Basic Invocation
-
-```bash
-workflow brainstorming
-```
-
-### With Context Document
-
-```bash
-# Provide domain-specific context to guide the session
-workflow brainstorming --data /path/to/context.md
-```
-
 ### Configuration
 
-The workflow leverages configuration from `/bmad/cis/config.yaml`:
+The workflow leverages configuration from `{bmad_folder}/core/config.yaml`:
 
 - **output_folder**: Where session results are saved
 - **user_name**: Session participant identification
-- **brain_techniques**: CSV database of 36 creative techniques
+
+And the following has a default or can be passed in as an override for custom brainstorming scenarios.
+
+- **brain_techniques**: CSV database of 36 creative techniques, default is `./brain-methods.csv`
 
 ## Workflow Structure
 
@@ -185,7 +175,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">
 
@@ -158,6 +158,7 @@ Which approach would you prefer? (Enter 1-4)
 
   </step>
 
+<critical>Create the output document using the template, and record at the {{session_start_plan}} documenting the chosen techniques, along with which approach was used. For all remaining steps, progressively add to the document throughout the brainstorming</critical>
 </step>
 
 <step n="3" goal="Execute Techniques Interactively">
@@ -202,7 +203,7 @@ Example facilitation flow for any technique:
 
 4. Next Prompt: Pull next facilitation_prompt when ready to advance
 
-5. Monitor Energy: After 10-15 minutes, check if they want to continue or switch
+5. Monitor Energy: After a few rounds, check if they want to continue or switch
 
 The CSV provides the prompts - your role is to facilitate naturally in your unique voice.
 </example>
@@ -215,7 +216,7 @@ Continue engaging with the technique until the user indicates they want to:
 - End the session
 
 <energy-checkpoint>
-  After 15-20 minutes with a technique, check: "Should we continue with this technique or try something new?"
+  After 4 rounds with a technique, check: "Should we continue with this technique or try something new?"
 </energy-checkpoint>
 
 <template-output>technique_sessions</template-output>
@@ -254,7 +255,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/advanced-elicitation.xml</invoke-task>
 
 <template-output>key_themes, insights_learnings</template-output>
 

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

@@ -4,6 +4,10 @@
 **Facilitator:** {{agent_role}} {{agent_name}}
 **Participant:** {{user_name}}
 
+## Session Start
+
+{{session_start_plan}}
+
 ## Executive Summary
 
 **Topic:** {{session_topic}}

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
@@ -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"`
@@ -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"