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

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

@@ -3,7 +3,7 @@ name: 'step-02-workflow-validation'
 description: 'Validate workflow.md against workflow-template.md standards'
 
 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check'
+workflow_path: '{project-root}/.bmad/bmb/workflows/workflow-compliance-check'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-02-workflow-validation.md'
@@ -16,8 +16,8 @@ targetWorkflowFile: '{target_workflow_path}'
 complianceReportTemplate: '{workflow_path}/templates/compliance-report.md'
 
 # Documentation References
-stepTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md'
-workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md'
+stepTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md'
+workflowTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md'
 ---
 
 # Step 2: Workflow.md Validation
@@ -132,10 +132,10 @@ For each deviation:
 
 "**Initialization Validation:**"
 
-- Configuration Loading uses correct path format: `{project-root}/{*bmad_folder*}/[module]/config.yaml` (variable substitution pattern)
+- Configuration Loading uses correct path format: `{project-root}/.bmad/[module]/config.yaml` (variable substitution pattern)
 - First step follows pattern: `step-01-init.md` OR documented deviation
 - Required config variables properly listed
-- Variables use proper substitution pattern: {project-root}, {_bmad_folder_}, {workflow_path}, etc.
+- Variables use proper substitution pattern: {project-root}, .bmad, {workflow_path}, etc.
 
 For violations:
 

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

@@ -3,7 +3,7 @@ name: 'step-03-step-validation'
 description: 'Validate each step file against step-template.md standards'
 
 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check'
+workflow_path: '{project-root}/.bmad/bmb/workflows/workflow-compliance-check'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-03-step-validation.md'
@@ -16,8 +16,8 @@ targetWorkflowStepsPath: '{target_workflow_steps_path}'
 complianceReportTemplate: '{workflow_path}/templates/compliance-report.md'
 
 # Documentation References
-stepTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md'
-workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md'
+stepTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md'
+workflowTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md'
 ---
 
 # Step 3: Step-by-Step Validation
@@ -138,8 +138,8 @@ Check for proper references:
 
 ```yaml
 # 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'
 ```
 
 **Violations to document:**
@@ -186,7 +186,7 @@ For each step:
 
 "**Path Variable Validation:**"
 
-- Check format: `{project-root}/{*bmad_folder*}/bmb/...` vs `{project-root}/src/modules/bmb/...`
+- Check format: `{project-root}/.bmad/bmb/...` vs `{project-root}/bmb/...`
 - Ensure consistent variable usage across all step files
 - Validate relative vs absolute path usage
 

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

@@ -3,7 +3,7 @@ name: 'step-04-file-validation'
 description: 'Validate file sizes, markdown formatting, and CSV data files'
 
 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check'
+workflow_path: '{project-root}/.bmad/bmb/workflows/workflow-compliance-check'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-04-file-validation.md'
@@ -16,9 +16,9 @@ targetWorkflowPath: '{target_workflow_path}'
 complianceReportTemplate: '{workflow_path}/templates/compliance-report.md'
 
 # Documentation References
-stepTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md'
-workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md'
-csvStandards: '{project-root}/{bmad_folder}/bmb/docs/workflows/csv-data-file-standards.md'
+stepTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md'
+workflowTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md'
+csvStandards: '{project-root}/.bmad/bmb/docs/workflows/csv-data-file-standards.md'
 ---
 
 # Step 4: File Size, Formatting, and Data Validation

package/src/modules/bmb/workflows/workflow-compliance-check/steps/step-05-intent-spectrum-validation.md

@@ -3,7 +3,7 @@ name: 'step-05-intent-spectrum-validation'
 description: 'Dedicated analysis and validation of intent vs prescriptive spectrum positioning'
 
 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check'
+workflow_path: '{project-root}/.bmad/bmb/workflows/workflow-compliance-check'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-05-intent-spectrum-validation.md'
@@ -16,9 +16,9 @@ targetWorkflowPath: '{target_workflow_path}'
 complianceReportTemplate: '{workflow_path}/templates/compliance-report.md'
 
 # Documentation References
-stepTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md'
-workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md'
-intentSpectrum: '{project-root}/{bmad_folder}/bmb/docs/workflows/intent-vs-prescriptive-spectrum.md'
+stepTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md'
+workflowTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md'
+intentSpectrum: '{project-root}/.bmad/bmb/docs/workflows/intent-vs-prescriptive-spectrum.md'
 ---
 
 # Step 5: Intent vs Prescriptive Spectrum Validation

package/src/modules/bmb/workflows/workflow-compliance-check/steps/step-06-web-subprocess-validation.md

@@ -3,7 +3,7 @@ name: 'step-06-web-subprocess-validation'
 description: 'Analyze web search utilization and subprocess optimization opportunities across workflow steps'
 
 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check'
