bmad-method 6.0.0-alpha.15 → 6.0.0-alpha.17

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

@@ -97,14 +97,22 @@ agent:
       action: 'Update ./{agent-name}-sidecar/memories.md with session insights'
       description: 'Save what we discussed today'
 
-    - trigger: patterns
-      action: '#memory-recall'
-      description: 'Recall patterns from past interactions'
-
     - trigger: insight
       action: 'Document breakthrough in ./{agent-name}-sidecar/breakthroughs.md'
       description: 'Record a significant insight'
 
+    - multi: "[DF] Do Foo or start [CH] Chat with expert"
+      triggers:
+        - do-foo
+            - input: [DF] or fuzzy match on do foo
+            - action: '#main-action'
+            - data: what is being discussed or suggested with the command, along with custom party custom agents if specified
+            - type: action
+        - expert-chat:
+            - input: [CH] or fuzzy match validate agent
+            - action: agent responds as expert based on its persona to converse
+            - type: action
+
   install_config:
     compile_time_only: true
     description: 'Personalize your expert agent'
@@ -196,14 +204,6 @@ critical_actions:
 - **Memory integration** - Past context becomes part of current session
 - **Protocol adherence** - Ensures consistent behavior
 
-### {agent_sidecar_folder} Variable
-
-Special variable resolved during installation:
-
-- Points to the agent's installation directory
-- Used to reference sidecar files
-- Example: `.bmad/custom/agents/journal-keeper/`
-
 ## What Gets Injected at Compile Time
 
 Same as simple agents, PLUS:
@@ -223,7 +223,7 @@ Same as simple agents, PLUS:
 
 ## Reference Example
 
-See: `src/modules/bmb/reference/agents/expert-examples/journal-keeper/`
+See: `bmb/reference/agents/expert-examples/journal-keeper/`
 
 Features demonstrated:
 
@@ -238,7 +238,7 @@ Features demonstrated:
 
 ```bash
 # Copy entire folder to your project
-cp -r /path/to/journal-keeper/ .bmad/custom/agents/
+cp -r /path/to/journal-keeper/ _bmad/custom/agents/
 
 # Install with personalization
 bmad agent-install
@@ -312,12 +312,11 @@ critical_actions:
 ## Best Practices
 
 1. **Load sidecar files in critical_actions** - Must be explicit and MANDATORY
-2. **Enforce domain restrictions** - Clear boundaries prevent scope creep
-3. **Use {agent_sidecar_folder} paths** - Portable across installations
-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
-7. **Include privacy features** - Users trust expert agents with personal data
+2. **Enforce domain restrictions** - Clear boundaries prevent scope creep=
+3. **Design for memory growth** - Structure sidecar files for accumulation
+4. **Reference past naturally** - Don't dump memory, weave it into conversation
+5. **Separate concerns** - Memories, instructions, knowledge in distinct files
+6. **Include privacy features** - Users trust expert agents with personal data
 
 ## Common Patterns
 
@@ -356,8 +355,8 @@ identity: |
 - [ ] Sidecar folder structure created and populated
 - [ ] memories.md has clear section structure
 - [ ] instructions.md contains core directives
-- [ ] Menu actions reference {agent_sidecar_folder} correctly
-- [ ] File paths use {agent_sidecar_folder} variable
+- [ ] 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

@@ -18,7 +18,7 @@ Comprehensive guides for each agent type (choose based on use case):
 
 ## Reference Examples
 
-Production-ready examples in `/src/modules/bmb/reference/agents/`:
+Production-ready examples in `/bmb/reference/agents/`:
 
 **Simple Agents** (`simple-examples/`)
 

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

@@ -14,7 +14,7 @@ Self-contained agents with prompts, menus, and optional install-time customizati
 ```yaml
 agent:
   metadata:
-    id: .bmad/agents/{agent-name}/{agent-name}.md
+    id: _bmad/agents/{agent-name}/{agent-name}.md
     name: 'Persona Name'
     title: 'Agent Title'
     icon: 'emoji'
@@ -63,18 +63,22 @@ agent:
         Another reusable prompt template
 
   menu:
-    - trigger: action1
-      action: '#main-action'
-      description: 'Execute the main action'
-
-    - trigger: action2
-      action: '#another-action'
-      description: 'Execute another action'
-
     - trigger: inline
-      action: 'Direct inline instruction text'
+      action: 'Direct inline prompt text'
       description: 'Execute inline action'
 
+    - multi: "[DF] Do Foo or start [CH] Chat with expert"
+      triggers:
+        - do-foo
+            - input: [DF] or fuzzy match on do foo
+            - action: '#main-action'
+            - data: what is being discussed or suggested with the command, along with custom party custom agents if specified
+            - type: action
+        - expert-chat:
+            - input: [CH] or fuzzy match validate agent
+            - action: agent responds as expert based on its persona to converse
+            - type: action
+
   install_config:
     compile_time_only: true
     description: 'Personalize your agent'
@@ -104,7 +108,7 @@ agent:
 
 ### Metadata
 
-- **id**: Final compiled path (`.bmad/agents/{name}/{name}.md` for standalone)
+- **id**: Final compiled path (`_bmad/agents/{name}/{name}.md` for standalone)
 - **name**: Agent's persona name displayed to users
 - **title**: Professional role/function
 - **icon**: Single emoji for visual identification
@@ -202,7 +206,7 @@ The `tools/cli/lib/agent/compiler.js` automatically adds:
 
 ## Reference Example
 
-See: `src/modules/bmb/reference/agents/simple-examples/commit-poet.agent.yaml`
+See: `../../reference/agents/simple-examples/commit-poet.agent.yaml`
 
 Features demonstrated:
 
