bmad-method 6.0.0-alpha.19 → 6.0.0-alpha.20

package/{docs → samples}/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith-sidecar/knowledge/installers.md

@@ -30,7 +30,7 @@
 ### IDE Manager & Base
 
 - @/tools/cli/installers/lib/ide/manager.js - IdeManager class (dynamic handler loading)
-- @/tools/cli/installers/lib/ide/\_base-ide.js - BaseIdeSetup class (all handlers extend this)
+- @/tools/cli/installers/lib/ide/_base-ide.js - BaseIdeSetup class (all handlers extend this)
 
 ### Shared Utilities
 
@@ -117,7 +117,7 @@ Contains:
 
 - Add new IDE handler: Create file in /tools/cli/installers/lib/ide/, extend BaseIdeSetup
 - Fix installer bug: Check installer.js (94KB - main logic)
-- Add module installer: Create \_module-installer/installer.js if custom installer logic needed
+- Add module installer: Create _module-installer/installer.js if custom installer logic needed
 - Update shared generators: Modify files in /shared/ directory
 
 ## Relationships

package/{docs → samples}/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith-sidecar/knowledge/modules.md

@@ -142,7 +142,7 @@ Defined in @/tools/cli/lib/platform-codes.js
 
 ## Common Tasks
 
-- Create new module installer: Add \_module-installer/installer.js
+- Create new module installer: Add _module-installer/installer.js
 - Add IDE sub-module: Create sub-modules/{ide-name}/ with config
 - Add new IDE support: Create handler in installers/lib/ide/
 - Customize module installation: Modify module.yaml

package/{docs → samples}/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-01-init.md

@@ -66,7 +66,7 @@ To set up the quiz game by selecting game mode, choosing a category, and prepari
 
 ### 1. Welcome and Configuration Loading
 
-Load config from {project-root}/\_bmad/bmb/config.yaml to get user_name.
+Load config from {project-root}/_bmad/bmb/config.yaml to get user_name.
 
 Present dramatic welcome:
 "🎺 _DRAMATIC MUSIC PLAYS_ 🎺

package/{docs → samples}/sample-custom-modules/sample-unitary-module/workflows/quiz-master/workflow.md

@@ -45,7 +45,7 @@ web_bundle: true
 
 ### 1. Module Configuration Loading
 
-Load and read full config from {project-root}/\_bmad/bmb/config.yaml and resolve:
+Load and read full config from {project-root}/_bmad/bmb/config.yaml and resolve:
 
 - `user_name`, `output_folder`, `communication_language`, `document_output_language`
 

package/src/core/tasks/review-adversarial-general.xml

@@ -0,0 +1,41 @@
+<!-- if possible, run this in a separate subagent or process with read access to the project, 
+  but no context except the content to review -->
+
+<task id="_bmad/core/tasks/review-adversarial-general.xml" name="Adversarial Review (General)">
+  <objective>Cynically review content and produce findings</objective>
+
+  <inputs>
+    <input name="content" desc="Content to review - diff, spec, story, doc, or any artifact" />
+  </inputs>
+
+  <llm critical="true">
+    <i>You are a cynical, jaded reviewer with zero patience for sloppy work</i>
+    <i>The content was submitted by a clueless weasel and you expect to find problems</i>
+    <i>Be skeptical of everything</i>
+    <i>Look for what's missing, not just what's wrong</i>
+    <i>Use a precise, professional tone - no profanity or personal attacks</i>
+  </llm>
+
+  <flow>
+    <step n="1" title="Receive Content">
+      <action>Load the content to review from provided input or context</action>
+      <action>If content to review is empty, ask for clarification and abort task</action>
+      <action>Identify content type (diff, branch, uncommitted changes, document, etc.)</action>
+    </step>
+
+    <step n="2" title="Adversarial Analysis" critical="true">
+      <mandate>Review with extreme skepticism - assume problems exist</mandate>
+      <action>Find at least ten issues to fix or improve in the provided content</action>
+    </step>
+
+    <step n="3" title="Present Findings">
+      <action>Output findings as a Markdown list (descriptions only)</action>
+    </step>
+  </flow>
+
+  <halt-conditions>
+    <condition>HALT if zero findings - this is suspicious, re-analyze or ask for guidance</condition>
+    <condition>HALT if content is empty or unreadable</condition>
+  </halt-conditions>
+
+</task>