+workflow_path: '{project-root}/.bmad/bmb/workflows/workflow-compliance-check'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-06-web-subprocess-validation.md'
@@ -16,9 +16,9 @@ targetWorkflowStepsPath: '{target_workflow_steps_path}'
 complianceReportTemplate: '{workflow_path}/templates/compliance-report.md'
 
 # Documentation References
-stepTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md'
-workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md'
-intentSpectrum: '{project-root}/{bmad_folder}/bmb/docs/workflows/intent-vs-prescriptive-spectrum.md'
+stepTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md'
+workflowTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md'
+intentSpectrum: '{project-root}/.bmad/bmb/docs/workflows/intent-vs-prescriptive-spectrum.md'
 ---
 
 # Step 6: Web Search & Subprocess Optimization Analysis

package/src/modules/bmb/workflows/workflow-compliance-check/steps/step-07-holistic-analysis.md

@@ -3,7 +3,7 @@ name: 'step-07-holistic-analysis'
 description: 'Analyze workflow flow, goal alignment, and meta-workflow failures'
 
 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check'
+workflow_path: '{project-root}/.bmad/bmb/workflows/workflow-compliance-check'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-07-holistic-analysis.md'
@@ -16,9 +16,9 @@ targetWorkflowFile: '{target_workflow_path}'
 complianceReportTemplate: '{workflow_path}/templates/compliance-report.md'
 
 # Documentation References
-stepTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md'
-workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md'
-intentSpectrum: '{project-root}/{bmad_folder}/bmb/docs/workflows/intent-vs-prescriptive-spectrum.md'
+stepTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md'
+workflowTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md'
+intentSpectrum: '{project-root}/.bmad/bmb/docs/workflows/intent-vs-prescriptive-spectrum.md'
 ---
 
 # Step 7: Holistic Workflow Analysis

package/src/modules/bmb/workflows/workflow-compliance-check/steps/step-08-generate-report.md

@@ -3,7 +3,7 @@ name: 'step-08-generate-report'
 description: 'Generate comprehensive compliance report with fix recommendations'
 
 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check'
+workflow_path: '{project-root}/.bmad/bmb/workflows/workflow-compliance-check'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-08-generate-report.md'
@@ -15,8 +15,8 @@ targetWorkflowFile: '{target_workflow_path}'
 complianceReportTemplate: '{workflow_path}/templates/compliance-report.md'
 
 # Documentation References
-stepTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md'
-workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md'
+stepTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md'
+workflowTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md'
 ---
 
 # Step 8: Comprehensive Compliance Report Generation

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

@@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution:
 
 ### 1. Configuration Loading
 
