Merge 0f06ef724b into 26e47562dd

- Update changelog with recent changes
- Version bump to 6.0.0-alpha.16
- Document temporary custom content installation disable
- Document BMB workflow path fixes and package updates

CHANGELOG.md

@@ -1,5 +1,36 @@
 # Changelog
 
+## [6.0.0-alpha.16]
+
+**Release: December 10, 2025**
+
+### 🔧 Temporary Changes & Fixes
+
+**Installation Improvements:**
+
+- **Temporary Custom Content Installation Disable**: Custom content installation temporarily disabled to improve stability
+- **BMB Workflow Path Fixes**: Fixed numerous path references in BMB workflows to ensure proper step file resolution
+- **Package Updates**: Updated dependencies for improved security and performance
+
+**Path Resolution Improvements:**
+
+- **BMB Agent Builder Fixes**: Corrected path references in step files and documentation
+- **Workflow Path Standardization**: Ensured consistent path handling across all BMB workflows
+- **Documentation References**: Updated internal documentation links and references
+
+**Cleanup Changes:**
+
+- **Example Modules Removal**: Temporarily removed example modules to prevent accidental installation
+- **Hardcoded Path Cleanup**: Continued removal of hardcoded `.bmad` folder references from demo content
+- **Memory Management**: Improved sidecar file handling for custom modules
+
+### 📊 Statistics
+
+- **336 files changed** with path fixes and improvements
+- **4 commits** since alpha.15
+
+---
+
 ## [6.0.0-alpha.15]
 
 **Release: December 7, 2025**
@@ -145,7 +176,7 @@
 - Fixed version reading from package.json instead of hardcoded fallback
 - Removed hardcoded years from WebSearch queries
 - Removed broken build caching mechanism
-- Fixed hardcoded 'bmad' prefix from files-manifest.csv paths
+- Fixed hardcoded '.bmad' prefix from files-manifest.csv paths
 - Enhanced TTS injection summary with tracking and documentation
 - Fixed CI nvmrc configuration issues
 

docs/agent-customization-guide.md

@@ -9,7 +9,7 @@ Customize BMad agents without modifying core files. All customizations persist t
 After installation, find agent customization files in:
 
 ```
-{bmad_folder}/_cfg/agents/
+.bmad/_cfg/agents/
 ├── core-bmad-master.customize.yaml
 ├── bmm-dev.customize.yaml
 ├── bmm-pm.customize.yaml
@@ -119,7 +119,7 @@ prompts:
 **Example 1: Customize Developer Agent for TDD**
 
 ```yaml
-# {bmad_folder}/_cfg/agents/bmm-dev.customize.yaml
+# .bmad/_cfg/agents/bmm-dev.customize.yaml
 agent:
   metadata:
     name: 'TDD Developer'
@@ -135,20 +135,20 @@ critical_actions:
 **Example 2: Add Custom Deployment Workflow**
 
 ```yaml
-# {bmad_folder}/_cfg/agents/bmm-dev.customize.yaml
+# .bmad/_cfg/agents/bmm-dev.customize.yaml
 menu:
   - trigger: deploy-staging
-    workflow: '{project-root}/{bmad_folder}/deploy-staging.yaml'
+    workflow: '{project-root}/.bmad/deploy-staging.yaml'
     description: Deploy to staging environment
   - trigger: deploy-prod
-    workflow: '{project-root}/{bmad_folder}/deploy-prod.yaml'
+    workflow: '{project-root}/.bmad/deploy-prod.yaml'
     description: Deploy to production (with approval)
 ```
 
 **Example 3: Multilingual Product Manager**
 
 ```yaml
-# {bmad_folder}/_cfg/agents/bmm-pm.customize.yaml
+# .bmad/_cfg/agents/bmm-pm.customize.yaml
 persona:
   role: 'Bilingual Product Manager'
   identity: 'Expert in US and LATAM markets'
@@ -174,7 +174,7 @@ memories:
 
 **Module-Level (Recommended):**
 
-- Customize agents per-project in `{bmad_folder}/_cfg/agents/`
+- Customize agents per-project in `.bmad/_cfg/agents/`
 - Different projects can have different agent behaviors
 
 **Global Config (Coming Soon):**

docs/ide-info/crush.md

@@ -7,7 +7,7 @@ BMAD agents are installed as commands in `.crush/commands/bmad/`.
 ### How to Use
 
 1. **Open Command Palette**: Use Crush command interface
-2. **Navigate**: Browse to `{bmad_folder}/{module}/agents/`
+2. **Navigate**: Browse to `.bmad/{module}/agents/`
 3. **Select Agent**: Choose the agent command
 4. **Execute**: Run to activate agent persona
 

docs/ide-info/cursor.md

@@ -6,20 +6,20 @@ BMAD agents are installed in `.cursor/rules/bmad/` as MDC rules.
 
 ### How to Use
 
-1. **Reference in Chat**: Use `@{bmad_folder}/{module}/agents/{agent-name}`
-2. **Include Entire Module**: Use `@{bmad_folder}/{module}`
-3. **Reference Index**: Use `@{bmad_folder}/index` for all available agents
+1. **Reference in Chat**: Use `@.bmad/{module}/agents/{agent-name}`
+2. **Include Entire Module**: Use `@.bmad/{module}`
+3. **Reference Index**: Use `@.bmad/index` for all available agents
 
 ### Examples
 
 ```
-@{bmad_folder}/core/agents/dev - Activate dev agent
-@{bmad_folder}/bmm/agents/architect - Activate architect agent
-@{bmad_folder}/core - Include all core agents/tasks
+@.bmad/core/agents/dev - Activate dev agent
+@.bmad/bmm/agents/architect - Activate architect agent
+@.bmad/core - Include all core agents/tasks
 ```
 
 ### Notes
 
 - Rules are Manual type - only loaded when explicitly referenced
 - No automatic context pollution
-- Can combine multiple agents: `@{bmad_folder}/core/agents/dev @{bmad_folder}/core/agents/test`
+- Can combine multiple agents: `@.bmad/core/agents/dev @.bmad/core/agents/test`

docs/ide-info/iflow.md

@@ -7,7 +7,7 @@ BMAD agents are installed as commands in `.iflow/commands/bmad/`.
 ### How to Use
 
 1. **Access Commands**: Use iFlow command interface
-2. **Navigate**: Browse to `{bmad_folder}/agents/` or `{bmad_folder}/tasks/`
+2. **Navigate**: Browse to `.bmad/agents/` or `.bmad/tasks/`
 3. **Select**: Choose the agent or task command
 4. **Execute**: Run to activate
 
@@ -22,8 +22,8 @@ BMAD agents are installed as commands in `.iflow/commands/bmad/`.
 ### Examples
 
 ```