package/src/modules/bmb/README.md

@@ -0,0 +1,25 @@
+# BMB - BMad Builder Module
+
+Specialized tools and workflows for creating, customizing, and extending BMad components including agents, workflows, and complete modules.
+
+## Overview
+
+BMB provides a complete toolkit for extending BMad Method with disciplined, systematic approaches to agent and workflow development while maintaining framework consistency and power.
+
+**1 Master Builder Agent** | **5 Creation Workflows** | **3 Agent Architectures**
+
+## Documentation
+
+For complete documentation, architecture guides, and reference materials:
+
+**[→ BMB Documentation](./docs/index.md)**
+
+## Quick Links
+
+- [Agent Creation Guide](./docs/agents/index.md) - Build custom agents
+- [Workflow Architecture](./docs/workflows/index.md) - Design workflows
+- [Reference Examples](./reference/) - Working examples and templates
+
+---
+
+Part of [BMad Method](https://github.com/bmadcode/bmad-method) v6.0

package/src/modules/bmb/docs/agents/expert-agent-architecture.md

@@ -223,7 +223,7 @@ Same as simple agents, PLUS:
 
 ## Reference Example
 
-See: `bmb/reference/agents/expert-examples/journal-keeper/`
+See: [journal-keeper/](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/agents/expert-examples/journal-keeper)
 
 Features demonstrated:
 
@@ -355,8 +355,8 @@ identity: |
 - [ ] Sidecar folder structure created and populated
 - [ ] memories.md has clear section structure
 - [ ] instructions.md contains core directives
-- [ ] Menu actions reference \_bmad/\_memory correctly
-- [ ] File paths use \_bmad/\_memory/[agentname]-sidecar/ to reference sidecar content
+- [ ] Menu actions reference _bmad/_memory correctly
+- [ ] File paths use _bmad/_memory/[agentname]-sidecar/ to reference sidecar content
 - [ ] Install config personalizes sidecar references
 - [ ] Agent folder named consistently: `{agent-name}/`
 - [ ] YAML file named: `{agent-name}.agent.yaml`

package/src/modules/bmb/docs/agents/index.md

@@ -9,7 +9,7 @@ Comprehensive guides for each agent type (choose based on use case):
 - [Understanding Agent Types](./understanding-agent-types.md) - **START HERE** - Architecture vs capability, "The Same Agent, Three Ways"
 - [Simple Agent Architecture](./simple-agent-architecture.md) - Self-contained, optimized, personality-driven
 - [Expert Agent Architecture](./expert-agent-architecture.md) - Memory, sidecar files, domain restrictions
-- [Module Agent Architecture](./module-agent-architecture.md) - Workflow integration, professional tools
+- Module Agent Architecture _(TODO)_ - Workflow integration, professional tools
 
 ## Agent Design Patterns
 
@@ -18,20 +18,20 @@ Comprehensive guides for each agent type (choose based on use case):
 
 ## Reference Examples
 
-Production-ready examples in `/bmb/reference/agents/`:
+Production-ready examples in [bmb/reference/agents/](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/agents):
 
-**Simple Agents** (`simple-examples/`)
+**Simple Agents** ([simple-examples/](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/agents/simple-examples))
 
-- `commit-poet.agent.yaml` - Commit message artisan with style customization
+- [commit-poet.agent.yaml](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/agents/simple-examples/commit-poet.agent.yaml) - Commit message artisan with style customization
 
-**Expert Agents** (`expert-examples/`)
+**Expert Agents** ([expert-examples/](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/agents/expert-examples))
 
-- `journal-keeper/` - Personal journal companion with memory and pattern recognition
+- [journal-keeper/](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/agents/expert-examples/journal-keeper) - Personal journal companion with memory and pattern recognition
 
-**Module Agents** (`module-examples/`)
+**Module Agents** ([module-examples/](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/agents/module-examples))
 
-- `security-engineer.agent.yaml` - BMM security specialist with threat modeling
-- `trend-analyst.agent.yaml` - CIS trend intelligence expert
+- [security-engineer.agent.yaml](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/agents/module-examples/security-engineer.agent.yaml) - BMM security specialist with threat modeling
+- [trend-analyst.agent.yaml](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/agents/module-examples/trend-analyst.agent.yaml) - CIS trend intelligence expert
 
 ## Installation Guide
 

package/src/modules/bmb/docs/agents/simple-agent-architecture.md

@@ -206,7 +206,7 @@ The `tools/cli/lib/agent/compiler.js` automatically adds:
 
 ## Reference Example
 
-See: `../../reference/agents/simple-examples/commit-poet.agent.yaml`
+See: [commit-poet.agent.yaml](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/agents/simple-examples/commit-poet.agent.yaml)
 
 Features demonstrated:
 

package/src/modules/bmb/docs/agents/understanding-agent-types.md

@@ -7,7 +7,7 @@ ALL agent types can:
 - ✓ Write to {output_folder}, {project-root}, or anywhere on system
 - ✓ Update artifacts and files
 - ✓ Execute bash commands
-- ✓ Use core variables (\_bmad, {output_folder}, etc.)
+- ✓ Use core variables (_bmad, {output_folder}, etc.)
 - ✓ Have complex prompts and logic
 - ✓ Invoke external tools
 

package/src/modules/bmb/docs/{README.md → index.md}

@@ -20,8 +20,6 @@ Specialized tools and workflows for creating, customizing, and extending BMad co
 
 - Install Location: `_bmad/bmb/agents/bmad-builder.md`
 
-### 📋 Workflows
-
 ### 📚 Documentation
 
 - Comprehensive guides for agents, workflows, and modules
@@ -46,33 +44,33 @@ Specialized tools and workflows for creating, customizing, and extending BMad co
 
 - **[Workflow Index](./workflows/index.md)** - Core workflow system overview
 - **[Architecture Guide](./workflows/architecture.md)** - Step-file design and JIT loading
-- **[Template System](./workflows/templates/step-template.md)** - Standard step file template
+- **Template System** _(TODO)_ - Standard step file template
 - **[Intent vs Prescriptive](./workflows/intent-vs-prescriptive-spectrum.md)** - Design philosophy
 
 ## Reference Materials
 
 ### 🤖 Agent Examples
 
-- **[Simple Agent Example](../reference/agents/simple-examples/commit-poet.agent.yaml)** - Self-contained agent
-- **[Expert Agent Example](../reference/agents/expert-examples/journal-keeper/journal-keeper.agent.yaml)** - Agent with persistent memory
-- **[Module Add On Agent Examples](../reference/agents/module-examples/security-engineer.agent.yaml)** - Integration patterns (BMM, CIS)
+- **[Simple Agent Example](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/agents/simple-examples/commit-poet.agent.yaml)** - Self-contained agent
+- **[Expert Agent Example](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/agents/expert-examples/journal-keeper/journal-keeper.agent.yaml)** - Agent with persistent memory
+- **[Module Add On Agent Examples](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/agents/module-examples/security-engineer.agent.yaml)** - Integration patterns (BMM, CIS)
 
 ### 📋 Workflow Examples
 
-- **[Meal Prep & Nutrition](./reference/workflows/meal-prep-nutrition/)** - Complete step-file workflow demonstration
+- **[Meal Prep & Nutrition](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/workflows/meal-prep-nutrition)** - Complete step-file workflow demonstration
 - **Template patterns** for document generation and state management
 
 ## Core Workflows
 
 ### Creation Workflows (Step-File Architecture)
 
-**[create-agent](./workflows/create-agent/)** - Build BMad agents
+**create-agent** _(TODO)_ - Build BMad agents
 
 - 11 guided steps from brainstorming to celebration
 - 18 reference data files with validation checklists
 - Template-based agent generation
 
-**[create-workflow](./workflows/create-workflow/)** - Design workflows
+**create-workflow** _(TODO)_ - Design workflows
 
 - 12 structured steps from init to review
 - 9 template files for workflow creation
@@ -80,13 +78,13 @@ Specialized tools and workflows for creating, customizing, and extending BMad co
 
 ### Editing Workflows
 
-**[edit-agent](./workflows/edit-agent/)** - Modify existing agents
+**edit-agent** _(TODO)_ - Modify existing agents
 
 - 5 steps: discovery → validation
 - Intent-driven analysis and updates
 - Best practice compliance
 
-**[edit-workflow](./workflows/edit-workflow/)** - Update workflows
+**edit-workflow** _(TODO)_ - Update workflows
 
 - 5 steps: analyze → compliance check
 - Structure maintenance and validation
@@ -94,7 +92,7 @@ Specialized tools and workflows for creating, customizing, and extending BMad co
 
 ### Quality Assurance
 
-**[workflow-compliance-check](./workflows/workflow-compliance-check/)** - Validation
+**workflow-compliance-check** _(TODO)_ - Validation
 
 - 8 systematic validation steps
 - Adversarial analysis approach

package/src/modules/bmb/docs/workflows/index.md

@@ -12,27 +12,27 @@ Essential terminology and concepts for understanding BMAD workflows.
 
 The micro-file architecture, JIT step loading, state management, and collaboration patterns that make BMAD workflows optimal for AI execution.
 
-### [Writing Workflows](./writing-workflows.md)
+### Writing Workflows _(TODO)_
 
 Complete guide to creating workflows: workflow.md control files, step files, CSV data integration, and frontmatter design.
 
-### [Step Files & Dialog Patterns](./step-files.md)
+### Step Files & Dialog Patterns _(TODO)_
 
 Crafting effective step files: structure, execution rules, prescriptive vs intent-based dialog, and validation patterns.
 
-### [Templates & Content Generation](./templates.md)
+### Templates & Content Generation _(TODO)_
 
 Creating append-only templates, frontmatter design, conditional content, and dynamic content generation strategies.
 
-### [Workflow Patterns](./patterns.md)
+### Workflow Patterns _(TODO)_
 
 Common workflow types: linear, conditional, protocol integration, multi-agent workflows, and real-world examples.
 
-### [Migration Guide](./migration.md)
+### Migration Guide _(TODO)_
 
 Converting from XML-heavy workflows to the new pure markdown format, with before/after examples and checklist.
 
-### [Best Practices & Reference](./best-practices.md)
+### Best Practices & Reference _(TODO)_
 
 Critical rules, anti-patterns, performance optimization, debugging, quick reference templates, and troubleshooting.
 

package/src/modules/bmb/docs/workflows/templates/step-01-init-continuable-template.md

@@ -13,16 +13,16 @@ description: 'Initialize the [workflow-type] workflow by detecting continuation
 
 <!-- Path Definitions -->
 
-workflow\*path: '{project-root}/\_bmad/[module-path]/workflows/[workflow-name]'
+workflow\*path: `{project-root}/_bmad/[module-path]/workflows/[workflow-name]`
 
 # File References (all use {variable} format in file)
 
-thisStepFile: '{workflow_path}/steps/step-01-init.md'
-nextStepFile: '{workflow_path}/steps/step-02-[step-name].md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/[output-file-name]-{project_name}.md'
-continueFile: '{workflow_path}/steps/step-01b-continue.md'
-templateFile: '{workflow_path}/templates/[main-template].md'
+thisStepFile: `{workflow_path}/steps/step-01-init.md`
+nextStepFile: `{workflow_path}/steps/step-02-[step-name].md`
+workflowFile: `{workflow_path}/workflow.md`
+outputFile: `{output_folder}/[output-file-name]-{project_name}.md`
+continueFile: `{workflow_path}/steps/step-01b-continue.md`
+templateFile: `{workflow_path}/templates/[main-template].md`
 
 # Template References
 

package/src/modules/bmb/docs/workflows/templates/step-1b-template.md

@@ -13,7 +13,7 @@ description: 'Handle workflow continuation from previous session'
 
 <!-- Path Definitions -->
 
-workflow\*path: '{project-root}/\_bmad/[module-path]/workflows/[workflow-name]'
+workflow\*path: '{project-root}/_bmad/[module-path]/workflows/[workflow-name]'
 
 # File References (all use {variable} format in file)
 

package/src/modules/bmb/docs/workflows/templates/step-template.md

@@ -11,7 +11,7 @@ description: '[Brief description of what this step accomplishes]'
 
 <!-- Path Definitions -->
 
-workflow\*path: '{project-root}/\_bmad/[module]/reference/workflows/[workflow-name]' # the folder the workflow.md file is in
+workflow\*path: '{project-root}/_bmad/[module]/reference/workflows/[workflow-name]' # the folder the workflow.md file is in
 
 # File References (all use {variable} format in file)
 
@@ -23,8 +23,8 @@ outputFile: '{output_folder}/[output-file-name]-{project_name}.md'
 
 # Task References (IF THE workflow uses and it makes sense in this step to have these )
 
-advancedElicitationTask: '{project-root}/\_bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/\_bmad/core/workflows/party-mode/workflow.md'
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 
 # Template References (if this step uses a specific templates)
 
@@ -243,7 +243,7 @@ Display: "**Select an Option:** [A] [Continue to Step Foo] [A] [Continue to Step
 
 ### Initialization Step Example
 
-See [step-01-init.md](../reference/workflows/meal-prep-nutrition/steps/step-01-init.md) for an example of:
+See [step-01-init.md](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md) for an example of:
 
 - Detecting existing workflow state and short circuit to 1b
 - Creating output documents from templates
@@ -252,7 +252,7 @@ See [step-01-init.md](../reference/workflows/meal-prep-nutrition/steps/step-01-i
 
 ### Continuation Step Example
 
-See [step-01b-continue.md](../reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md) for an example of:
+See [step-01b-continue.md](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md) for an example of:
 
 - Handling already-in-progress workflows
 - Detecting completion status
@@ -261,7 +261,7 @@ See [step-01b-continue.md](../reference/workflows/meal-prep-nutrition/steps/step
 
 ### Standard Step with Menu Example
 
-See [step-02-profile.md](../reference/workflows/meal-prep-nutrition/steps/step-02-profile.md) for an example of:
+See [step-02-profile.md](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md) for an example of:
 
 - Presenting a menu with A/P/C options
 - Forcing halt until user selects 'C' (Continue)
@@ -271,7 +271,7 @@ See [step-02-profile.md](../reference/workflows/meal-prep-nutrition/steps/step-0
 
 ### Final Step Example
 
-See [step-06-prep-schedule.md](../reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md) for an example of:
+See [step-06-prep-schedule.md](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md) for an example of:
 
 - Completing workflow deliverables
 - Marking workflow as complete in frontmatter

package/src/modules/bmb/docs/workflows/templates/workflow-template.md

@@ -53,7 +53,7 @@ web_bundle: [true/false] # Set to true for inclusion in web bundle builds
 
 ### 1. Module Configuration Loading
 
-Load and read full config from {project-root}/\_bmad/[MODULE FOLDER]/config.yaml and resolve:
+Load and read full config from {project-root}/_bmad/[MODULE FOLDER]/config.yaml and resolve:
 
 - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, [MODULE VARS]
 

package/src/modules/bmb/docs/workflows/templates/workflow.md

@@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution:
 
 ### 1. Configuration Loading
 
-Load and read full config from {project-root}/\_bmad/{{targetModule}}/config.yaml and resolve:
+Load and read full config from {project-root}/_bmad/{{targetModule}}/config.yaml and resolve:
 
 - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
 

package/src/modules/bmb/reference/workflows/meal-prep-nutrition/workflow.md

@@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution:
 
 ### 1. Configuration Loading
 
-Load and read full config from {project-root}/\_bmad/core/config.yaml and resolve:
+Load and read full config from {project-root}/_bmad/core/config.yaml and resolve:
 
 - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
 

package/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/workflow.md

@@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution:
 
 ### 1. Configuration Loading
 
-Load and read full config from {project-root}/\_bmad/bmm/config.yaml and resolve:
+Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:
 
 - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level`
 

package/src/modules/bmb/workflows/create-agent/templates/expert-agent.template.md

@@ -313,7 +313,7 @@ critical_actions:
 
 1. **Load sidecar files in critical_actions** - Must be explicit and MANDATORY
 2. **Enforce domain restrictions** - Clear boundaries prevent scope creep
-3. **Use \_bmad/\_memory/[agentname]-sidcar/ paths** - For reference to any sidecar content
+3. **Use _bmad/_memory/[agentname]-sidcar/ paths** - For reference to any sidecar content
 4. **Design for memory growth** - Structure sidecar files for accumulation
 5. **Reference past naturally** - Don't dump memory, weave it into conversation
 6. **Separate concerns** - Memories, instructions, knowledge in distinct files
@@ -356,8 +356,8 @@ identity: |
 - [ ] Sidecar folder structure created and populated
 - [ ] memories.md has clear section structure
 - [ ] instructions.md contains core directives
-- [ ] Menu actions reference \_bmad/\_memory/[agentname]-sidcar/ correctly if needing sidecar content reference
-- [ ] File paths use \_bmad/\_memory/[agentname]-sidcar/ to reference where the file will be after sidecar content is installed
+- [ ] Menu actions reference _bmad/_memory/[agentname]-sidcar/ correctly if needing sidecar content reference
+- [ ] File paths use _bmad/_memory/[agentname]-sidcar/ to reference where the file will be after sidecar content is installed
 - [ ] Install config personalizes sidecar references
 - [ ] Agent folder named consistently: `{agent-name}/`
 - [ ] YAML file named: `{agent-name}.agent.yaml`

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

@@ -129,7 +129,7 @@ Create all directories in {bmb_creations_output_folder}/{module_name}/:
 3. **tasks/** - For task files (if tasks planned)
 4. **templates/** - For shared templates
 5. **data/** - For module data
-6. **\_module-installer/** - For installation configuration
+6. **_module-installer/** - For installation configuration
 
 ### 4. Create Placeholder README
 

package/src/modules/bmb/workflows/create-module/steps/step-08-installer.md

@@ -71,8 +71,8 @@ From step 5, we planned these configuration fields:
 
 ### 2. Create Installer Directory
 
-Ensure \_module-installer directory exists
-Directory: {bmb_creations_output_folder}/{module_name}/\_module-installer/
+Ensure _module-installer directory exists
+Directory: {bmb_creations_output_folder}/{module_name}/_module-installer/
 
 ### 3. Create module.yaml
 
@@ -95,7 +95,7 @@ Does your module need any special setup during installation? For example:
 
 "I'll create an installer.js file for custom logic."
 
-Create file: {bmb_creations_output_folder}/{module_name}/\_module-installer/installer.js from {installerTemplate}
+Create file: {bmb_creations_output_folder}/{module_name}/_module-installer/installer.js from {installerTemplate}
 
 Update installer.js with module-specific logic
 
@@ -105,7 +105,7 @@ Update installer.js with module-specific logic
 
 If your module needs to copy files during installation (templates, examples, documentation), we can add them to the assets directory."
 
-Create directory: \_module-installer/assets/
+Create directory: _module-installer/assets/
 Add note about what assets to include
 
 ### 6. Document Installer Setup
@@ -131,7 +131,7 @@ Update module-plan.md with installer section:
 
 1. User runs: `bmad install {module_name}`
 2. Installer asks: [list of questions]
-3. Creates: \_bmad/{module_name}/
+3. Creates: _bmad/{module_name}/
 4. Generates: config.yaml with user settings
 
 ### Validation

package/src/modules/bmb/workflows/create-module/templates/agent.template.md

@@ -264,7 +264,7 @@ Analyze the visual design with my signature dramatic flair
 menu: # Core interactions - multi: "[CH] Chat with Caravaggio or [SPM] Start Party Mode"
 triggers: - party-mode:
 input: SPM or fuzzy match start party mode
-route: "{project-root}/\_bmad/core/workflows/edit-agent/workflow.md"
+route: "{project-root}/_bmad/core/workflows/edit-agent/workflow.md"
 data: what's being discussed, plus custom party agents if specified
 type: exec - expert-chat:
 input: CH or fuzzy match validate agent

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

@@ -11,11 +11,11 @@ This document provides the validation criteria used in step-11-validate.md to en
 - [ ] tasks/ - Task files (if needed)
 - [ ] templates/ - Shared templates
 - [ ] data/ - Module data
-- [ ] \_module-installer/ - Installation config
+- [ ] _module-installer/ - Installation config
 - [ ] README.md - Module documentation
 - [ ] module.yaml - module config file
 
-### Optional File in \_module-installer/
+### Optional File in _module-installer/
 
 - [ ] installer.js - Custom logic (if needed)
 

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

@@ -46,7 +46,7 @@ installed_path: '{project-root}/_bmad/bmb/workflows/create-module'
 
 ### 1. Module Configuration Loading
 
-Load and read full config from {project-root}/\_bmad/bmb/config.yaml and resolve:
+Load and read full config from {project-root}/_bmad/bmb/config.yaml and resolve:
 
 - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `bmb_creations_output_folder`
 

package/src/modules/bmb/workflows/create-workflow/steps/step-07-build.md

@@ -72,7 +72,7 @@ To generate all the workflow files (workflow.md, step files, templates, and supp
 - When building continuable step-01-init.md files, use template `{project-root}/_bmad/bmb/docs/workflows/templates/step-01-init-continuable-template.md`
 - When building continuation steps, use template `{project-root}/_bmad/bmb/docs/workflows/templates/step-1b-template.md`
 - When building the main workflow.md file, you must follow template `{project-root}/_bmad/bmb/docs/workflows/templates/workflow-template.md`
-- Example step files from {project-root}/\_bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md for patterns
+- Example step files from {project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md for patterns
 
 ## FILE GENERATION SEQUENCE:
 
@@ -117,7 +117,7 @@ Load and follow {workflowTemplate}:
 
 - Create workflow.md using template structure
 - Insert workflow name and description
-- Configure all path variables ({project-root}, \_bmad, {workflow_path})
+- Configure all path variables ({project-root}, _bmad, {workflow_path})
 - Set web_bundle flag to true unless user has indicated otherwise
 - Define role and goal
 - Include initialization path to step-01

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

@@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution:
 
 ### 1. Configuration Loading
 
-Load and read full config from {project-root}/\_bmad/bmb/config.yaml and resolve:
+Load and read full config from {project-root}/_bmad/bmb/config.yaml and resolve:
 
 - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `bmb_creations_output_folder`
 

package/src/modules/bmb/workflows/edit-agent/workflow.md

@@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution:
 
 ### 1. Configuration Loading
 
-Load and read full config from {project-root}/\_bmad/bmb/config.yaml and resolve:
+Load and read full config from {project-root}/_bmad/bmb/config.yaml and resolve:
 
 - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
 

package/src/modules/bmb/workflows/edit-workflow/workflow.md

@@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution:
 
 ### 1. Configuration Loading
 
-Load and read full config from {project-root}/\_bmad/bmb/config.yaml and resolve:
+Load and read full config from {project-root}/_bmad/bmb/config.yaml and resolve:
 
 - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
 

package/src/modules/bmb/workflows/workflow-compliance-check/steps/step-02-workflow-validation.md

@@ -135,7 +135,7 @@ For each deviation:
 - Configuration Loading uses correct path format: `{project-root}/_bmad/[module]/config.yaml` (variable substitution pattern)
 - First step follows pattern: `step-01-init.md` OR documented deviation
 - Required config variables properly listed
-- Variables use proper substitution pattern: {project-root}, \_bmad, {workflow_path}, etc.
+- Variables use proper substitution pattern: {project-root}, _bmad, {workflow_path}, etc.
 
 For violations:
 

package/src/modules/bmb/workflows/workflow-compliance-check/workflow.md

@@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution:
 
 ### 1. Configuration Loading
 
-Load and read full config from {project-root}/\_bmad/bmb/config.yaml and resolve:
+Load and read full config from {project-root}/_bmad/bmb/config.yaml and resolve:
 
 - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
 

package/src/modules/bmb/workflows-legacy/edit-module/checklist.md

@@ -126,7 +126,7 @@ Use this checklist to validate module edits meet BMAD Core standards.
 
 - [ ] Web bundles configured in workflow.yaml files
 - [ ] All referenced files included in web_bundle_files
-- [ ] Paths are \_bmad/-relative (not project-root)
+- [ ] Paths are _bmad/-relative (not project-root)
 - [ ] No config_source references in web bundles
 - [ ] Invoked workflows included in dependencies