-Load and read full config from {project-root}/{bmad_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`
 

package/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

package/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
 

package/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

package/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"

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

package/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>
 

package/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"

package/src/modules/bmgd/README.md

@@ -136,7 +136,7 @@ bmgd/
 
 ## Configuration
 
-After installation, configure the module in `{bmad_folder}/bmgd/config.yaml`
+After installation, configure the module in `.bmad/bmgd/config.yaml`
 
 Key settings:
 

package/src/modules/bmgd/agents/game-architect.agent.yaml

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: "{bmad_folder}/bmgd/agents/game-architect.md"
+    id: ".bmad/bmgd/agents/game-architect.md"
     name: Cloud Dragonborn
     title: Game Architect
     icon: 🏛️
@@ -16,18 +16,18 @@ agent:
 
   menu:
     - trigger: correct-course
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml"
-      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/correct-course/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
+      workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/correct-course/workflow.yaml"
       description: Course Correction Analysis
 
     - trigger: create-architecture
-      workflow: "{project-root}/{bmad_folder}/bmgd/workflows/3-technical/game-architecture/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmgd/workflows/3-technical/game-architecture/workflow.yaml"
       description: Produce a Scale Adaptive Game Architecture
 
     - 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: Consult with other expert agents from the party
 
     - 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 to challenge the LLM to get better results

package/src/modules/bmgd/agents/game-designer.agent.yaml

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: "{bmad_folder}/bmgd/agents/game-designer.md"
+    id: ".bmad/bmgd/agents/game-designer.md"
     name: Samus Shepard
     title: Game Designer
     icon: 🎲
@@ -16,25 +16,25 @@ agent:
 
   menu:
     - trigger: brainstorm-game
-      workflow: "{project-root}/{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml"
       description: 1. Guide me through Game Brainstorming
 
     - trigger: create-game-brief
-      workflow: "{project-root}/{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmgd/workflows/1-preproduction/game-brief/workflow.yaml"
       description: 3. Create Game Brief
 
     - trigger: create-gdd
-      workflow: "{project-root}/{bmad_folder}/bmgd/workflows/2-design/gdd/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmgd/workflows/2-design/gdd/workflow.yaml"
       description: 4. Create Game Design Document (GDD)
 
     - trigger: narrative
-      workflow: "{project-root}/{bmad_folder}/bmgd/workflows/2-design/narrative/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmgd/workflows/2-design/narrative/workflow.yaml"
       description: 5. Create Narrative Design Document (story-driven games)
 
     - 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: Consult with other expert agents from the party
 
     - 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 to challenge the LLM to get better results

package/src/modules/bmgd/agents/game-dev.agent.yaml

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: "{bmad_folder}/bmgd/agents/game-dev.md"
+    id: ".bmad/bmgd/agents/game-dev.md"
     name: Link Freeman
     title: Game Developer
     icon: 🕹️
@@ -17,24 +17,24 @@ agent:
 
   menu:
     - trigger: develop-story
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/dev-story/workflow.yaml"
-      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/dev-story/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
+      workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/dev-story/workflow.yaml"
       description: "Execute Dev Story workflow, implementing tasks and tests, or performing updates to the story"
 
     - trigger: code-review
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/code-review/workflow.yaml"
-      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/code-review/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
+      workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/code-review/workflow.yaml"
       description: "Perform a thorough clean context QA code review on a story flagged Ready for Review"
 
     - trigger: story-done
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-done/workflow.yaml"
-      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/story-done/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/story-done/workflow.yaml"
+      workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/story-done/workflow.yaml"
       description: "Mark story done after DoD complete"
 
     - 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: Consult with other expert agents from the party
 
     - 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 to challenge the LLM to get better results

package/src/modules/bmgd/agents/game-scrum-master.agent.yaml

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: "{bmad_folder}/bmgd/agents/game-scrum-master.md"
+    id: ".bmad/bmgd/agents/game-scrum-master.md"
     name: Max
     title: Game Dev Scrum Master
     icon: 🎯
@@ -19,57 +19,57 @@ agent:
 
   menu:
     - trigger: sprint-planning
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-planning/workflow.yaml"
-      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/sprint-planning/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml"
+      workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/sprint-planning/workflow.yaml"
       description: Generate or update sprint-status.yaml from epic files
 
     - trigger: epic-tech-context
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml"
-      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/epic-tech-context/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml"
+      workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/epic-tech-context/workflow.yaml"
       description: (Optional) Use the GDD and Architecture to create an Epic-Tech-Spec for a specific epic
 
     - trigger: validate-epic-tech-context
-      validate-workflow: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/epic-tech-context/workflow.yaml"
+      validate-workflow: "{project-root}/.bmad/bmgd/workflows/4-production/epic-tech-context/workflow.yaml"
       description: (Optional) Validate latest Tech Spec against checklist
 
     - trigger: create-story-draft
-      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 Story Draft for a game feature
 
     - trigger: validate-create-story
-      validate-workflow: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/create-story/workflow.yaml"
+      validate-workflow: "{project-root}/.bmad/bmgd/workflows/4-production/create-story/workflow.yaml"
       description: (Optional) Validate Story Draft with Independent Review
 
     - trigger: story-context
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-context/workflow.yaml"
-      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/story-context/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/story-context/workflow.yaml"
+      workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/story-context/workflow.yaml"
       description: (Optional) Assemble dynamic Story Context (XML) from latest docs and code and mark story ready for dev
 
     - trigger: validate-story-context
-      validate-workflow: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/story-context/workflow.yaml"
+      validate-workflow: "{project-root}/.bmad/bmgd/workflows/4-production/story-context/workflow.yaml"
       description: (Optional) Validate latest Story Context XML against checklist
 
     - trigger: story-ready-for-dev
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-ready/workflow.yaml"
-      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/story-ready/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/story-ready/workflow.yaml"
+      workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/story-ready/workflow.yaml"
       description: (Optional) Mark drafted story ready for dev without generating Story Context
 
     - trigger: epic-retrospective
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/retrospective/workflow.yaml"
-      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/retrospective/workflow.yaml"
-      data: "{project-root}/{bmad_folder}/_cfg/agent-manifest.csv"
+      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml"
+      workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/retrospective/workflow.yaml"
+      data: "{project-root}/.bmad/_cfg/agent-manifest.csv"
       description: (Optional) Facilitate team retrospective after a game development epic is completed
 
     - trigger: correct-course
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml"
-      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/correct-course/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
+      workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/correct-course/workflow.yaml"
       description: (Optional) Navigate significant changes during game dev sprint
 
     - 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: Consult with other expert agents from the party
 
     - 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 to challenge the LLM to get better results

package/src/modules/bmgd/module.yaml

@@ -12,7 +12,6 @@ subheader: "Configure the settings for the BMad Game Development module"
 ## communication_language
 ## document_output_language
 ## output_folder
-## bmad_folder
 ## install_user_docs
 ## kb_install
 

package/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md

@@ -1,4 +1,4 @@
-<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</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: {installed_path}/workflow.yaml</critical>
 <critical>Communicate all responses in {communication_language}</critical>
 <critical>This is a meta-workflow that orchestrates the CIS brainstorming workflow with game-specific context and additional game design techniques</critical>