-/{bmad_folder}/agents/core-dev - Activate dev agent
-/{bmad_folder}/tasks/core-setup - Execute setup task
+/.bmad/agents/core-dev - Activate dev agent
+/.bmad/tasks/core-setup - Execute setup task
 ```
 
 ### Notes

docs/ide-info/opencode.md

@@ -14,7 +14,7 @@ BMAD agents are installed as OpenCode agents in `.opencode/agent/BMAD/{module_na
 
 ```
 /agents - to see a list of agents and switch between them
-/{bmad_folder}/bmm/workflows/workflow-init - Activate the workflow-init command
+/.bmad/bmm/workflows/workflow-init - Activate the workflow-init command
 ```
 
 ### Notes

docs/installers-bundlers/ide-injections.md

@@ -158,7 +158,7 @@ src/modules/bmm/
 
 ```yaml
 injections:
-  - file: '{bmad_folder}/bmm/agents/pm.md'
+  - file: '.bmad/bmm/agents/pm.md'
     point: 'pm-agent-instructions'
     requires: 'any' # Injected if ANY subagent is selected
     content: |
@@ -166,7 +166,7 @@ injections:
         <i>Use 'market-researcher' subagent for analysis</i>
       </llm>
 
-  - file: '{bmad_folder}/bmm/templates/prd.md'
+  - file: '.bmad/bmm/templates/prd.md'
     point: 'prd-goals-context-delegation'
     requires: 'market-researcher' # Only if this specific subagent selected
     content: |

docs/installers-bundlers/installers-modules-platforms-reference.md

@@ -19,7 +19,7 @@ BMad Core is a modular AI agent framework with intelligent installation, platfor
 
 - **Modular Design**: Core + optional modules (BMB, BMM, CIS)
 - **Smart Installation**: Interactive configuration with dependency resolution
-- **Clean Architecture**: Centralized `{bmad_folder}` directory add to project, no source pollution with multiple folders added
+- **Clean Architecture**: Centralized `.bmad` directory add to project, no source pollution with multiple folders added
 
 ## Architecture
 
@@ -27,7 +27,7 @@ BMad Core is a modular AI agent framework with intelligent installation, platfor
 
 ```
 project-root/
-├── {bmad_folder}/             # Centralized installation
+├── .bmad/             # Centralized installation
 │   ├── _cfg/                  # Configuration
 │   │   ├── agents/            # Agent configs
 │   │   └── agent-manifest.csv # Agent manifest
@@ -185,7 +185,7 @@ Cline, Roo, Rovo Dev,Auggie, GitHub Copilot, Codex, Gemini, Qwen, Trae, Kilo, Cr
 
    ```yaml
    injections:
-     - file: '{bmad_folder}/bmm/agents/pm.md'
+     - file: '.bmad/bmm/agents/pm.md'
        point: 'pm-agent-instructions'
        content: |
          <i>Platform-specific instruction</i>
@@ -271,14 +271,14 @@ Generated in: `bmad/_cfg/agents/{module}-{agent}.md`
 
 ### Common Issues
 
-| Issue                   | Solution                                     |
-| ----------------------- | -------------------------------------------- |
-| Existing installation   | Use `bmad update` or remove `{bmad_folder}/` |
-| Module not found        | Check `src/modules/` exists                  |
-| Config not applied      | Verify `{bmad_folder}/{module}/config.yaml`  |
-| Missing config.yaml     | Fixed: All modules now get configs           |
-| Agent unavailable       | Check for `localskip="true"`                 |
-| module-installer copied | Fixed: Now excluded from copy                |
+| Issue                   | Solution                             |
+| ----------------------- | ------------------------------------ |
+| Existing installation   | Use `bmad update` or remove `.bmad/` |
+| Module not found        | Check `src/modules/` exists          |
+| Config not applied      | Verify `.bmad/{module}/config.yaml`  |
+| Missing config.yaml     | Fixed: All modules now get configs   |
+| Agent unavailable       | Check for `localskip="true"`         |
+| module-installer copied | Fixed: Now excluded from copy        |
 
 ### Debug Commands
 
@@ -290,19 +290,19 @@ bmad status -v      # Detailed status
 ### Best Practices
 
 1. Run from project root
-2. Backup `{bmad_folder}/_cfg/` before updates
+2. Backup `.bmad/_cfg/` before updates
 3. Use interactive mode for guidance
 4. Review generated configs post-install
 
 ## Migration from v4
 
-| v4                  | v6                           |
-| ------------------- | ---------------------------- |
-| Scattered files     | Centralized `{bmad_folder}/` |
-| Monolithic          | Modular                      |
-| Manual config       | Interactive setup            |
-| Limited IDE support | 15+ platforms                |
-| Source modification | Clean injection              |
+| v4                  | v6                   |
+| ------------------- | -------------------- |
+| Scattered files     | Centralized `.bmad/` |
+| Monolithic          | Modular              |
+| Manual config       | Interactive setup    |
+| Limited IDE support | 15+ platforms        |
+| Source modification | Clean injection      |
 
 ## Technical Notes
 
@@ -327,8 +327,8 @@ Agents can specify both `workflow` (source location) and `workflow-install` (des
 ```yaml
 menu:
   - trigger: create-story
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story/workflow.yaml'
-    workflow-install: '{project-root}/{bmad_folder}/bmgd/workflows/4-production/create-story/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/4-implementation/create-story/workflow.yaml'
+    workflow-install: '{project-root}/.bmad/bmgd/workflows/4-production/create-story/workflow.yaml'
     description: 'Create a game feature story'
 ```
 
@@ -348,10 +348,10 @@ menu:
 
    ```yaml
    # Source workflow (in bmm):
-   config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+   config_source: "{project-root}/.bmad/bmm/config.yaml"
 
    # Vendored workflow (in bmgd):
-   config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
+   config_source: "{project-root}/.bmad/bmgd/config.yaml"
    ```
 
 **Result**: Modules become completely standalone with their own copies of needed workflows, configured for their specific use case.

docs/v4-to-v6-upgrade.md

@@ -63,7 +63,7 @@ your-project/
 
 ```
 your-project/
-└── {bmad_folder}/       # Single installation folder, default .bmad
+└── .bmad/       # Single installation folder, default .bmad
     ├── core/            # Real core framework (applies to all modules)
     ├── bmm/             # BMad Method (software/game dev)
     ├── bmb/             # BMad Builder (create agents/workflows)
@@ -75,8 +75,8 @@ your-project/
 ### Key Concept Changes
 
 - **v4 `.bmad-core`**: Was actually the BMad Method
-- **v6 `{bmad_folder}/core/`**: Is the real universal core framework
-- **v6 `{bmad_folder}/bmm/`**: Is the BMad Method module
+- **v6 `.bmad/core/`**: Is the real universal core framework
+- **v6 `.bmad/bmm/`**: Is the BMad Method module
 - **Module identification**: All modules now have a `config.yaml` file
 
 ---
@@ -114,11 +114,11 @@ In v4, you may have modified agent files directly in `.bmad-*` folders.
 
 ### v6 Agent Customization
 
-**All customizations** now go in `{bmad_folder}/_cfg/agents/` using customize files:
+**All customizations** now go in `.bmad/_cfg/agents/` using customize files:
 
 **Example: Renaming an agent and changing communication style**
 
-File: `{bmad_folder}/_cfg/agents/bmm-pm.customize.yaml`
+File: `.bmad/_cfg/agents/bmm-pm.customize.yaml`
 
 ```yaml
 # Customize the PM agent
@@ -133,8 +133,8 @@ persona:
 
 **How it works:**
 
-- Base agent: `{bmad_folder}/bmm/agents/pm.md`
-- Customization: `{bmad_folder}/_cfg/agents/bmm-pm.customize.yaml`
+- Base agent: `.bmad/bmm/agents/pm.md`
+- Customization: `.bmad/_cfg/agents/bmm-pm.customize.yaml`
 - Result: Agent uses your custom name and style, but updates don't overwrite your changes
 
 ---
@@ -212,9 +212,9 @@ Since you are migrating an existing project from v4, it's most likely **Level 3
 ## Post-Migration Checklist
 
 - [ ] v4 folders backed up to `v4-backup/`
-- [ ] v6 installed to `{bmad_folder}/` folder
+- [ ] v6 installed to `.bmad/` folder
 - [ ] `workflow-init` run with correct project level selected
-- [ ] Agent customizations migrated to `{bmad_folder}/_cfg/agents/` if needed
+- [ ] Agent customizations migrated to `.bmad/_cfg/agents/` if needed
 - [ ] IDE integration working (test by listing agents)
 - [ ] For active development: `sprint-planning` workflow executed
 
@@ -224,4 +224,4 @@ Since you are migrating an existing project from v4, it's most likely **Level 3
 
 - **Discord**: [Join the BMad Community](https://discord.gg/gk8jAdXWmj)
 - **Issues**: [GitHub Issue Tracker](https://github.com/bmad-code-org/BMAD-METHOD/issues)
-- **Docs**: Check `{bmad_folder}/docs/` in your installation for IDE-specific instructions
+- **Docs**: Check `.bmad/docs/` in your installation for IDE-specific instructions

docs/web-bundles-gemini-gpt-guide.md

@@ -336,7 +336,7 @@ Agents adapt their menus based on project phase and available workflows.
 
 Customize agents using the [Agent Customization Guide](./agent-customization-guide.md):
 
-1. Edit `{bmad_folder}/_cfg/agents/<agent>.customize.yaml`
+1. Edit `.bmad/_cfg/agents/<agent>.customize.yaml`
 2. Rebuild: `npx bmad-method build <agent-name>`
 3. Generate bundles: `npm run bundle`
 

package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "bmad-method",
-  "version": "6.0.0-alpha.13",
+  "version": "6.0.0-alpha.15",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "bmad-method",
-      "version": "6.0.0-alpha.13",
+      "version": "6.0.0-alpha.15",
       "license": "MIT",
       "dependencies": {
         "@kayvan/markdown-tree-parser": "^1.6.1",

package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.0.0-alpha.15",
+  "version": "6.0.0-alpha.16",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",

src/core/agents/bmad-master.agent.yaml

@@ -3,7 +3,7 @@
 
 agent:
   metadata:
-    id: "{bmad_folder}/core/agents/bmad-master.md"
+    id: ".bmad/core/agents/bmad-master.md"
     name: "BMad Master"
     title: "BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator"
     icon: "🧙"
@@ -17,22 +17,22 @@ agent:
 
   # Agent-specific critical actions
   critical_actions:
-    - "Load into memory {project-root}/{bmad_folder}/core/config.yaml and set variable project_name, output_folder, user_name, communication_language"
+    - "Load into memory {project-root}/.bmad/core/config.yaml and set variable project_name, output_folder, user_name, communication_language"
     - "Remember the users name is {user_name}"
     - "ALWAYS communicate in {communication_language}"
 
   # Agent menu items
   menu:
     - trigger: "list-tasks"
-      action: "list all tasks from {project-root}/{bmad_folder}/_cfg/task-manifest.csv"
+      action: "list all tasks from {project-root}/.bmad/_cfg/task-manifest.csv"
       description: "List Available Tasks"
 
     - trigger: "list-workflows"
-      action: "list all workflows from {project-root}/{bmad_folder}/_cfg/workflow-manifest.csv"
+      action: "list all workflows from {project-root}/.bmad/_cfg/workflow-manifest.csv"
       description: "List Workflows"
 
     - 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: "Group chat with all agents"
 
   # Empty prompts section (no custom prompts for this agent)

src/core/agents/bmad-web-orchestrator.agent.xml

@@ -1,7 +1,7 @@
-<agent id="{bmad_folder}/core/agents/bmad-orchestrator.md" name="BMad Orchestrator" title="BMad Web Orchestrator" icon="🎭" localskip="true">
+<agent id=".bmad/core/agents/bmad-orchestrator.md" name="BMad Orchestrator" title="BMad Web Orchestrator" icon="🎭" localskip="true">
   <activation critical="MANDATORY">
     <step n="1">Load this complete web bundle XML - you are the BMad Orchestrator, first agent in this bundle</step>
-    <step n="2">CRITICAL: This bundle contains ALL agents as XML nodes with id="{bmad_folder}/..." and ALL workflows/tasks as nodes findable
+    <step n="2">CRITICAL: This bundle contains ALL agents as XML nodes with id=".bmad/..." and ALL workflows/tasks as nodes findable
       by type
       and id</step>
     <step n="3">Greet user as BMad Orchestrator and display numbered list of ALL menu items from menu section below</step>
@@ -16,7 +16,7 @@
         <handler type="workflow">
           When menu item has: workflow="workflow-id"
           1. Find workflow node by id in this bundle (e.g., &lt;workflow id="workflow-id"&gt;)
-          2. CRITICAL: Always LOAD {bmad_folder}/core/tasks/workflow.xml if referenced
+          2. CRITICAL: Always LOAD .bmad/core/tasks/workflow.xml if referenced
           3. Execute the workflow content precisely following all steps
           4. Save outputs after completing EACH workflow step (never batch)
           5. If workflow id is "todo", inform user it hasn't been implemented yet
@@ -49,7 +49,7 @@
 
         <handler type="validate-workflow">
           When menu item has: validate-workflow="workflow-id"
-          1. MUST LOAD {bmad_folder}/core/tasks/validate-workflow.xml
+          1. MUST LOAD .bmad/core/tasks/validate-workflow.xml
           2. Execute all validation instructions from that file
           3. Check workflow's validation property for schema
           4. Identify file to validate or ask user to specify
@@ -105,9 +105,9 @@
     <item cmd="*help">Show numbered command list</item>
     <item cmd="*list-agents">List all available agents with their capabilities</item>
     <item cmd="*agents [agent-name]">Transform into a specific agent</item>
-    <item cmd="*party-mode" exec="{bmad_folder}/core/workflows/party-mode/workflow.md">Enter group chat with all agents
+    <item cmd="*party-mode" exec=".bmad/core/workflows/party-mode/workflow.md">Enter group chat with all agents
       simultaneously</item>
-    <item cmd="*advanced-elicitation" task="{bmad_folder}/core/tasks/advanced-elicitation.xml">Push agent to perform advanced elicitation</item>
+    <item cmd="*advanced-elicitation" task=".bmad/core/tasks/advanced-elicitation.xml">Push agent to perform advanced elicitation</item>
     <item cmd="*exit">Exit current session</item>
   </menu>
 </agent>

src/core/module.yaml

@@ -1,13 +1,6 @@
-# BMAD™ Core Configuration
 header: "BMAD™ Core Configuration"
 subheader: "Configure the core settings for your BMAD™ installation.\nThese settings will be used across all modules and agents."
 
-bmad_folder:
-  prompt: "What is the root folder for BMAD installation? (Recommended: .bmad)"
-  default: ".bmad"
-  result: "{value}"
-  regex: "^[a-zA-Z0-9._-]{1,20}$"
-
 user_name:
   prompt: "What shall the agents call you?"
   default: "BMad"

src/core/resources/excalidraw/README.md

@@ -72,8 +72,8 @@ Provides the **HOW** (universal knowledge) while agents provide the **WHAT** (do
 
 ```yaml
 # workflows/diagrams/create-flowchart/workflow.yaml
-helpers: '{project-root}/{bmad_folder}/core/resources/excalidraw/excalidraw-helpers.md'
-json_validation: '{project-root}/{bmad_folder}/core/resources/excalidraw/validate-json-instructions.md'
+helpers: '{project-root}/.bmad/core/resources/excalidraw/excalidraw-helpers.md'
+json_validation: '{project-root}/.bmad/core/resources/excalidraw/validate-json-instructions.md'
 ```
 
 **Domain-specific additions:**
@@ -99,8 +99,8 @@ flowchart:
 
 ```yaml
 # workflows/create-visual-metaphor/workflow.yaml
-helpers: '{project-root}/{bmad_folder}/core/resources/excalidraw/excalidraw-helpers.md'
-json_validation: '{project-root}/{bmad_folder}/core/resources/excalidraw/validate-json-instructions.md'
+helpers: '{project-root}/.bmad/core/resources/excalidraw/excalidraw-helpers.md'
+json_validation: '{project-root}/.bmad/core/resources/excalidraw/validate-json-instructions.md'
 ```
 
 **Domain-specific additions:**

src/core/tasks/advanced-elicitation.xml

@@ -1,6 +1,6 @@
-<task id="{bmad_folder}/core/tasks/advanced-elicitation.xml" name="Advanced Elicitation" standalone="true"
-  methods="{project-root}/{bmad_folder}/core/tasks/advanced-elicitation-methods.csv"
-  agent-party="{project-root}/{bmad_folder}/_cfg/agent-manifest.csv">
+<task id=".bmad/core/tasks/advanced-elicitation.xml" name="Advanced Elicitation" standalone="true"
+  methods="{project-root}/.bmad/core/tasks/advanced-elicitation-methods.csv"
+  agent-party="{project-root}/.bmad/_cfg/agent-manifest.csv">
   <llm critical="true">
     <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
     <i>DO NOT skip steps or change the sequence</i>

src/core/tasks/index-docs.xml

@@ -1,4 +1,4 @@
-<task id="{bmad_folder}/core/tasks/index-docs" name="Index Docs"
+<task id=".bmad/core/tasks/index-docs" name="Index Docs"
   description="Generates or updates an index.md of all documents in the specified directory" webskip="true" standalone="true">
   <llm critical="true">
     <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>

src/core/tasks/validate-workflow.xml

@@ -1,4 +1,4 @@
-<task id="{bmad_folder}/core/tasks/validate-workflow.xml" name="Validate Workflow Output">
+<task id=".bmad/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>

src/core/tasks/workflow.xml

@@ -1,4 +1,4 @@
-<task id="{bmad_folder}/core/tasks/workflow.xml" name="Execute Workflow">
+<task id=".bmad/core/tasks/workflow.xml" name="Execute Workflow">
   <objective>Execute given workflow by loading its configuration, following instructions, and producing output</objective>
 
   <llm critical="true">
@@ -74,14 +74,14 @@
           <action>Display generated content</action>
           <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>
+              <action>Start the advanced elicitation workflow {project-root}/.bmad/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>
+              <action>Start the party-mode workflow {project-root}/.bmad/core/workflows/party-mode/workflow.yaml</action>
             </if>
             <if
               response="y">
@@ -225,7 +225,7 @@
     <critical-rules>
       • This is the complete workflow execution engine
       • You MUST Follow instructions exactly as written
-      • The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml
+      • The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml
       • You MUST have already loaded and processed: {installed_path}/workflow.yaml
       • This workflow uses INTENT-DRIVEN PLANNING - adapt organically to product type and context
       • YOU ARE FACILITATING A CONVERSATION With a user to produce a final document step by step. The whole process is meant to be

src/core/tools/shard-doc.xml

@@ -1,4 +1,4 @@
-<tool id="{bmad_folder}/core/tasks/shard-doc" name="Shard Document"
+<tool id=".bmad/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>

src/core/workflows/brainstorming/workflow.md

@@ -28,7 +28,7 @@ This uses **micro-file architecture** for disciplined execution:
 
 ### Configuration Loading
 
-Load config from `{project-root}/{bmad_folder}/core/config.yaml` and resolve:
+Load config from `{project-root}/.bmad/core/config.yaml` and resolve:
 
 - `project_name`, `output_folder`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
@@ -36,7 +36,7 @@ Load config from `{project-root}/{bmad_folder}/core/config.yaml` and resolve:
 
 ### Paths
 
-- `installed_path` = `{project-root}/{bmad_folder}/core/workflows/brainstorming`
+- `installed_path` = `{project-root}/.bmad/core/workflows/brainstorming`
 - `template_path` = `{installed_path}/template.md`
 - `brain_techniques_path` = `{installed_path}/brain-methods.csv`
 - `default_output_file` = `{output_folder}/analysis/brainstorming-session-{{date}}.md`

src/core/workflows/party-mode/steps/step-01-agent-loading.md

@@ -18,7 +18,7 @@
 
 ## CONTEXT BOUNDARIES:
 
-- Agent manifest CSV is available at `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
+- Agent manifest CSV is available at `{project-root}/.bmad/_cfg/agent-manifest.csv`
 - User configuration from config.yaml is loaded and resolved
 - Party mode is standalone interactive workflow
 - All agent data is available for conversation orchestration
@@ -37,7 +37,7 @@ Begin agent loading process:
 
 **Agent Manifest Loading:**"
 
-Load and parse the agent manifest CSV from `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
+Load and parse the agent manifest CSV from `{project-root}/.bmad/_cfg/agent-manifest.csv`
 
 ### 2. Extract Agent Data
 

src/core/workflows/party-mode/workflow.md

@@ -27,17 +27,17 @@ This uses **micro-file architecture** with **sequential conversation orchestrati
 
 ### Configuration Loading
 
-Load config from `{project-root}/{bmad_folder}/core/config.yaml` and resolve:
+Load config from `{project-root}/.bmad/core/config.yaml` and resolve:
 
 - `project_name`, `output_folder`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
 - `date` as a system-generated value
-- Agent manifest path: `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
+- Agent manifest path: `{project-root}/.bmad/_cfg/agent-manifest.csv`
 
 ### Paths
 
-- `installed_path` = `{project-root}/{bmad_folder}/core/workflows/party-mode`
-- `agent_manifest_path` = `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
+- `installed_path` = `{project-root}/.bmad/core/workflows/party-mode`
+- `agent_manifest_path` = `{project-root}/.bmad/_cfg/agent-manifest.csv`
 - `standalone_mode` = `true` (party mode is an interactive workflow)
 
 ---

src/modules/bmb/README.md

@@ -24,13 +24,13 @@ Specialized tools and workflows for creating, customizing, and extending BMad co
 
 **Active Workflows** (Step-File Architecture)
 
-- Location: `src/modules/bmb/workflows/`
+- Location: `bmb/workflows/create-agent/`
 - 5 core workflows with 41 step files total
 - Template-based execution with JIT loading
 
 **Legacy Workflows** (Being Migrated)
 
-- Location: `src/modules/bmb/workflows-legacy/`
+- Location: `bmb/workflows/create-agent-legacy/`
 - Module-specific workflows pending conversion to step-file architecture
 
 ### 📚 Documentation

src/modules/bmb/agents/bmad-builder.agent.yaml

@@ -4,7 +4,7 @@
 agent:
   webskip: true
   metadata:
-    id: "{bmad_folder}/bmb/agents/bmad-builder.md"
+    id: ".bmad/bmb/agents/bmad-builder.md"
     name: BMad Builder
     title: BMad Builder
     icon: 🧙
@@ -24,26 +24,26 @@ agent:
 
   discussion: true
   conversational_knowledge:
-    - agents: "{project-root}/{bmad_folder}/bmb/docs/agents/kb.csv"
-    - workflows: "{project-root}/{bmad_folder}/bmb/docs/workflows/kb.csv"
-    - modules: "{project-root}/{bmad_folder}/bmb/docs/modules/kb.csv"
+    - agents: "{project-root}/.bmad/bmb/docs/agents/kb.csv"
+    - workflows: "{project-root}/.bmad/bmb/docs/workflows/kb.csv"
+    - modules: "{project-root}/.bmad/bmb/docs/modules/kb.csv"
 
   menu:
     - multi: "[CA] Create, [EA] Edit, or [VA] Validate with Compliance CheckBMAD agents with best practices"
       triggers:
         - create-agent:
             - input: CA or fuzzy match create agent
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/create-agent/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/create-agent/workflow.md"
             - data: null
             - type: exec
         - edit-agent:
             - input: EA or fuzzy match edit agent
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/edit-agent/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/edit-agent/workflow.md"
             - data: null
             - type: exec
         - run-agent-compliance-check:
             - input: VA or fuzzy match validate agent
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/agent-compliance-check/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/agent-compliance-check/workflow.md"
             - data: null
             - type: exec
 
@@ -51,17 +51,17 @@ agent:
       triggers:
         - create-workflow:
             - input: CW or fuzzy match create workflow
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/create-workflow/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/create-workflow/workflow.md"
             - data: null
             - type: exec
         - edit-workflow:
             - input: EW or fuzzy match edit workflow
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/edit-workflow/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/edit-workflow/workflow.md"
             - data: null
             - type: exec
         - run-workflow-compliance-check:
             - input: VW or fuzzy match validate workflow
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/workflow-compliance-check/workflow.md"
             - data: null
             - type: exec
 
@@ -69,26 +69,26 @@ agent:
       triggers:
         - brainstorm-module:
             - input: BM or fuzzy match brainstorm module
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/brainstorm-module/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/brainstorm-module/workflow.md"
             - data: null
             - type: exec
         - product-brief-module:
             - input: PBM or fuzzy match product brief module
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/product-brief-module/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/product-brief-module/workflow.md"
             - data: null
             - type: exec
         - create-module:
             - input: CM or fuzzy match create module
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/create-module/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/create-module/workflow.md"
             - data: null
             - type: exec
         - edit-module:
             - input: EM or fuzzy match edit module
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/edit-module/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/edit-module/workflow.md"
             - data: null
             - type: exec
         - run-module-compliance-check:
             - input: VM or fuzzy match validate module
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/module-compliance-check/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/module-compliance-check/workflow.md"
             - data: null
             - type: exec

src/modules/bmb/docs/agents/agent-compilation.md

@@ -35,7 +35,7 @@ rex.agent.yaml           ← Persona name (users might rename to "Max")
 **Pattern:**
 
 - Filename: `{role-or-function}.agent.yaml` (kebab-case)
-- Metadata ID: `{bmad_folder}/{module}/agents/{role-or-function}.md`
+- Metadata ID: `.bmad/{module}/agents/{role-or-function}.md`
 - Persona Name: User-customizable in metadata or customize.yaml
 
 **Example:**
@@ -44,7 +44,7 @@ rex.agent.yaml           ← Persona name (users might rename to "Max")
 # File: presentation-master.agent.yaml
 agent:
   metadata:
-    id: '{bmad_folder}/cis/agents/presentation-master.md'
+    id: '.bmad/cis/agents/presentation-master.md'
     name: Caravaggio # ← Users can change this to "Pablo" or "Vince"
     title: Visual Communication & Presentation Expert
 ```

src/modules/bmb/docs/agents/agent-menu-patterns.md

@@ -65,11 +65,11 @@ For module agents orchestrating multi-step processes.
 ```yaml
 menu:
   - trigger: create-prd
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/prd/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/prd/workflow.yaml'
     description: 'Create Product Requirements Document'
 
   - trigger: brainstorm
-    workflow: '{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml'
+    workflow: '{project-root}/.bmad/core/workflows/brainstorming/workflow.yaml'
     description: 'Guided brainstorming session'
 
   # Placeholder for unimplemented workflows
@@ -92,11 +92,11 @@ For executing tasks directly.
 ```yaml
 menu:
   - trigger: validate
-    exec: '{project-root}/{bmad_folder}/core/tasks/validate-workflow.xml'
+    exec: '{project-root}/.bmad/core/tasks/validate-workflow.xml'
     description: 'Validate document structure'
 
   - trigger: advanced-elicitation
-    exec: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
+    exec: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
     description: 'Advanced elicitation techniques'
 ```
 
@@ -113,8 +113,8 @@ For document generation with templates.
 ```yaml
 menu:
   - trigger: create-brief
-    exec: '{project-root}/{bmad_folder}/core/tasks/create-doc.xml'
-    tmpl: '{project-root}/{bmad_folder}/bmm/templates/brief.md'
+    exec: '{project-root}/.bmad/core/tasks/create-doc.xml'
+    tmpl: '{project-root}/.bmad/bmm/templates/brief.md'
     description: 'Create a Product Brief'
 ```
 
@@ -131,8 +131,8 @@ Universal attribute for supplementary information.
 ```yaml
 menu:
   - trigger: team-standup
-    exec: '{project-root}/{bmad_folder}/bmm/tasks/standup.xml'
-    data: '{project-root}/{bmad_folder}/_cfg/agent-manifest.csv'
+    exec: '{project-root}/.bmad/bmm/tasks/standup.xml'
+    data: '{project-root}/.bmad/_cfg/agent-manifest.csv'
     description: 'Run team standup'
 
   - trigger: analyze-metrics
@@ -154,12 +154,12 @@ Control visibility based on deployment target:
 ```yaml
 menu:
   - trigger: git-flow
-    exec: '{project-root}/{bmad_folder}/bmm/tasks/git-flow.xml'
+    exec: '{project-root}/.bmad/bmm/tasks/git-flow.xml'
     description: 'Git workflow operations'
     ide-only: true # Only in IDE environments
 
   - trigger: advanced-elicitation
-    exec: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
+    exec: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
     description: 'Advanced elicitation'
     web-only: true # Only in web bundles
 ```
@@ -251,20 +251,20 @@ menu:
 menu:
   # Analysis Phase
   - trigger: brainstorm
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
     description: 'Brainstorm ideas'
 
   - trigger: research
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/research/workflow.yaml'
     description: 'Conduct research'
 
   # Planning Phase
   - trigger: prd
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/2-planning/prd/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/2-planning/prd/workflow.yaml'
     description: 'Create PRD'
 
   - trigger: architecture
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/2-planning/architecture/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/2-planning/architecture/workflow.yaml'
     description: 'Design architecture'
 ```
 
@@ -362,8 +362,8 @@ prompts:
 
 ```yaml
 # GOOD - Portable paths
-workflow: "{project-root}/{bmad_folder}/bmm/workflows/prd/workflow.yaml"
-exec: "{project-root}/{bmad_folder}/core/tasks/validate.xml"
+workflow: "{project-root}/.bmad/bmm/workflows/prd/workflow.yaml"
+exec: "{project-root}/.bmad/core/tasks/validate.xml"
 data: "{project-root}/_data/metrics.csv"
 
 # BAD - Hardcoded paths
@@ -374,7 +374,7 @@ exec: "../../../core/tasks/validate.xml"
 ### Available Variables
 
 - `{project-root}` - Project root directory
-- `{bmad_folder}` - BMAD installation folder
+- `.bmad` - BMAD installation folder
 - `{agent_sidecar_folder}` - Agent installation directory (Expert agents)
 - `{output_folder}` - Document output location
 - `{user_name}` - User's name from config
@@ -444,23 +444,23 @@ menu:
 ```yaml
 menu:
   - trigger: workflow-init
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/workflow-status/init/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/workflow-status/init/workflow.yaml'
     description: 'Initialize workflow path (START HERE)'
 
   - trigger: brainstorm
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
     description: 'Guided brainstorming'
 
   - trigger: prd
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/2-planning/prd/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/2-planning/prd/workflow.yaml'
     description: 'Create PRD'
 
   - trigger: architecture
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/2-planning/architecture/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/2-planning/architecture/workflow.yaml'
     description: 'Design architecture'
 
   - trigger: party-mode
-    workflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml'
+    workflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.yaml'
     description: 'Multi-agent discussion'
 ```
 

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

@@ -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:
 

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/`)
 

src/modules/bmb/docs/agents/module-agent-architecture.md

@@ -27,7 +27,7 @@ Compiles to:
 ```yaml
 agent:
   metadata:
-    id: '{*bmad_folder*}/{module-code}/agents/{agent-name}.md'
+    id: '.bmad/{module-code}/agents/{agent-name}.md'
     name: 'Persona Name'
     title: 'Professional Title'
     icon: 'emoji'
@@ -41,29 +41,29 @@ agent:
 
   menu:
     - trigger: workflow-action
-      workflow: '{project-root}/{*bmad_folder*}/{module-code}/workflows/{workflow-name}/workflow.yaml'
+      workflow: '{project-root}/.bmad/{module-code}/workflows/{workflow-name}/workflow.yaml'
       description: 'Execute module workflow'
 
     - trigger: another-workflow
-      workflow: '{project-root}/{*bmad_folder*}/core/workflows/{workflow-name}/workflow.yaml'
+      workflow: '{project-root}/.bmad/core/workflows/{workflow-name}/workflow.yaml'
       description: 'Execute core workflow'
 
     - trigger: task-action
-      exec: '{project-root}/{*bmad_folder*}/{module-code}/tasks/{task-name}.xml'
+      exec: '{project-root}/.bmad/{module-code}/tasks/{task-name}.xml'
       description: 'Execute module task'
 
     - trigger: cross-module
-      workflow: '{project-root}/{*bmad_folder*}/other-module/workflows/{workflow-name}/workflow.yaml'
+      workflow: '{project-root}/.bmad/other-module/workflows/{workflow-name}/workflow.yaml'
       description: 'Execute workflow from another module'
 
     - trigger: with-template
-      exec: '{project-root}/{*bmad_folder*}/core/tasks/create-doc.xml'
-      tmpl: '{project-root}/{*bmad_folder*}/{module-code}/templates/{template-name}.md'
+      exec: '{project-root}/.bmad/core/tasks/create-doc.xml'
+      tmpl: '{project-root}/.bmad/{module-code}/templates/{template-name}.md'
       description: 'Create document from template'
 
     - trigger: with-data
-      exec: '{project-root}/{*bmad_folder*}/{module-code}/tasks/{task-name}.xml'
-      data: '{project-root}/{*bmad_folder*}/_cfg/agent-manifest.csv'
+      exec: '{project-root}/.bmad/{module-code}/tasks/{task-name}.xml'
+      data: '{project-root}/.bmad/_cfg/agent-manifest.csv'
       description: 'Execute task with data file'
 ```
 
@@ -71,7 +71,7 @@ agent:
 
 ### Metadata
 
-- **id**: Path with `{*bmad_folder*}` variable (resolved at install time)
+- **id**: Path with `.bmad` variable (resolved at install time)
 - **name**: Agent persona name
 - **title**: Professional role
 - **icon**: Single emoji
@@ -101,7 +101,7 @@ persona:
 ```yaml
 menu:
   - trigger: create-prd
-    workflow: '{project-root}/{*bmad_folder*}/bmm/workflows/prd/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/prd/workflow.yaml'
     description: 'Create Product Requirements Document'
 ```
 
@@ -112,7 +112,7 @@ Invokes BMAD workflow engine to execute multi-step processes.
 ```yaml
 menu:
   - trigger: validate
-    exec: '{project-root}/{*bmad_folder*}/core/tasks/validate-workflow.xml'
+    exec: '{project-root}/.bmad/core/tasks/validate-workflow.xml'
     description: 'Validate document structure'
 ```
 
@@ -123,8 +123,8 @@ Executes single-operation tasks.
 ```yaml
 menu:
   - trigger: create-brief
-    exec: '{project-root}/{*bmad_folder*}/core/tasks/create-doc.xml'
-    tmpl: '{project-root}/{*bmad_folder*}/bmm/templates/brief.md'
+    exec: '{project-root}/.bmad/core/tasks/create-doc.xml'
+    tmpl: '{project-root}/.bmad/bmm/templates/brief.md'
     description: 'Create a Product Brief from template'
 ```
 
@@ -135,8 +135,8 @@ Combines task execution with template file.
 ```yaml
 menu:
   - trigger: team-standup
-    exec: '{project-root}/{*bmad_folder*}/bmm/tasks/standup.xml'
-    data: '{project-root}/{*bmad_folder*}/_cfg/agent-manifest.csv'
+    exec: '{project-root}/.bmad/bmm/tasks/standup.xml'
+    data: '{project-root}/.bmad/_cfg/agent-manifest.csv'
     description: 'Run team standup with agent roster'
 ```
 
@@ -160,12 +160,12 @@ Control visibility based on platform:
 ```yaml
 menu:
   - trigger: advanced-elicitation
-    exec: '{project-root}/{*bmad_folder*}/core/tasks/advanced-elicitation.xml'
+    exec: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
     description: 'Advanced elicitation techniques'
     web-only: true # Only shows in web bundle
 
   - trigger: git-operations
-    exec: '{project-root}/{*bmad_folder*}/bmm/tasks/git-flow.xml'
+    exec: '{project-root}/.bmad/bmm/tasks/git-flow.xml'
     description: 'Git workflow operations'
     ide-only: true # Only shows in IDE environments
 ```
@@ -175,7 +175,7 @@ menu:
 ### Core Variables
 
 - `{project-root}` - Root directory of installed project
-- `{*bmad_folder*}` - BMAD installation folder (usually `.bmad`)
+- `.bmad` - BMAD installation folder (usually `.bmad`)
 - `{user_name}` - User's name from module config
 - `{communication_language}` - Language preference
 - `{output_folder}` - Document output directory
@@ -186,7 +186,7 @@ menu:
 
 ```yaml
 # GOOD
-workflow: "{project-root}/{*bmad_folder*}/bmm/workflows/prd/workflow.yaml"
+workflow: "{project-root}/.bmad/bmm/workflows/prd/workflow.yaml"
 
 # BAD
 workflow: "/Users/john/project/.bmad/bmm/workflows/prd/workflow.yaml"
@@ -208,7 +208,7 @@ Module agents use the same injection process as simple agents:
 **Key difference:** Module agents load **module-specific config** instead of core config:
 
 ```xml
-<step n="2">Load and read {project-root}/{*bmad_folder*}/{module}/config.yaml...</step>
+<step n="2">Load and read {project-root}/.bmad/{module}/config.yaml...</step>
 ```
 
 ## Reference Examples
@@ -252,15 +252,15 @@ Agents load this at activation for consistent behavior.
 ```yaml
 menu:
   - trigger: init
-    workflow: '{project-root}/{*bmad_folder*}/bmm/workflows/workflow-init/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/workflow-init/workflow.yaml'
     description: 'Initialize workflow path (START HERE)'
 
   - trigger: status
-    workflow: '{project-root}/{*bmad_folder*}/bmm/workflows/workflow-status/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml'
     description: 'Check current workflow status'
 
   - trigger: next-step
-    workflow: '{project-root}/{*bmad_folder*}/bmm/workflows/next-step/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/next-step/workflow.yaml'
     description: 'Execute next workflow in sequence'
 ```
 
@@ -270,20 +270,20 @@ menu:
 menu:
   # Phase 1: Analysis
   - trigger: brainstorm
-    workflow: '{project-root}/{*bmad_folder*}/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
     description: 'Guided brainstorming session'
 
   - trigger: research
-    workflow: '{project-root}/{*bmad_folder*}/bmm/workflows/1-analysis/research/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/research/workflow.yaml'
     description: 'Market and technical research'
 
   # Phase 2: Planning
   - trigger: prd
-    workflow: '{project-root}/{*bmad_folder*}/bmm/workflows/2-planning/prd/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/2-planning/prd/workflow.yaml'
     description: 'Create PRD'
 
   - trigger: architecture
-    workflow: '{project-root}/{*bmad_folder*}/bmm/workflows/2-planning/architecture/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/2-planning/architecture/workflow.yaml'
     description: 'Design architecture'
 ```
 
@@ -292,24 +292,23 @@ menu:
 ```yaml
 menu:
   - trigger: party-mode
-    workflow: '{project-root}/{*bmad_folder*}/core/workflows/party-mode/workflow.yaml'
+    workflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.yaml'
     description: 'Bring all agents together'
 
   - trigger: brainstorm
-    workflow: '{project-root}/{*bmad_folder*}/cis/workflows/brainstorming/workflow.yaml'
+    workflow: '{project-root}/.bmad/cis/workflows/brainstorming/workflow.yaml'
     description: 'Use CIS brainstorming techniques'
 ```
 
 ## Best Practices
 
-1. **Use {_bmad_folder_} paths** - Portable across installations
-2. **Organize workflows by phase** - Clear progression for users
-3. **Include workflow-status** - Help users track progress
-4. **Reference module config** - Consistent behavior
-5. **No Handlebars templating** - Module agents are fixed personalities
-6. **Professional personas** - Match module purpose
-7. **Clear trigger names** - Self-documenting commands
-8. **Group related workflows** - Logical menu organization
+1. **Organize workflows by phase** - Clear progression for users
+2. **Include workflow-status** - Help users track progress
+3. **Reference module config** - Consistent behavior
+4. **No Handlebars templating** - Module agents are fixed personalities
+5. **Professional personas** - Match module purpose
+6. **Clear trigger names** - Self-documenting commands
+7. **Group related workflows** - Logical menu organization
 
 ## Common Patterns
 
@@ -318,7 +317,7 @@ menu:
 ```yaml
 menu:
   - trigger: start
-    workflow: '{project-root}/{*bmad_folder*}/{module}/workflows/init/workflow.yaml'
+    workflow: '{project-root}/.bmad/{module}/workflows/init/workflow.yaml'
     description: 'Start new project (BEGIN HERE)'
 ```
 
@@ -327,7 +326,7 @@ menu:
 ```yaml
 menu:
   - trigger: status
-    workflow: '{project-root}/{*bmad_folder*}/{module}/workflows/status/workflow.yaml'
+    workflow: '{project-root}/.bmad/{module}/workflows/status/workflow.yaml'
     description: 'Check workflow progress'
 ```
 
@@ -336,27 +335,27 @@ menu:
 ```yaml
 menu:
   - trigger: party
-    workflow: '{project-root}/{*bmad_folder*}/core/workflows/party-mode/workflow.yaml'
+    workflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.yaml'
     description: 'Multi-agent discussion'
 ```
 
 ## Module Agent vs Simple/Expert
 
-| Aspect        | Module Agent                       | Simple/Expert Agent              |
-| ------------- | ---------------------------------- | -------------------------------- |
-| Location      | `{*bmad_folder*}/{module}/agents/` | `{*bmad_folder*}/custom/agents/` |
-| Persona       | Fixed, professional                | Customizable via install_config  |
-| Handlebars    | No templating                      | Yes, extensive                   |
-| Menu actions  | Workflows, tasks, templates        | Prompts, inline actions          |
-| Configuration | Module config.yaml                 | Core config or none              |
-| Purpose       | Professional tooling               | Personal utilities               |
+| Aspect        | Module Agent                | Simple/Expert Agent             |
+| ------------- | --------------------------- | ------------------------------- |
+| Location      | `.bmad/{module}/agents/`    | `.bmad/custom/agents/`          |
+| Persona       | Fixed, professional         | Customizable via install_config |
+| Handlebars    | No templating               | Yes, extensive                  |
+| Menu actions  | Workflows, tasks, templates | Prompts, inline actions         |
+| Configuration | Module config.yaml          | Core config or none             |
+| Purpose       | Professional tooling        | Personal utilities              |
 
 ## Validation Checklist
 
 - [ ] Valid YAML syntax
 - [ ] Metadata includes `module: "{module-code}"`
-- [ ] id uses `{*bmad_folder*}/{module}/agents/{name}.md`
-- [ ] All workflow paths use `{project-root}/{*bmad_folder*}/` prefix
+- [ ] id uses `.bmad/{module}/agents/{name}.md`
+- [ ] All workflow paths use `{project-root}/.bmad/` prefix
 - [ ] No hardcoded paths
 - [ ] No duplicate triggers
 - [ ] Each menu item has description

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

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'

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

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)
 

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)
 

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

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)
 

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`

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`
 

src/modules/bmb/module.yaml

@@ -11,7 +11,6 @@ subheader: "Configure the settings for the BoMB Factory!\nThe agent, workflow an
 ## user_name
 ## communication_language
 ## output_folder
-## bmad_folder
 ## install_user_docs
 ## kb_install
 

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

@@ -7,7 +7,7 @@ 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
+- Use `.bmad` path variables
 - Have fixed professional personas (no install_config)
 - Reference module-specific configurations
 

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"

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"

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'

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'

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'

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'

src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md

@@ -3,7 +3,7 @@ name: 'step-04-strategy'
 description: 'Design a personalized meal strategy that meets nutritional needs and fits lifestyle'
 
 # 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-04-strategy.md'
@@ -13,8 +13,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
 recipeDatabase: '{workflow_path}/data/recipe-database.csv'
@@ -167,8 +167,8 @@ Display: **Select an Option:** [A] Meal Variety Optimization [P] Chef & Dietitia
 #### Menu Handling Logic:
 
 - HALT and AWAIT ANSWER
-- IF A: Execute `{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml`
-- IF P: Execute `{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md` with a chef and dietitian expert also as part of the party
+- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml`
+- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md` with a chef and dietitian expert also as part of the party
 - IF C: Save content to nutrition-plan.md, update frontmatter `stepsCompleted` to add 4 at the end of the array before loading next step, check cooking frequency:
   - IF cooking frequency > 2x/week: load, read entire file, then execute `{workflow_path}/step-05-shopping.md`
   - IF cooking frequency ≤ 2x/week: load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md`

src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md

@@ -3,7 +3,7 @@ name: 'step-05-shopping'
 description: 'Create a comprehensive shopping list that supports the meal strategy'
 
 # 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-05-shopping.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
 shoppingTemplate: '{workflow_path}/templates/shopping-section.md'
@@ -157,8 +157,8 @@ Display: **Select an Option:** [A] Budget Optimization Strategies [P] Shopping P
 #### Menu Handling Logic:
 
 - HALT and AWAIT ANSWER
-- IF A: Execute `{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml`
-- IF P: Execute `{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md`
+- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml`
+- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md`
 - IF C: Save content to nutrition-plan.md, update frontmatter `stepsCompleted` to add 5 at the end of the array before loading next step, then load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md`
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options)
 

src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md

@@ -3,7 +3,7 @@ name: 'step-06-prep-schedule'
 description: "Create a realistic meal prep schedule that fits the user's lifestyle"
 
 # 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-06-prep-schedule.md'
@@ -11,8 +11,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
 prepScheduleTemplate: '{workflow_path}/templates/prep-schedule-section.md'
@@ -178,8 +178,8 @@ Display: **Select an Option:** [A] Advanced Prep Techniques [P] Coach Perspectiv
 #### Menu Handling Logic:
 
 - HALT and AWAIT ANSWER
-- IF A: Execute `{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml`
-- IF P: Execute `{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md`
+- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml`
+- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md`
 - IF C: update frontmatter `stepsCompleted` to add 6 at the end of the array before loading next step, mark workflow complete, display final message
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
 

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

@@ -49,10 +49,10 @@ This uses **step-file architecture** for disciplined execution:
 
 ### 1. Configuration Loading
 
-Load and read full config from {project-root}/{bmad_folder}/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`
 
 ### 2. First Step EXECUTION
 
-Load, read the full file and then execute `{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md` to begin the workflow.
+Load, read the full file and then execute `{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md` to begin the workflow.

src/modules/bmb/workflows-legacy/edit-module/README.md

@@ -106,7 +106,7 @@ Modules can share workflows:
 
 ```yaml
 # In agent menu item:
-workflow: '{project-root}/{bmad_folder}/other-module/workflows/shared-workflow/workflow.yaml'
+workflow: '{project-root}/.bmad/other-module/workflows/shared-workflow/workflow.yaml'
 ```
 
 Common patterns:
@@ -151,7 +151,7 @@ Changes are reviewed and approved by you before being applied.
 - Can configure web bundles
 - Are the development source of truth
 
-**Installed modules** (in {bmad_folder}/):
+**Installed modules** (in .bmad/):
 
 - Are deployed to target projects
 - Use config.yaml for user customization

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

@@ -5,7 +5,7 @@ Use this checklist to validate module edits meet BMAD Core standards.
 ## Module Structure Validation
 
 - [ ] Module has clear 3-letter code (bmm, bmb, cis, etc.)
-- [ ] Module is in correct location (src/modules/ for source, {bmad_folder}/ for installed)
+- [ ] Module is in correct location (src/modules/ for source, .bmad/ for installed)
 - [ ] agents/ directory exists
 - [ ] workflows/ directory exists
 - [ ] config.yaml exists in module root
@@ -127,7 +127,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_folder}/-relative (not project-root)
+- [ ] Paths are .bmad/-relative (not project-root)
 - [ ] No config_source references in web bundles
 - [ ] Invoked workflows included in dependencies
 

src/modules/bmb/workflows-legacy/edit-module/instructions.md

@@ -1,7 +1,7 @@
 # Edit Module - Module Editor Instructions
 
-<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/edit-module/workflow.yaml</critical>
+<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/edit-module/workflow.yaml</critical>
 <critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication based on context and user needs</critical>
 <critical>The goal is COLLABORATIVE IMPROVEMENT - work WITH the user, not FOR them</critical>
 <critical>Communicate all responses in {communication_language}</critical>
@@ -9,7 +9,7 @@
 <workflow>
 
 <step n="1" goal="Load and deeply understand the target module">
-<ask>What is the path to the module you want to edit? (provide path to module directory like {bmad_folder}/bmm/ or src/modules/bmm/)</ask>
+<ask>What is the path to the module you want to edit? (provide path to module directory like .bmad/bmm/ or src/modules/bmm/)</ask>
 
 <action>Load the module directory structure completely:
 
@@ -187,7 +187,7 @@ Let the conversation flow naturally. Build a shared vision of what "better" look
 **If setting up cross-module integration:**
 
 - Identify which workflows from other modules are needed
-- Show how to reference workflows properly: {project-root}/{bmad_folder}/{{module}}/workflows/{{workflow}}/workflow.yaml
+- Show how to reference workflows properly: {project-root}/.bmad/{{module}}/workflows/{{workflow}}/workflow.yaml
 - Document the integration in README
 - Ensure dependencies are clear
 - Consider adding example usage

src/modules/bmb/workflows-legacy/edit-module/workflow.yaml

@@ -4,26 +4,26 @@ description: "Edit existing BMAD modules (structure, agents, workflows, document
 author: "BMad"
 
 # Critical variables load from config_source
-config_source: "{project-root}/{bmad_folder}/bmb/config.yaml"
+config_source: "{project-root}/.bmad/bmb/config.yaml"
 communication_language: "{config_source}:communication_language"
 user_name: "{config_source}:user_name"
 
 # Required Data Files - Critical for understanding module conventions
-module_structure_guide: "{project-root}/{bmad_folder}/bmb/workflows/create-module/module-structure.md"
+module_structure_guide: "{project-root}/.bmad/bmb/workflows/create-module/module-structure.md"
 
 # Related workflow editors
-agent_editor: "{project-root}/{bmad_folder}/bmb/workflows/edit-agent/workflow.yaml"
-workflow_editor: "{project-root}/{bmad_folder}/bmb/workflows/edit-workflow/workflow.yaml"
+agent_editor: "{project-root}/.bmad/bmb/workflows/edit-agent/workflow.yaml"
+workflow_editor: "{project-root}/.bmad/bmb/workflows/edit-workflow/workflow.yaml"
 
 # Reference examples - for learning patterns
-bmm_module_dir: "{project-root}/{bmad_folder}/bmm/"
-bmb_module_dir: "{project-root}/{bmad_folder}/bmb/"
-cis_module_dir: "{project-root}/{bmad_folder}/cis/"
-existing_agents_dir: "{project-root}/{bmad_folder}/*/agents/"
-existing_workflows_dir: "{project-root}/{bmad_folder}/*/workflows/"
+bmm_module_dir: "{project-root}/.bmad/bmm/"
+bmb_module_dir: "{project-root}/.bmad/bmb/"
+cis_module_dir: "{project-root}/.bmad/cis/"
+existing_agents_dir: "{project-root}/.bmad/*/agents/"
+existing_workflows_dir: "{project-root}/.bmad/*/workflows/"
 
 # Module path and component files
-installed_path: "{project-root}/{bmad_folder}/bmb/workflows/edit-module"
+installed_path: "{project-root}/.bmad/bmb/workflows/edit-module"
 template: false # This is an action workflow - no template needed
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

src/modules/bmb/workflows-legacy/module-brief/README.md

@@ -254,8 +254,8 @@ To customize this workflow:
 
 For issues or questions:
 
-- Review the workflow creation guide at `/{bmad_folder}/bmb/workflows/create-workflow/workflow-creation-guide.md`
-- Study existing module examples in `/{bmad_folder}/` for patterns and inspiration
+- Review the workflow creation guide at `/.bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
+- Study existing module examples in `/.bmad/` for patterns and inspiration
 - Validate output using `checklist.md`
 - Consult module structure guide at `create-module/module-structure.md`
 

src/modules/bmb/workflows-legacy/module-brief/instructions.md

@@ -1,7 +1,7 @@
 # Module Brief Instructions
 
-<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/module-brief/workflow.yaml</critical>
+<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/module-brief/workflow.yaml</critical>
 <critical>Communicate in {communication_language} throughout the module brief creation process</critical>
 <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
 

src/modules/bmb/workflows-legacy/module-brief/workflow.yaml

@@ -4,15 +4,15 @@ description: "Create a comprehensive Module Brief that serves as the blueprint f
 author: "BMad Builder"
 
 # Critical variables
-config_source: "{project-root}/{bmad_folder}/bmb/config.yaml"
+config_source: "{project-root}/.bmad/bmb/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 date: system-generated
 
 # Reference examples and documentation
-existing_modules_dir: "{project-root}/{bmad_folder}/"
-module_structure_guide: "{project-root}/{bmad_folder}/bmb/workflows/create-module/module-structure.md"
+existing_modules_dir: "{project-root}/.bmad/"
+module_structure_guide: "{project-root}/.bmad/bmb/workflows/create-module/module-structure.md"
 
 # Optional user inputs - discovered if they exist
 input_file_patterns:
@@ -22,7 +22,7 @@ input_file_patterns:
     load_strategy: "FULL_LOAD"
 
 # Module path and component files
-installed_path: "{project-root}/{bmad_folder}/bmb/workflows/module-brief"
+installed_path: "{project-root}/.bmad/bmb/workflows/module-brief"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

src/modules/bmb/workflows/create-agent/data/reference/agents/module-examples/README.md

@@ -7,7 +7,7 @@ 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
+- Use `.bmad` path variables
 - Have fixed professional personas (no install_config)
 - Reference module-specific configurations
 

src/modules/bmb/workflows/create-agent/data/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,22 +32,22 @@ agent:
   menu:
     # NOTE: These workflows are hypothetical examples - not implemented
     - trigger: threat-model
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/threat-model/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/threat-model/workflow.yaml"
       description: "Create STRIDE threat model for architecture"
 
     - trigger: security-review
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/security-review/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/security-review/workflow.yaml"
       description: "Review code/design for security issues"
 
     - trigger: owasp-check
-      exec: "{project-root}/{bmad_folder}/bmm/tasks/owasp-top-10.xml"
+      exec: "{project-root}/.bmad/bmm/tasks/owasp-top-10.xml"
       description: "Check against OWASP Top 10"
 
     - trigger: compliance
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/compliance-check/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/compliance-check/workflow.yaml"
       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"

src/modules/bmb/workflows/create-agent/data/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
-      workflow: "{project-root}/{bmad_folder}/cis/workflows/trend-scan/workflow.yaml"
+      workflow: "{project-root}/.bmad/cis/workflows/trend-scan/workflow.yaml"
       description: "Scan for emerging trends in a domain"
 
     - trigger: analyze-trend
-      workflow: "{project-root}/{bmad_folder}/cis/workflows/trend-analysis/workflow.yaml"
+      workflow: "{project-root}/.bmad/cis/workflows/trend-analysis/workflow.yaml"
       description: "Deep dive on a specific trend"
 
     - trigger: opportunity-map
-      workflow: "{project-root}/{bmad_folder}/cis/workflows/opportunity-mapping/workflow.yaml"
+      workflow: "{project-root}/.bmad/cis/workflows/opportunity-mapping/workflow.yaml"
       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
-      workflow: "{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml"
+      workflow: "{project-root}/.bmad/core/workflows/brainstorming/workflow.yaml"
       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"

src/modules/bmb/workflows/create-agent/data/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'

src/modules/bmb/workflows/create-agent/data/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'

src/modules/bmb/workflows/create-agent/data/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'

src/modules/bmb/workflows/create-agent/data/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'

src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md

@@ -3,7 +3,7 @@ name: 'step-04-strategy'
 description: 'Design a personalized meal strategy that meets nutritional needs and fits lifestyle'
 
 # 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-04-strategy.md'
@@ -13,8 +13,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
 recipeDatabase: '{workflow_path}/data/recipe-database.csv'
@@ -167,8 +167,8 @@ Display: **Select an Option:** [A] Meal Variety Optimization [P] Chef & Dietitia
 #### Menu Handling Logic:
 
 - HALT and AWAIT ANSWER
-- IF A: Execute `{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml`
-- IF P: Execute `{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md`
+- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml`
+- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md`
 - IF C: Save content to nutrition-plan.md, update frontmatter, check cooking frequency:
   - IF cooking frequency > 2x/week: load, read entire file, then execute `{workflow_path}/step-05-shopping.md`
   - IF cooking frequency ≤ 2x/week: load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md`

src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md

@@ -3,7 +3,7 @@ name: 'step-05-shopping'
 description: 'Create a comprehensive shopping list that supports the meal strategy'
 
 # 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-05-shopping.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
 shoppingTemplate: '{workflow_path}/templates/shopping-section.md'
@@ -157,8 +157,8 @@ Display: **Select an Option:** [A] Budget Optimization Strategies [P] Shopping P
 #### Menu Handling Logic:
 
 - HALT and AWAIT ANSWER
-- IF A: Execute `{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml`
-- IF P: Execute `{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md`
+- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml`
+- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md`
 - IF C: Save content to nutrition-plan.md, update frontmatter, then load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md`
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options)
 

src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md

@@ -3,7 +3,7 @@ name: 'step-06-prep-schedule'
 description: "Create a realistic meal prep schedule that fits the user's lifestyle"
 
 # 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-06-prep-schedule.md'
@@ -11,8 +11,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
 prepScheduleTemplate: '{workflow_path}/templates/prep-schedule-section.md'
@@ -178,8 +178,8 @@ Display: **Select an Option:** [A] Advanced Prep Techniques [P] Coach Perspectiv
 #### Menu Handling Logic:
 
 - HALT and AWAIT ANSWER
-- IF A: Execute `{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml`
-- IF P: Execute `{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md`
+- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml`
+- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md`
 - IF C: Update frontmatter with all steps completed, mark workflow complete, display final message
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
 

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

@@ -49,10 +49,10 @@ This uses **step-file architecture** for disciplined execution:
 
 ### 1. Configuration Loading
 
-Load and read full config from {project-root}/{bmad_folder}/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`
 
 ### 2. First Step EXECUTION
 
-Load, read the full file and then execute `{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md` to begin the workflow.
+Load, read the full file and then execute `{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md` to begin the workflow.

src/modules/bmb/workflows/create-agent/data/validation-complete.md

@@ -2,8 +2,8 @@
 
 ## Migration Summary
 
-**Legacy Workflow:** `src/modules/bmb/workflows-legacy/create-agent/workflow.yaml` + `instructions.md`
-**New Workflow:** `src/modules/bmb/workflows/create-agent/workflow.md` + 11 step files
+**Legacy Workflow:** `bmb/workflows/create-agent-legacy/create-agent/workflow.yaml` + `instructions.md`
+**New Workflow:** `bmb/workflows/create-agent/create-agent/workflow.md` + 11 step files
 **Migration Date:** 2025-11-30T06:32:21.248Z
 **Migration Status:** ✅ COMPLETE
 
@@ -81,10 +81,10 @@
 
 **Agent Documentation References**
 
-- Agent compilation guide: `{project-root}/{bmad_folder}/bmb/docs/agents/agent-compilation.md`
-- Agent types guide: `{project-root}/{bmad_folder}/bmb/docs/agents/understanding-agent-types.md`
+- Agent compilation guide: `{project-root}/.bmad/bmb/docs/agents/agent-compilation.md`
+- Agent types guide: `{project-root}/.bmad/bmb/docs/agents/understanding-agent-types.md`
 - Architecture docs: simple, expert, module agent architectures
-- Menu patterns guide: `{project-root}/{bmad_folder}/bmb/docs/agents/agent-menu-patterns.md`
+- Menu patterns guide: `{project-root}/.bmad/bmb/docs/agents/agent-menu-patterns.md`
 - Status: ✅ ALL REFERENCES PRESERVED
 
 **Communication Presets**

src/modules/bmb/workflows/create-agent/steps/step-01-brainstorm.md

@@ -3,18 +3,18 @@ name: 'step-01-brainstorm'
 description: 'Optional brainstorming for agent ideas'
 
 # Path Definitions
-workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent'
+workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-01-brainstorm.md'
 nextStepFile: '{workflow_path}/steps/step-02-discover.md'
 workflowFile: '{workflow_path}/workflow.md'
 brainstormContext: '{workflow_path}/data/brainstorm-context.md'
-brainstormWorkflow: '{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.md'
+brainstormWorkflow: '{project-root}/.bmad/core/workflows/brainstorming/workflow.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'
 ---
 
 # Step 1: Optional Brainstorming

src/modules/bmb/workflows/create-agent/steps/step-02-discover.md

@@ -3,14 +3,14 @@ name: 'step-02-discover'
 description: 'Discover the agent purpose and type through natural conversation'
 
 # Path Definitions
-workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent'
+workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-02-discover.md'
 nextStepFile: '{workflow_path}/steps/step-03-persona.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/agent-purpose-{project_name}.md'
-agentTypesGuide: '{project-root}/{bmad_folder}/bmb/docs/agents/understanding-agent-types.md'
+agentTypesGuide: '{project-root}/.bmad/bmb/docs/agents/understanding-agent-types.md'
 simpleExamples: '{workflow_path}/data/reference/agents/simple-examples/'
 expertExamples: '{workflow_path}/data/reference/agents/expert-examples/'
 moduleExamples: '{workflow_path}/data/reference/agents/module-examples/'
@@ -19,8 +19,8 @@ moduleExamples: '{workflow_path}/data/reference/agents/module-examples/'
 agentPurposeTemplate: '{workflow_path}/templates/agent-purpose-and-type.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'
 ---
 
 # Step 2: Discover Agent Purpose and Type

src/modules/bmb/workflows/create-agent/steps/step-03-persona.md

@@ -3,7 +3,7 @@ name: 'step-03-persona'
 description: 'Shape the agent personality through collaborative discovery'
 
 # Path Definitions
-workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent'
+workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-03-persona.md'
@@ -11,14 +11,14 @@ nextStepFile: '{workflow_path}/steps/step-04-commands.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/agent-persona-{project_name}.md'
 communicationPresets: '{workflow_path}/data/communication-presets.csv'
-agentMenuPatterns: '{project-root}/{bmad_folder}/bmb/docs/agents/agent-menu-patterns.md'
+agentMenuPatterns: '{project-root}/.bmad/bmb/docs/agents/agent-menu-patterns.md'
 
 # Template References
 personaTemplate: '{workflow_path}/templates/agent-persona.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'
 ---
 
 # Step 3: Shape Agent's Personality

src/modules/bmb/workflows/create-agent/steps/step-04-commands.md

@@ -3,24 +3,24 @@ name: 'step-04-commands'
 description: 'Build capabilities through natural progression and refine commands'
 
 # Path Definitions
-workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent'
+workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-04-commands.md'
 nextStepFile: '{workflow_path}/steps/step-05-name.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/agent-commands-{project_name}.md'
-agentMenuPatterns: '{project-root}/{bmad_folder}/bmb/docs/agents/agent-menu-patterns.md'
-simpleArchitecture: '{project-root}/{bmad_folder}/bmb/docs/agents/simple-agent-architecture.md'
-expertArchitecture: '{project-root}/{bmad_folder}/bmb/docs/agents/expert-agent-architecture.md'
-moduleArchitecture: '{project-root}/{bmad_folder}/bmb/docs/agents/module-agent-architecture.md'
+agentMenuPatterns: '{project-root}/.bmad/bmb/docs/agents/agent-menu-patterns.md'
+simpleArchitecture: '{project-root}/.bmad/bmb/docs/agents/simple-agent-architecture.md'
+expertArchitecture: '{project-root}/.bmad/bmb/docs/agents/expert-agent-architecture.md'
+moduleArchitecture: '{project-root}/.bmad/bmb/docs/agents/module-agent-architecture.md'
 
 # Template References
 commandsTemplate: '{workflow_path}/templates/agent-commands.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'
 ---
 
 # Step 4: Build Capabilities and Commands

src/modules/bmb/workflows/create-agent/steps/step-05-name.md

@@ -3,7 +3,7 @@ name: 'step-05-name'
 description: 'Name the agent based on discovered characteristics'
 
 # Path Definitions
-workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent'
+workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-05-name.md'
@@ -15,8 +15,8 @@ outputFile: '{output_folder}/agent-identity-{project_name}.md'
 identityTemplate: '{workflow_path}/templates/agent-identity.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'
 ---
 
 # Step 5: Agent Naming and Identity

src/modules/bmb/workflows/create-agent/steps/step-06-build.md

@@ -3,22 +3,22 @@ name: 'step-06-build'
 description: 'Generate complete YAML incorporating all discovered elements'
 
 # Path Definitions
-workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent'
+workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-06-build.md'
 nextStepFile: '{workflow_path}/steps/step-07-validate.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/agent-yaml-{project_name}.md'
-moduleOutputFile: '{project-root}/{bmad_folder}/{target_module}/agents/{agent_filename}.agent.yaml'
+moduleOutputFile: '{project-root}/.bmad/{target_module}/agents/{agent_filename}.agent.yaml'
 standaloneOutputFile: '{workflow_path}/data/{agent_filename}/{agent_filename}.agent.yaml'
 
 # Template References
 completeAgentTemplate: '{workflow_path}/templates/agent-complete-{agent_type}.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'
 ---
 
 # Step 6: Build Complete Agent YAML

src/modules/bmb/workflows/create-agent/steps/step-07-validate.md

@@ -3,22 +3,22 @@ name: 'step-07-validate'
 description: 'Quality check with personality and technical validation'
 
 # Path Definitions
-workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent'
+workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-07-validate.md'
 nextStepFile: '{workflow_path}/steps/step-08-setup.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/agent-validation-{project_name}.md'
-agentValidationChecklist: '{project-root}/{bmad_folder}/bmb/workflows/create-agent/agent-validation-checklist.md'
+agentValidationChecklist: '{project-root}/.bmad/bmb/workflows/create-agent/agent-validation-checklist.md'
 agentFile: '{{output_file_path}}'
 
 # Template References
 validationTemplate: '{workflow_path}/templates/validation-results.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'
 ---
 
 # Step 7: Quality Check and Validation

src/modules/bmb/workflows/create-agent/steps/step-08-setup.md

@@ -3,7 +3,7 @@ name: 'step-08-setup'
 description: 'Set up the agent workspace with sidecar files for expert agents'
 
 # Path Definitions
-workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent'
+workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-08-setup.md'
@@ -16,8 +16,8 @@ agentSidecarFolder: '{{standalone_output_folder}}/{{agent_filename}}-sidecar'
 sidecarTemplate: '{workflow_path}/templates/expert-sidecar-structure.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'
 ---
 
 # Step 8: Expert Agent Workspace Setup

src/modules/bmb/workflows/create-agent/steps/step-09-customize.md

@@ -3,21 +3,21 @@ name: 'step-09-customize'
 description: 'Optional personalization with customization file creation'
 
 # Path Definitions
-workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent'
+workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-09-customize.md'
 nextStepFile: '{workflow_path}/steps/step-10-build-tools.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/agent-customization-{project_name}.md'
-configOutputFile: '{project-root}/{bmad_folder}/_cfg/agents/{target_module}-{agent_filename}.customize.yaml'
+configOutputFile: '{project-root}/.bmad/_cfg/agents/{target_module}-{agent_filename}.customize.yaml'
 
 # Template References
 customizationTemplate: '{workflow_path}/templates/agent-customization.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'
 ---
 
 # Step 9: Optional Customization File

src/modules/bmb/workflows/create-agent/steps/step-10-build-tools.md

@@ -3,7 +3,7 @@ name: 'step-10-build-tools'
 description: 'Handle build tools availability and generate compiled agent if needed'
 
 # Path Definitions
-workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent'
+workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-10-build-tools.md'
@@ -17,8 +17,8 @@ compiledAgentFile: '{{output_folder}}/{{agent_filename}}.md'
 buildHandlingTemplate: '{workflow_path}/templates/build-results.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'
 ---
 
 # Step 10: Build Tools Handling

src/modules/bmb/workflows/create-agent/steps/step-11-celebrate.md

@@ -3,7 +3,7 @@ name: 'step-11-celebrate'
 description: 'Celebrate completion and guide next steps for using the agent'
 
 # Path Definitions
-workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent'
+workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-11-celebrate.md'
@@ -16,8 +16,8 @@ compiledAgentFile: '{{compiled_agent_path}}'
 completionTemplate: '{workflow_path}/templates/completion-summary.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'
 ---
 
 # Step 11: Celebration and Next Steps

src/modules/bmb/workflows/create-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_folder}/bmb/config.yaml`:
+Load and read full config from `{project-root}/.bmad/bmb/config.yaml`:
 
 - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
 
@@ -63,12 +63,12 @@ Load, read completely, then execute `steps/step-01-brainstorm.md` to begin the w
 
 # Technical documentation for agent building
 
-agent_compilation: "{project-root}/{bmad_folder}/bmb/docs/agents/agent-compilation.md"
-understanding_agent_types: "{project-root}/{bmad_folder}/bmb/docs/agents/understanding-agent-types.md"
-simple_agent_architecture: "{project-root}/{bmad_folder}/bmb/docs/agents/simple-agent-architecture.md"
-expert_agent_architecture: "{project-root}/{bmad_folder}/bmb/docs/agents/expert-agent-architecture.md"
-module_agent_architecture: "{project-root}/{bmad_folder}/bmb/docs/agents/module-agent-architecture.md"
-agent_menu_patterns: "{project-root}/{bmad_folder}/bmb/docs/agents/agent-menu-patterns.md"
+agent_compilation: "{project-root}/.bmad/bmb/docs/agents/agent-compilation.md"
+understanding_agent_types: "{project-root}/.bmad/bmb/docs/agents/understanding-agent-types.md"
+simple_agent_architecture: "{project-root}/.bmad/bmb/docs/agents/simple-agent-architecture.md"
+expert_agent_architecture: "{project-root}/.bmad/bmb/docs/agents/expert-agent-architecture.md"
+module_agent_architecture: "{project-root}/.bmad/bmb/docs/agents/module-agent-architecture.md"
+agent_menu_patterns: "{project-root}/.bmad/bmb/docs/agents/agent-menu-patterns.md"
 
 # Data and templates
 
@@ -77,15 +77,15 @@ brainstorm_context: "{workflow_path}/data/brainstorm-context.md"
 
 # Reference examples
 
-simple_agent_examples: "{project-root}/src/modules/bmb/reference/agents/simple-examples/"
-expert_agent_examples: "{project-root}/src/modules/bmb/reference/agents/expert-examples/"
-module_agent_examples: "{project-root}/src/modules/bmb/reference/agents/module-examples/"
+simple_agent_examples: "{project-root}/bmb/reference/agents/simple-examples/"
+expert_agent_examples: "{project-root}/bmb/reference/agents/expert-examples/"
+module_agent_examples: "{project-root}/bmb/reference/agents/module-examples/"
 
 # Output configuration
 
-custom_agent_location: "{project-root}/{bmad_folder}/custom/src/agents"
-module_output_file: "{project-root}/{bmad_folder}/{target_module}/agents/{agent_filename}.agent.yaml"
+custom_agent_location: "{project-root}/.bmad/custom/src/agents"
+module_output_file: "{project-root}/.bmad/{target_module}/agents/{agent_filename}.agent.yaml"
 standalone_output_folder: "{custom_agent_location}/{agent_filename}"
 standalone_output_file: "{standalone_output_folder}/{agent_filename}.agent.yaml"
 standalone_info_guide: "{standalone_output_folder}/info-and-installation-guide.md"
-config_output_file: "{project-root}/{bmad_folder}/\_cfg/agents/{target_module}-{agent_filename}.customize.yaml"
+config_output_file: "{project-root}/.bmad/\_cfg/agents/{target_module}-{agent_filename}.customize.yaml"

src/modules/bmb/workflows/create-module/steps/step-01-init.md

@@ -2,8 +2,8 @@
 nextStepFile: '{installed_path}/steps/step-02-concept.md'
 continueFile: '{installed_path}/steps/step-01b-continue.md'
 modulePlanTemplate: '{installed_path}/templates/module-plan.template.md'
-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'
 customModuleLocation: '{custom_module_location}'
 modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
 ---

src/modules/bmb/workflows/create-module/steps/step-02-concept.md

@@ -1,10 +1,10 @@
 ---
-installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module'
+installed_path: '{project-root}/.bmad/bmb/workflows/create-module'
 nextStepFile: '{installed_path}/steps/step-03-components.md'
 modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
-moduleStructureGuide: '{project-root}/src/modules/bmb/workflows-legacy/create-module/module-structure.md'
-advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
+moduleStructureGuide: '{project-root}/bmb/workflows/create-agent-legacy/create-module/module-structure.md'
+advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
 ---
 
 # Step 2: Define Module Concept and Scope

src/modules/bmb/workflows/create-module/steps/step-03-components.md

@@ -1,10 +1,10 @@
 ---
-installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module'
+installed_path: '{project-root}/.bmad/bmb/workflows/create-module'
 nextStepFile: '{installed_path}/steps/step-04-structure.md'
 modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
-agent_examples_path: '{project-root}/src/modules/bmb/reference/agents/module-examples'
-advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
+agent_examples_path: '{project-root}/bmb/reference/agents/module-examples'
+advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
 ---
 
 # Step 3: Plan Module Components

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

@@ -1,9 +1,9 @@
 ---
-installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module'
+installed_path: '{project-root}/.bmad/bmb/workflows/create-module'
 nextStepFile: '{installed_path}/steps/step-05-config.md'
 modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
-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'
 ---
 
 # Step 4: Create Module Structure

src/modules/bmb/workflows/create-module/steps/step-05-config.md

@@ -1,9 +1,9 @@
 ---
-installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module'
+installed_path: '{project-root}/.bmad/bmb/workflows/create-module'
 nextStepFile: '{installed_path}/steps/step-06-agents.md'
 modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
-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'
 ---
 
 # Step 5: Plan Module Configuration
@@ -185,7 +185,7 @@ Update module-plan.md with configuration section:
 ### Result Configuration Structure
 
 The module.yaml will generate:
-- Module configuration at: {bmad_folder}/{module_code}/config.yaml
+- Module configuration at: .bmad/{module_code}/config.yaml
 - User settings stored as: [describe structure]
 ````
 

src/modules/bmb/workflows/create-module/steps/step-06-agents.md

@@ -1,11 +1,11 @@
 ---
-installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module'
+installed_path: '{project-root}/.bmad/bmb/workflows/create-module'
 nextStepFile: '{installed_path}/steps/step-07-workflows.md'
 modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
 agentTemplate: '{installed_path}/templates/agent.template.md'
-agent_examples_path: '{project-root}/src/modules/bmb/reference/agents/module-examples'
-advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
+agent_examples_path: '{project-root}/bmb/reference/agents/module-examples'
+advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
 ---
 
 # Step 6: Create Module Agents
@@ -183,7 +183,7 @@ agent:
       triggers:
         - party-mode:
           input: SPM
-          route: '{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md'
+          route: '{project-root}/.bmad/core/workflows/edit-agent/workflow.md'
           type: exec
         - expert-chat:
           input: CH
@@ -204,7 +204,7 @@ agent:
 
     # Workflow only for complex processes
     - trigger: 'complex-process'
-      route: '{project-root}/{bmad_folder}/{custom_module}/workflows/[workflow]/workflow.md'
+      route: '{project-root}/.bmad/{custom_module}/workflows/[workflow]/workflow.md'
       description: 'Complex process [icon]'
 
     # Quick inline actions

src/modules/bmb/workflows/create-module/steps/step-07-workflows.md

@@ -1,10 +1,10 @@
 ---
-installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module'
+installed_path: '{project-root}/.bmad/bmb/workflows/create-module'
 nextStepFile: '{installed_path}/steps/step-08-installer.md'
 modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
 workflowPlanTemplate: '{installed_path}/templates/workflow-plan-template.md'
-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'
 ---
 
 # Step 7: Review Workflow Plans

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

@@ -1,11 +1,11 @@
 ---
-installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module'
+installed_path: '{project-root}/.bmad/bmb/workflows/create-module'
 nextStepFile: '{installed_path}/steps/step-09-documentation.md'
 modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
 installerTemplate: '{installed_path}/templates/installer.template.js'
 installConfigTemplate: '{installed_path}/templates/install-config.template.yaml'
-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'
 ---
 
 # Step 8: Setup Module Installer
@@ -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_folder}/{module_name}/
+3. Creates: .bmad/{module_name}/
 4. Generates: config.yaml with user settings
 
 ### Validation

src/modules/bmb/workflows/create-module/steps/step-09-documentation.md

@@ -1,10 +1,10 @@
 ---
-installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module'
+installed_path: '{project-root}/.bmad/bmb/workflows/create-module'
 nextStepFile: '{installed_path}/steps/step-10-roadmap.md'
 modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
 moduleReadmeFile: '{custom_module_location}/{module_name}/README.md'
-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'
 ---
 
 # Step 9: Create Module Documentation
@@ -140,7 +140,7 @@ bmad install {module_name}
 
 ## Configuration
 
-The module can be configured in `{bmad_folder}/{module_name}/config.yaml`
+The module can be configured in `.bmad/{module_name}/config.yaml`
 
 **Key Settings:**
 

src/modules/bmb/workflows/create-module/steps/step-10-roadmap.md

@@ -1,10 +1,10 @@
 ---
-installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module'
+installed_path: '{project-root}/.bmad/bmb/workflows/create-module'
 nextStepFile: '{installed_path}/steps/step-11-validate.md'
 modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
 moduleTodoFile: '{custom_module_location}/{module_name}/TODO.md'
-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'
 ---
 
 # Step 10: Generate Development Roadmap

src/modules/bmb/workflows/create-module/steps/step-11-validate.md

@@ -2,8 +2,8 @@
 workflowFile: '{installed_path}/workflow.md'
 modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
 validationChecklist: '{installed_path}/validation.md'
-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'
 ---
 
 # Step 11: Validate and Finalize Module
@@ -297,8 +297,8 @@ Display: **Module Creation Complete!** [A] Advanced Elicitation [P] Party Mode [
 
 #### Menu Handling Logic:
 
-- IF A: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml for reflection on process
-- IF P: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md to celebrate completion
+- IF A: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml for reflection on process
+- IF P: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md to celebrate completion
 - IF C: Mark as complete and exit gracefully
 - IF Any other comments or queries: help user respond then redisplay menu
 

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

@@ -55,7 +55,7 @@ agent:
       triggers:
         - party-mode:
           input: SPM or fuzzy match start party mode
-          route: '{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md'
+          route: '{project-root}/.bmad/core/workflows/edit-agent/workflow.md'
           data: what is being discussed or suggested with the command
           type: exec
         - expert-chat:
@@ -83,7 +83,7 @@ agent:
 
     # Workflow for complex processes
     - trigger: 'generate-report'
-      route: '{project-root}/{bmad_folder}/{custom_module}/workflows/report-gen/workflow.md'
+      route: '{project-root}/.bmad/{custom_module}/workflows/report-gen/workflow.md'
       description: 'Generate detailed report 📊'
 
     # Exec with internal prompt reference
@@ -156,7 +156,7 @@ Expert agents support three types of menu actions:
 
 ```yaml
 - trigger: 'generate-report'
-  route: '{project-root}/{bmad_folder}/{custom_module}/workflows/report-gen/workflow.md'
+  route: '{project-root}/.bmad/{custom_module}/workflows/report-gen/workflow.md'
   description: 'Generate report 📊'
 ```
 
@@ -171,7 +171,7 @@ Expert agents support three types of menu actions:
 
 2. **Variable Usage**:
    - `{agent_sidecar_folder}` resolves to the agents sidecar folder destination after installation
-   - `{bmad_folder}` resolves to .bmad
+   - `.bmad` resolves to .bmad
    - `{custom_module}` resolves to custom/src/modules
    - `{module}` is your module code/name
 
@@ -268,7 +268,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_folder}/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
@@ -305,11 +305,11 @@ type: action
       triggers:
         - pitch-deck:
           input: PD or fuzzy match pitch deck
-          route: "{project-root}/{bmad_folder}/{custom_module}/workflows/pitch-deck/workflow.md"
+          route: "{project-root}/.bmad/{custom_module}/workflows/pitch-deck/workflow.md"
           description: 'Investor pitch deck 📈'
         - explainer:
           input: EX or fuzzy match explainer
-          route: "{project-root}/{bmad_folder}/{custom_module}/workflows/explainer/workflow.md"
+          route: "{project-root}/.bmad/{custom_module}/workflows/explainer/workflow.md"
           description: 'Video explainer 🎥'
 
     - trigger: 'save-project'

src/modules/bmb/workflows/create-module/templates/module.template.yaml

@@ -50,4 +50,4 @@ prompt:
 
 # STATIC path:
 # data_path:
-#   result: "{project-root}/{bmad_folder}/{module_name}/data"
+#   result: "{project-root}/.bmad/{module_name}/data"

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

@@ -2,7 +2,7 @@
 name: create-module
 description: 'Interactive workflow to build complete BMAD modules with agents, workflows, and installation infrastructure'
 web_bundle: true
-installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module'
+installed_path: '{project-root}/.bmad/bmb/workflows/create-module'
 ---
 
 # Create Module Workflow
@@ -46,7 +46,7 @@ installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module'
 
 ### 1. Module Configuration Loading
 
-Load and read full config from {project-root}/{bmad_folder}/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`, `custom_module_location`
 

src/modules/bmb/workflows/create-workflow/steps/step-01-init.md

@@ -3,7 +3,7 @@ name: 'step-01-init'
 description: 'Initialize workflow creation session by gathering project information and setting up unique workflow folder'
 
 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow'
+workflow_path: '{project-root}/.bmad/bmb/workflows/create-workflow'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-01-init.md'
@@ -97,7 +97,7 @@ After getting the workflow name:
 
 Based on the module selection, confirm the target location:
 
-- For bmb module: `{custom_workflow_location}` (defaults to `{bmad_folder}/custom/src/workflows`)
+- For bmb module: `{custom_workflow_location}` (defaults to `.bmad/custom/src/workflows`)
 - For other modules: Check their module.yaml for custom workflow locations
 - Confirm the exact folder path where the workflow will be created
 - Store the confirmed path as `{targetWorkflowPath}`

src/modules/bmb/workflows/create-workflow/steps/step-02-gather.md

@@ -3,7 +3,7 @@ name: 'step-02-gather'
 description: 'Gather comprehensive requirements for the workflow being created'
 
 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow'
+workflow_path: '{project-root}/.bmad/bmb/workflows/create-workflow'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-02-gather.md'
@@ -13,8 +13,8 @@ targetWorkflowPath: '{custom_stand_alone_location}/workflows/{new_workflow_name}
 workflowPlanFile: '{targetWorkflowPath}/workflow-plan-{new_workflow_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
 # No template needed - will append requirements directly to workflow plan
 ---
@@ -90,7 +90,7 @@ Let's load some examples to help you decide the workflow pattern:
 Load and reference the Meal Prep & Nutrition Plan workflow as an example:
 
 ```
-Read: {project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition/workflow.md
+Read: {project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md
 ```
 
 This shows a linear workflow structure. Now let's explore your desired pattern:
@@ -104,7 +104,7 @@ This shows a linear workflow structure. Now let's explore your desired pattern:
 **Based on our reference examples:**
 
 - **Linear**: Like Meal Prep Plan (Init → Profile → Assessment → Strategy → Shopping → Prep)
-  - See: `{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition/`
+  - See: `{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition/`
 - **Looping**: User Story Generator (Generate → Review → Refine → Generate more... until done)
 - **Branching**: Architecture Decision (Analyze → Choose pattern → Implement based on choice)
 - **Iterative**: Document Review (Load → Analyze → Suggest changes → Implement → Repeat until approved)

src/modules/bmb/workflows/create-workflow/steps/step-03-tools-configuration.md

@@ -3,7 +3,7 @@ name: 'step-03-tools-configuration'
 description: 'Configure all required tools (core, memory, external) and installation requirements in one comprehensive step'
 
 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow'
+workflow_path: '{project-root}/.bmad/bmb/workflows/create-workflow'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-03-tools-configuration.md'
@@ -13,11 +13,11 @@ targetWorkflowPath: '{custom_stand_alone_location}/workflows/{new_workflow_name}
 workflowPlanFile: '{targetWorkflowPath}/workflow-plan-{new_workflow_name}.md'
 
 # Documentation References
-commonToolsCsv: '{project-root}/{bmad_folder}/bmb/docs/workflows/common-workflow-tools.csv'
+commonToolsCsv: '{project-root}/.bmad/bmb/docs/workflows/common-workflow-tools.csv'
 
 # 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
 # No template needed - will append tools configuration directly to workflow plan
 ---