@@ -215,7 +219,7 @@ Features demonstrated:
 
 ```bash
 # Copy to your project
-cp /path/to/commit-poet.agent.yaml .bmad/custom/agents/
+cp /path/to/commit-poet.agent.yaml _bmad/custom/agents/
 
 # Create custom.yaml and install
 echo "code: my-agent
@@ -243,50 +247,11 @@ The installer:
 5. **Use semantic XML tags** in prompt content for clarity
 6. **Test all conditional paths** before distribution
 
-## Common Patterns
-
-### Style Variants
-
-```yaml
-communication_style: |
-  {{#if enthusiasm == "high"}}
-  Enthusiastic and energetic approach!
-  {{/if}}
-  {{#if enthusiasm == "moderate"}}
-  Balanced and professional demeanor.
-  {{/if}}
-```
-
-### Feature Toggles
-
-```yaml
-prompts:
-  - id: main-action
-    content: |
-      {{#if advanced_mode}}
-      Include advanced analysis steps...
-      {{/if}}
-      {{#unless advanced_mode}}
-      Basic analysis only...
-      {{/unless}}
-```
-
-### User Personalization
-
-```yaml
-identity: |
-  {{#if custom_name}}
-  Known as {{custom_name}} to you.
-  {{/if}}
-```
-
 ## Validation Checklist
 
 - [ ] Valid YAML syntax
 - [ ] All metadata fields present (id, name, title, icon, type)
 - [ ] Persona complete (role, identity, communication_style, principles)
 - [ ] Prompts have unique IDs
-- [ ] Menu triggers don't start with `*` (auto-added)
 - [ ] Install config questions have defaults
-- [ ] Handlebars syntax is correct
 - [ ] File named `{agent-name}.agent.yaml`

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_folder}, {output_folder}, etc.)
+- ✓ Use core variables (\_bmad, {output_folder}, etc.)
 - ✓ Have complex prompts and logic
 - ✓ Invoke external tools
 
@@ -98,11 +98,11 @@ agent:
 
   menu:
     - trigger: implement-story
-      workflow: '{bmad_folder}/bmm/workflows/dev-story/workflow.yaml'
+      workflow: '_bmad/bmm/workflows/dev-story/workflow.yaml'
       description: Implement user story
 
     - trigger: refactor
-      workflow: '{bmad_folder}/bmm/workflows/refactor/workflow.yaml'
+      workflow: '_bmad/bmm/workflows/refactor/workflow.yaml'
       description: Refactor codebase
 ```
 
@@ -122,7 +122,7 @@ agent:
 ### The Reality
 
 - **Any agent type** (Simple, Expert, Module) can be bundled with or added to a module
-- A Simple agent COULD live in `.bmad/bmm/agents/`
+- A Simple agent COULD live in `_bmad/bmm/agents/`
 - An Expert agent COULD be included in a module bundle
 
 ### What Makes a "Module Agent" Special
@@ -138,14 +138,14 @@ A **Module Agent** is specifically:
 
 **Simple Agent added to BMM:**
 
-- Lives in `.bmad/bmm/agents/formatter.agent.yaml`
+- Lives in `_bmad/bmm/agents/formatter.agent.yaml`
 - Bundled with BMM for convenience
 - But still stateless, self-contained
 - NOT a "Module Agent" - just a Simple agent in a module
 
 **Module Agent in BMM:**
 
-- Lives in `.bmad/bmm/agents/tech-writer.agent.yaml`
+- Lives in `_bmad/bmm/agents/tech-writer.agent.yaml`
 - Orchestrates BMM documentation workflows
 - Coordinates with other BMM agents (PM, Dev, Analyst)
 - Included in default BMM bundle

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

@@ -69,7 +69,7 @@ workflow-folder/
 Standard variables in step files:
 
 ```yaml
-workflow_path: '{project-root}/{*bmad_folder*}/bmb/reference/workflows/[workflow-name]'
+workflow_path: '{project-root}/_bmad/bmb/reference/workflows/[workflow-name]'
 thisStepFile: '{workflow_path}/steps/step-[N]-[name].md'
 nextStepFile: '{workflow_path}/steps/step-[N+1]-[name].md'
 workflowFile: '{workflow_path}/workflow.md'

package/src/modules/bmb/docs/workflows/common-workflow-tools.csv

@@ -1,7 +1,7 @@
 propose,type,tool_name,description,url,requires_install
-always,workflow,party-mode,"Enables collaborative idea generation by managing turn-taking, summarizing contributions, and synthesizing ideas from multiple AI personas in structured conversation sessions about workflow steps or work in progress.",{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md,no
-always,task,advanced-elicitation,"Employs diverse elicitation strategies such as Socratic questioning, role-playing, and counterfactual analysis to critically evaluate and enhance LLM outputs, forcing assessment from multiple perspectives and techniques.",{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml,no
-always,task,brainstorming,"Facilitates idea generation by prompting users with targeted questions, encouraging divergent thinking, and synthesizing concepts into actionable insights through collaborative creative exploration.",{project-root}/{bmad_folder}/core/tasks/brainstorming.xml,no
+always,workflow,party-mode,"Enables collaborative idea generation by managing turn-taking, summarizing contributions, and synthesizing ideas from multiple AI personas in structured conversation sessions about workflow steps or work in progress.",{project-root}/_bmad/core/workflows/party-mode/workflow.md,no
+always,task,advanced-elicitation,"Employs diverse elicitation strategies such as Socratic questioning, role-playing, and counterfactual analysis to critically evaluate and enhance LLM outputs, forcing assessment from multiple perspectives and techniques.",{project-root}/_bmad/core/tasks/advanced-elicitation.xml,no
+always,task,brainstorming,"Facilitates idea generation by prompting users with targeted questions, encouraging divergent thinking, and synthesizing concepts into actionable insights through collaborative creative exploration.",{project-root}/_bmad/core/tasks/brainstorming.xml,no
 always,llm-tool-feature,web-browsing,"Provides LLM with capabilities to perform real-time web searches, extract relevant data, and incorporate current information into responses when up-to-date information is required beyond training knowledge.",,no
 always,llm-tool-feature,file-io,"Enables LLM to manage file operations such as creating, reading, updating, and deleting files, facilitating seamless data handling, storage, and document management within user environments.",,no
 always,llm-tool-feature,sub-agents,"Allows LLM to create and manage specialized sub-agents that handle specific tasks or modules within larger workflows, improving efficiency through parallel processing and modular task delegation.",,no

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

@@ -13,7 +13,7 @@ description: 'Initialize the [workflow-type] workflow by detecting continuation
 
 <!-- Path Definitions -->
 
-workflow*path: '{project-root}/{\_bmad_folder*}/[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-1b-template.md

@@ -13,7 +13,7 @@ description: 'Handle workflow continuation from previous session'
 
 <!-- Path Definitions -->
 
-workflow*path: '{project-root}/{\_bmad_folder*}/[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-file.md

@@ -3,7 +3,7 @@ name: "step-{{stepNumber}}-{{stepName}}"
 description: "{{stepDescription}}"
 
 # Path Definitions
-workflow_path: "{project-root}/{*bmad_folder*}/{{targetModule}}/workflows/{{workflowName}}"
+workflow_path: "{project-root}/_bmad/{{targetModule}}/workflows/{{workflowName}}"
 
 # File References
 thisStepFile: "{workflow_path}/steps/step-{{stepNumber}}-{{stepName}}.md"
@@ -16,8 +16,8 @@ outputFile: "{output_folder}/{{outputFileName}}-{project_name}.md"
 {{/hasOutput}}
 
 # Task References (list only if used in THIS step file instance and only the ones used, there might be others)
-advancedElicitationTask: "{project-root}/{*bmad_folder*}/core/tasks/advanced-elicitation.xml"
-partyModeWorkflow: "{project-root}/{*bmad_folder*}/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"
 
 {{#hasTemplates}}
 # Template References

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_folder*}/bmb/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_folder_}/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/{_bmad_folder_}/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)
 

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_folder_}/[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]
 
@@ -101,4 +101,4 @@ Example: Load, read the full file and then execute `{workflow_path}/steps/step-0
 
 ### NOTE: You can View a real example of a perfect workflow.md file that was created from this template
 
-`{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition/workflow.md`
+`{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md`

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_folder_}/{{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/module.yaml

@@ -1,26 +1,16 @@
-# BMAD™ Method Core Configuration
-
 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
-
 header: "BMad Optimized Builder (BoMB) Module Configuration"
-subheader: "Configure the settings for the BoMB Factory!\nThe agent, workflow and module builder for BMAD™"
+subheader: "Configure the settings for the BoMB Factory!\nThe agent, workflow and module builder for BMad™ "
+default_selected: false # This module will not be selected by default for new installations
 
 # Variables from Core Config inserted:
 ## user_name
 ## communication_language
+## document_output_language
 ## output_folder
-## bmad_folder
-## install_user_docs
-## kb_install
-
-custom_stand_alone_location:
-  prompt: "Where do custom agents and workflows get stored?"
-  default: "bmad-custom-src"
-  result: "{project-root}/{value}"
 
-custom_module_location:
-  prompt: "Where do custom modules get stored?"
-  default: "bmad-custom-modules-src"
+bmb_creations_output_folder:
+  prompt: "Where should BoMB generated agents, workflows and modules SOURCE be saved?"
+  default: "{output_folder}/bmb-creations"
   result: "{project-root}/{value}"

package/src/modules/bmb/reference/agents/expert-examples/journal-keeper/journal-keeper.agent.yaml

@@ -20,9 +20,9 @@ agent:
       - Reflection transforms experience into wisdom
 
   critical_actions:
-    - "Load COMPLETE file {agent_sidecar_folder}/journal-keeper-sidecar/memories.md and remember all past insights"
-    - "Load COMPLETE file {agent_sidecar_folder}/journal-keeper-sidecar/instructions.md and follow ALL journaling protocols"
-    - "ONLY read/write files in {agent_sidecar_folder}/journal-keeper-sidecar/ - this is our private space"
+    - "Load COMPLETE file {project-root}/_bmad/_memory/journal-keeper-sidecar/memories.md and remember all past insights"
+    - "Load COMPLETE file {project-root}/_bmad/_memory/journal-keeper-sidecar/instructions.md and follow ALL journaling protocols"
+    - "ONLY read/write files in {project-root}/_bmad/_memory/journal-keeper-sidecar/ - this is our private space"
     - "Track mood patterns, recurring themes, and breakthrough moments"
     - "Reference past entries naturally to show continuity"
 
@@ -120,7 +120,7 @@ agent:
       description: "Write today's journal entry"
 
     - trigger: quick
-      action: "Save a quick, unstructured entry to {agent_sidecar_folder}/journal-keeper-sidecar/entries/entry-{date}.md with timestamp and any patterns noticed"
+      action: "Save a quick, unstructured entry to {project-root}/_bmad/_memory/journal-keeper-sidecar/entries/entry-{date}.md with timestamp and any patterns noticed"
       description: "Quick capture without prompts"
 
     - trigger: mood
@@ -140,13 +140,13 @@ agent:
       description: "Reflect on the past week"
 
     - trigger: insight
-      action: "Document this breakthrough in {agent_sidecar_folder}/journal-keeper-sidecar/breakthroughs.md with date and significance"
+      action: "Document this breakthrough in {project-root}/_bmad/_memory/journal-keeper-sidecar/breakthroughs.md with date and significance"
       description: "Record a meaningful insight"
 
     - trigger: read-back
-      action: "Load and share entries from {agent_sidecar_folder}/journal-keeper-sidecar/entries/ for requested timeframe, highlighting themes and growth"
+      action: "Load and share entries from {project-root}/_bmad/_memory/journal-keeper-sidecar/entries/ for requested timeframe, highlighting themes and growth"
       description: "Review past entries"
 
     - trigger: save
-      action: "Update {agent_sidecar_folder}/journal-keeper-sidecar/memories.md with today's session insights and emotional markers"
+      action: "Update {project-root}/_bmad/_memory/journal-keeper-sidecar/memories.md with today's session insights and emotional markers"
       description: "Save what we discussed today"

package/src/modules/bmb/reference/agents/module-examples/README.md

@@ -7,9 +7,10 @@ Reference examples for module-integrated agents.
 Module agents integrate with BMAD module workflows (BMM, CIS, BMB). They:
 
 - Orchestrate multi-step workflows
-- Use `{bmad_folder}` path variables
-- Have fixed professional personas (no install_config)
+- Use `_bmad` path variables
 - Reference module-specific configurations
+- Can be bundled into web bundlers with the other agents
+- Participate in party mode with the modules other agents
 
 ## Examples
 
@@ -46,5 +47,3 @@ When creating module agents:
 3. Rewrite persona for your domain
 4. Replace menu with actual available workflows
 5. Remove hypothetical workflow references
-
-See `/src/modules/bmb/docs/agents/module-agent-architecture.md` for complete guide.

package/src/modules/bmb/reference/agents/module-examples/security-engineer.agent.yaml

@@ -10,7 +10,7 @@
 
 agent:
   metadata:
-    id: "{*bmad_folder*}/bmm/agents/security-engineer.md"
+    id: "_bmad/bmm/agents/security-engineer.md"
     name: "Sam"
     title: "Security Engineer"
     icon: "🔐"
@@ -32,11 +32,11 @@ agent:
   menu:
     # NOTE: These workflows are hypothetical examples assuming add to a module called bmm - not implemented
     - trigger: threat-model
-      exec: "{project-root}/{*bmad_folder*}/bmm/workflows/threat-model/workflow.md"
+      exec: "{project-root}/_bmad/bmm/workflows/threat-model/workflow.md"
       description: "Create STRIDE threat model for architecture"
 
     - trigger: security-review
-      exec: "{project-root}/{*bmad_folder*}/bmm/workflows/security-review/workflow.md"
+      exec: "{project-root}/_bmad/bmm/workflows/security-review/workflow.md"
       description: "Review code/design for security issues"
 
     - trigger: owasp-check
@@ -44,10 +44,10 @@ agent:
       description: "Check against OWASP Top 10"
 
     - trigger: compliance
-      exec: "{project-root}/{*bmad_folder*}/bmm/workflows/compliance-check/workflow.md"
+      exec: "{project-root}/_bmad/bmm/workflows/compliance-check/workflow.md"
       description: "Verify compliance requirements (SOC2, GDPR, etc.)"
 
     # Core workflow that exists
     - trigger: party-mode
-      exec: "{project-root}/{*bmad_folder*}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
       description: "Multi-agent security discussion"

package/src/modules/bmb/reference/agents/module-examples/trend-analyst.agent.yaml

@@ -10,7 +10,7 @@
 
 agent:
   metadata:
-    id: "{*bmad_folder*}/cis/agents/trend-analyst.md"
+    id: "_bmad/cis/agents/trend-analyst.md"
     name: "Nova"
     title: "Trend Analyst"
     icon: "📈"
@@ -32,26 +32,26 @@ agent:
   menu:
     # NOTE: These workflows are hypothetical examples - not implemented
     - trigger: scan-trends
-      exec: "{project-root}/{*bmad_folder*}/cis/workflows/trend-scan/workflow.md"
+      exec: "{project-root}/_bmad/cis/workflows/trend-scan/workflow.md"
       description: "Scan for emerging trends in a domain"
 
     - trigger: analyze-trend
-      exec: "{project-root}/{*bmad_folder*}/cis/workflows/trend-analysis/workflow.md"
+      exec: "{project-root}/_bmad/cis/workflows/trend-analysis/workflow.md"
       description: "Deep dive on a specific trend"
 
     - trigger: opportunity-map
-      exec: "{project-root}/{*bmad_folder*}/cis/workflows/opportunity-mapping/workflow.md"
+      exec: "{project-root}/_bmad/cis/workflows/opportunity-mapping/workflow.md"
       description: "Map trend to strategic opportunities"
 
     - trigger: competitor-trends
-      exec: "{project-root}/{*bmad_folder*}/cis/tasks/competitor-trend-watch.xml"
+      exec: "{project-root}/_bmad/cis/tasks/competitor-trend-watch.xml"
       description: "Monitor competitor trend adoption"
 
     # Core workflows that exist
     - trigger: brainstorm
-      exec: "{project-root}/{*bmad_folder*}/core/workflows/brainstorming/workflow.md"
+      exec: "{project-root}/_bmad/core/workflows/brainstorming/workflow.md"
       description: "Brainstorm trend implications"
 
     - trigger: party-mode
-      exec: "{project-root}/{*bmad_folder*}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
       description: "Discuss trends with other agents"

package/src/modules/bmb/reference/agents/simple-examples/README.md

@@ -127,7 +127,7 @@ This personality is maintained across ALL commands through the persona definitio
 ```yaml
 agent:
   metadata:
-    id: .bmad/agents/{agent-name}/{agent-name}.md  # Build path
+    id: _bmad/agents/{agent-name}/{agent-name}.md  # Build path
     name: "Display Name"
     title: "Professional Title"
     icon: "🎭"

package/src/modules/bmb/reference/agents/simple-examples/commit-poet.agent.yaml

@@ -1,6 +1,6 @@
 agent:
   metadata:
-    id: .bmad/agents/commit-poet/commit-poet.md
+    id: _bmad/agents/commit-poet/commit-poet.md
     name: "Inkwell Von Comitizen"
     title: "Commit Message Artisan"
     icon: "📜"

package/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md

@@ -3,7 +3,7 @@ name: 'step-01-init'
 description: 'Initialize the nutrition plan workflow by detecting continuation state and creating output document'
 
 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition'
+workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-01-init.md'

package/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md

@@ -3,7 +3,7 @@ name: 'step-01b-continue'
 description: 'Handle workflow continuation from previous session'
 
 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition'
+workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-01b-continue.md'

package/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md

@@ -3,7 +3,7 @@ name: 'step-02-profile'
 description: 'Gather comprehensive user profile information through collaborative conversation'
 
 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition'
+workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
 
 # File References (all use {variable} format in file)
 thisStepFile: '{workflow_path}/steps/step-02-profile.md'
@@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/{bmad_folder}/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
 profileTemplate: '{workflow_path}/templates/profile-section.md'

package/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md

@@ -3,7 +3,7 @@ name: 'step-03-assessment'
 description: 'Analyze nutritional requirements, identify restrictions, and calculate target macros'
 
 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition'
+workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-03-assessment.md'
@@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/{bmad_folder}/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'
 
 # Data References
 dietaryRestrictionsDB: '{workflow_path}/data/dietary-restrictions.csv'