Merge branch 'main' into fix/issue-1088-remove-stale-workflow-refs

2025-12-29 16:14:59 +00:00 · 2025-12-10 16:00:11 -07:00
parent b9ba98d3f8 26e47562dd
commit 0f06ef724b
389 changed files with 1556 additions and 4683 deletions
--- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01-init.md
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01-init.md
@@ -3,7 +3,7 @@ name: 'step-01-init'
 description: 'Initialize the product brief workflow by detecting continuation state and setting up the document'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/.bmad/bmm/workflows/1-analysis/product-brief'

 # File References
 thisStepFile: '{workflow_path}/steps/step-01-init.md'
--- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01b-continue.md
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01b-continue.md
@@ -3,7 +3,7 @@ name: 'step-01b-continue'
 description: 'Resume the product brief workflow from where it was left off, ensuring smooth continuation'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/.bmad/bmm/workflows/1-analysis/product-brief'

 # File References
 thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
--- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-02-vision.md
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-02-vision.md
@@ -3,7 +3,7 @@ name: 'step-02-vision'
 description: 'Discover and define the core product vision, problem statement, and unique value proposition'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/.bmad/bmm/workflows/1-analysis/product-brief'

 # File References
 thisStepFile: '{workflow_path}/steps/step-02-vision.md'
@@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.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: Product Vision Discovery
--- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-03-users.md
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-03-users.md
@@ -3,7 +3,7 @@ name: 'step-03-users'
 description: 'Define target users with rich personas and map their key interactions with the product'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/.bmad/bmm/workflows/1-analysis/product-brief'

 # File References
 thisStepFile: '{workflow_path}/steps/step-03-users.md'
@@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.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: Target Users Discovery
--- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-04-metrics.md
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-04-metrics.md
@@ -3,7 +3,7 @@ name: 'step-04-metrics'
 description: 'Define comprehensive success metrics that include user success, business objectives, and key performance indicators'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/.bmad/bmm/workflows/1-analysis/product-brief'

 # File References
 thisStepFile: '{workflow_path}/steps/step-04-metrics.md'
@@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.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: Success Metrics Definition
--- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-05-scope.md
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-05-scope.md
@@ -3,7 +3,7 @@ name: 'step-05-scope'
 description: 'Define MVP scope with clear boundaries and outline future vision while managing scope creep'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/.bmad/bmm/workflows/1-analysis/product-brief'

 # File References
 thisStepFile: '{workflow_path}/steps/step-05-scope.md'
@@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.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: MVP Scope Definition
--- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-06-complete.md
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-06-complete.md
@@ -3,7 +3,7 @@ name: 'step-06-complete'
 description: 'Complete the product brief workflow, update status files, and suggest next steps for the project'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/.bmad/bmm/workflows/1-analysis/product-brief'

 # File References
 thisStepFile: '{workflow_path}/steps/step-06-complete.md'
--- a/src/modules/bmm/workflows/1-analysis/product-brief/workflow.md
+++ b/src/modules/bmm/workflows/1-analysis/product-brief/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}/bmm/workflows/1-analysis/product-brief/steps/step-01-init.md` to begin the workflow.
+Load, read the full file and then execute `{project-root}/.bmad/bmm/workflows/1-analysis/product-brief/steps/step-01-init.md` to begin the workflow.
--- a/src/modules/bmm/workflows/1-analysis/research/workflow.md
+++ b/src/modules/bmm/workflows/1-analysis/research/workflow.md
@@ -42,7 +42,7 @@ This uses **micro-file architecture** with **routing-based discovery**:

 ### Configuration Loading

-Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:
+Load config from `{project-root}/.bmad/bmm/config.yaml` and resolve:

 - `project_name`, `output_folder`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
@@ -51,7 +51,7 @@ Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:

 ### Paths

- `installed_path` = `{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research`
+- `installed_path` = `{project-root}/.bmad/bmm/workflows/1-analysis/research`
 - `template_path` = `{installed_path}/research.template.md`
 - `default_output_file` = `{output_folder}/analysis/research/{{research_type}}-{{topic}}-research-{{date}}.md` (dynamic based on research type)

--- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md
@@ -29,8 +29,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding

@@ -154,7 +154,7 @@ Show the generated project understanding content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current project understanding content
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current project understanding content
 - Process the enhanced project insights that come back
 - Ask user: "Accept these improvements to the project understanding? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -162,7 +162,7 @@ Show the generated project understanding content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current project understanding
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current project understanding
 - Process the collaborative insights and different perspectives that come back
 - Ask user: "Accept these changes to the project understanding? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
--- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md
@@ -29,8 +29,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding

@@ -160,7 +160,7 @@ Show the generated core experience content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current core experience content
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current core experience content
 - Process the enhanced experience insights that come back
 - Ask user: "Accept these improvements to the core experience definition? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -168,7 +168,7 @@ Show the generated core experience content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current core experience definition
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current core experience definition
 - Process the collaborative experience improvements that come back
 - Ask user: "Accept these changes to the core experience definition? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
--- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md
@@ -29,8 +29,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding

@@ -163,7 +163,7 @@ Show the generated emotional response content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current emotional response content
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current emotional response content
 - Process the enhanced emotional insights that come back
 - Ask user: "Accept these improvements to the emotional response definition? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -171,7 +171,7 @@ Show the generated emotional response content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current emotional response definition
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current emotional response definition
 - Process the collaborative emotional insights that come back
 - Ask user: "Accept these changes to the emotional response definition? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
--- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md
@@ -29,8 +29,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding

@@ -178,7 +178,7 @@ Show the generated inspiration analysis content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current inspiration analysis content
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current inspiration analysis content
 - Process the enhanced pattern insights that come back
 - Ask user: "Accept these improvements to the inspiration analysis? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -186,7 +186,7 @@ Show the generated inspiration analysis content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current inspiration analysis
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current inspiration analysis
 - Process the collaborative pattern insights that come back
 - Ask user: "Accept these changes to the inspiration analysis? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
--- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md
@@ -29,8 +29,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding

@@ -196,7 +196,7 @@ Show the generated design system content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current design system content
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current design system content
 - Process the enhanced design system insights that come back
 - Ask user: "Accept these improvements to the design system decision? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -204,7 +204,7 @@ Show the generated design system content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current design system choice
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current design system choice
 - Process the collaborative design system insights that come back
 - Ask user: "Accept these changes to the design system decision? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
--- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md
@@ -29,8 +29,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding

@@ -198,7 +198,7 @@ Show the generated defining experience content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current defining experience content
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current defining experience content
 - Process the enhanced experience insights that come back
 - Ask user: "Accept these improvements to the defining experience? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -206,7 +206,7 @@ Show the generated defining experience content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current defining experience
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current defining experience
 - Process the collaborative experience insights that come back
 - Ask user: "Accept these changes to the defining experience? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
--- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md
@@ -29,8 +29,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding

@@ -168,7 +168,7 @@ Show the generated visual foundation content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current visual foundation content
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current visual foundation content
 - Process the enhanced visual insights that come back
 - Ask user: "Accept these improvements to the visual foundation? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -176,7 +176,7 @@ Show the generated visual foundation content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current visual foundation
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current visual foundation
 - Process the collaborative visual insights that come back
 - Ask user: "Accept these changes to the visual foundation? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
--- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md
@@ -29,8 +29,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding

@@ -168,7 +168,7 @@ Show the generated design direction content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current design direction content
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current design direction content
 - Process the enhanced design insights that come back
 - Ask user: "Accept these improvements to the design direction? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -176,7 +176,7 @@ Show the generated design direction content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current design direction
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current design direction
 - Process the collaborative design insights that come back
 - Ask user: "Accept these changes to the design direction? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
--- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md
@@ -29,8 +29,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding

@@ -186,7 +186,7 @@ Show the generated user journey content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current user journey content
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current user journey content
 - Process the enhanced journey insights that come back
 - Ask user: "Accept these improvements to the user journeys? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -194,7 +194,7 @@ Show the generated user journey content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current user journeys
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current user journeys
 - Process the collaborative journey insights that come back
 - Ask user: "Accept these changes to the user journeys? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
--- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md
@@ -29,8 +29,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding

@@ -192,7 +192,7 @@ Show the generated component strategy content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current component strategy content
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current component strategy content
 - Process the enhanced component insights that come back
 - Ask user: "Accept these improvements to the component strategy? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -200,7 +200,7 @@ Show the generated component strategy content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current component strategy
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current component strategy
 - Process the collaborative component insights that come back
 - Ask user: "Accept these changes to the component strategy? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
--- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md
@@ -29,8 +29,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding

@@ -181,7 +181,7 @@ Show the generated UX patterns content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current UX patterns content
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current UX patterns content
 - Process the enhanced pattern insights that come back
 - Ask user: "Accept these improvements to the UX patterns? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -189,7 +189,7 @@ Show the generated UX patterns content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current UX patterns
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current UX patterns
 - Process the collaborative pattern insights that come back
 - Ask user: "Accept these changes to the UX patterns? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
--- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md
@@ -29,8 +29,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding

@@ -208,7 +208,7 @@ Show the generated responsive and accessibility content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current responsive/accessibility content
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current responsive/accessibility content
 - Process the enhanced insights that come back
 - Ask user: "Accept these improvements to the responsive/accessibility strategy? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -216,7 +216,7 @@ Show the generated responsive and accessibility content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current responsive/accessibility strategy
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current responsive/accessibility strategy
 - Process the collaborative insights that come back
 - Ask user: "Accept these changes to the responsive/accessibility strategy? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
--- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md
@@ -25,7 +25,7 @@ This uses **micro-file architecture** for disciplined execution:

 ### Configuration Loading

-Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:
+Load config from `{project-root}/.bmad/bmm/config.yaml` and resolve:

 - `project_name`, `output_folder`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
@@ -33,7 +33,7 @@ Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:

 ### Paths

- `installed_path` = `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design`
+- `installed_path` = `{project-root}/.bmad/bmm/workflows/2-plan-workflows/create-ux-design`
 - `template_path` = `{installed_path}/ux-design-template.md`
 - `default_output_file` = `{output_folder}/ux-design-specification.md`

--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-01-init.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-01-init.md
@@ -3,7 +3,7 @@ name: 'step-01-init'
 description: 'Initialize the PRD workflow by detecting continuation state and setting up the document'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
+workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd'

 # File References
 thisStepFile: '{workflow_path}/steps/step-01-init.md'
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-01b-continue.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-01b-continue.md
@@ -3,7 +3,7 @@ name: 'step-01b-continue'
 description: 'Resume an interrupted PRD workflow from the last completed step'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
+workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd'

 # File References
 thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-02-discovery.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-02-discovery.md
@@ -3,7 +3,7 @@ name: 'step-02-discovery'
 description: 'Conduct project and domain discovery with data-driven classification'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
+workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd'

 # File References
 thisStepFile: '{workflow_path}/steps/step-02-discovery.md'
@@ -16,8 +16,8 @@ projectTypesCSV: '{workflow_path}/project-types.csv'
 domainComplexityCSV: '{workflow_path}/domain-complexity.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'
 ---

 # Step 2: Project & Domain Discovery
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-03-success.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-03-success.md
@@ -3,7 +3,7 @@ name: 'step-03-success'
 description: 'Define comprehensive success criteria covering user, business, and technical success'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
+workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd'

 # File References
 thisStepFile: '{workflow_path}/steps/step-03-success.md'
@@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/prd.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: Success Criteria Definition
@@ -49,8 +49,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding

@@ -228,7 +228,7 @@ Show the generated content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current success criteria content
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current success criteria content
 - Process the enhanced success metrics that come back
 - Ask user: "Accept these improvements to the success criteria? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -236,7 +236,7 @@ Show the generated content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current success criteria
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current success criteria
 - Process the collaborative improvements to metrics and scope
 - Ask user: "Accept these changes to the success criteria? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-04-journeys.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-04-journeys.md
@@ -3,7 +3,7 @@ name: 'step-04-journeys'
 description: 'Map ALL user types that interact with the system with narrative story-based journeys'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
+workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd'

 # File References
 thisStepFile: '{workflow_path}/steps/step-04-journeys.md'
@@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/prd.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: User Journey Mapping
@@ -49,8 +49,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding

@@ -222,7 +222,7 @@ Show the generated journey content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current journey content
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current journey content
 - Process the enhanced journey insights that come back
 - Ask user: "Accept these improvements to the user journeys? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -230,7 +230,7 @@ Show the generated journey content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current journeys
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current journeys
 - Process the collaborative journey improvements and additions
 - Ask user: "Accept these changes to the user journeys? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -240,7 +240,7 @@ Show the generated journey content and present choices:

 - Append the final content to `{output_folder}/prd.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
- Load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md` (or determine if step is optional based on domain complexity)
+- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md` (or determine if step is optional based on domain complexity)

 ## APPEND TO DOCUMENT:

--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md
@@ -3,7 +3,7 @@ name: 'step-05-domain'
 description: 'Explore domain-specific requirements for complex domains (optional step)'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
+workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd'

 # File References
 thisStepFile: '{workflow_path}/steps/step-05-domain.md'
@@ -15,8 +15,8 @@ outputFile: '{output_folder}/prd.md'
 domainComplexityCSV: '{workflow_path}/domain-complexity.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'
 ---

 # Step 5: Domain-Specific Exploration
@@ -52,8 +52,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding

@@ -71,7 +71,7 @@ Before proceeding with this step, verify:
 - Is `complexity_level` from step-02 equal to "high" and/or does the domain have specific regulatory/compliance needs?
 - Would domain exploration significantly impact the product requirements?

-If NO to these questions, skip this step and load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md`.
+If NO to these questions, skip this step and load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md`.

 ## YOUR TASK:

@@ -83,7 +83,7 @@ Explore domain-specific requirements for complex domains that need specialized c

 Load domain-specific configuration for complex domains:

- Load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/domain-complexity.csv` completely
+- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/domain-complexity.csv` completely
 - Find the row where `domain` matches the detected domain from step-02
 - Extract these columns:
  - `key_concerns` (semicolon-separated list)
@@ -207,7 +207,7 @@ Show the generated domain content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current domain content
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current domain content
 - Process the enhanced domain insights that come back
 - Ask user: "Accept these domain requirement improvements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -215,7 +215,7 @@ Show the generated domain content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current domain requirements
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current domain requirements
 - Process the collaborative domain expertise and validation
 - Ask user: "Accept these changes to domain requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -225,7 +225,7 @@ Show the generated domain content and present choices:

 - Append the content to `{output_folder}/prd.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
- Load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md`
+- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md`

 ## APPEND TO DOCUMENT:

@@ -257,7 +257,7 @@ When user selects 'C', append the content directly to the document using the str

 ## SKIP CONDITIONS:

-Skip this step and load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md` if:
+Skip this step and load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md` if:

 - `complexity_level` from step-02 is not "high"
 - Domain has no specific regulatory/compliance requirements
@@ -265,6 +265,6 @@ Skip this step and load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workf

 ## NEXT STEP:

-After user selects 'C' and content is saved to document, load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md`.
+After user selects 'C' and content is saved to document, load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md`.

 Remember: Do NOT proceed to step-06 until user explicitly selects 'C' from the A/P/C menu and content is saved!
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md
@@ -3,7 +3,7 @@ name: 'step-06-innovation'
 description: 'Detect and explore innovative aspects of the product (optional step)'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
+workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd'

 # File References
 thisStepFile: '{workflow_path}/steps/step-06-innovation.md'
@@ -15,8 +15,8 @@ outputFile: '{output_folder}/prd.md'
 projectTypesCSV: '{workflow_path}/project-types.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'
 ---

 # Step 6: Innovation Discovery
@@ -52,8 +52,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding

@@ -83,7 +83,7 @@ Detect and explore innovation patterns in the product, focusing on what makes it

 Load innovation signals specific to this project type:

- Load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/project-types.csv` completely
+- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/project-types.csv` completely
 - Find the row where `project_type` matches detected type from step-02
 - Extract `innovation_signals` (semicolon-separated list)
 - Extract `web_search_triggers` for potential innovation research
@@ -186,7 +186,7 @@ Show the generated innovation content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current innovation content
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current innovation content
 - Process the enhanced innovation insights that come back
 - Ask user: "Accept these improvements to the innovation analysis? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -194,7 +194,7 @@ Show the generated innovation content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current innovation content
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current innovation content
 - Process the collaborative innovation exploration and ideation
 - Ask user: "Accept these changes to the innovation analysis? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -204,7 +204,7 @@ Show the generated innovation content and present choices:

 - Append the final content to `{output_folder}/prd.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6]`
- Load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`
+- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`

 ## NO INNOVATION DETECTED:

@@ -215,7 +215,7 @@ If no genuine innovation signals are found after exploration:
 [A] Force innovation exploration - Let's try to find innovative angles
 [C] Continue - Skip innovation section and move to Project Type Analysis (Step 7 of 11)"

-If user selects 'A', proceed with content generation anyway. If 'C', skip this step and load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`.
+If user selects 'A', proceed with content generation anyway. If 'C', skip this step and load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`.

 ## APPEND TO DOCUMENT:

@@ -247,7 +247,7 @@ When user selects 'C', append the content directly to the document using the str

 ## SKIP CONDITIONS:

-Skip this step and load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md` if:
+Skip this step and load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md` if:

 - No innovation signals detected in conversation
 - Product is incremental improvement rather than breakthrough
@@ -256,6 +256,6 @@ Skip this step and load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workf

 ## NEXT STEP:

-After user selects 'C' and content is saved to document (or step is skipped), load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`.
+After user selects 'C' and content is saved to document (or step is skipped), load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`.

 Remember: Do NOT proceed to step-07 until user explicitly selects 'C' from the A/P/C menu (or confirms step skip)!
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md
@@ -3,7 +3,7 @@ name: 'step-07-project-type'
 description: 'Conduct project-type specific discovery using CSV-driven guidance'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
+workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd'

 # File References
 thisStepFile: '{workflow_path}/steps/step-07-project-type.md'
@@ -15,8 +15,8 @@ outputFile: '{output_folder}/prd.md'
 projectTypesCSV: '{workflow_path}/project-types.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'
 ---

 # Step 7: Project-Type Deep Dive
@@ -52,8 +52,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding

@@ -74,7 +74,7 @@ Conduct project-type specific discovery using CSV-driven guidance to define tech

 Load project-type specific configuration:

- Load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/project-types.csv` completely
+- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/project-types.csv` completely
 - Find the row where `project_type` matches detected type from step-02
 - Extract these columns:
  - `key_questions` (semicolon-separated list of discovery questions)
@@ -182,7 +182,7 @@ Show the generated project-type content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current project-type content
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current project-type content
 - Process the enhanced technical insights that come back
 - Ask user: "Accept these improvements to the technical requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -190,7 +190,7 @@ Show the generated project-type content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current project-type requirements
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current project-type requirements
 - Process the collaborative technical expertise and validation
 - Ask user: "Accept these changes to the technical requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -200,7 +200,7 @@ Show the generated project-type content and present choices:

 - Append the final content to `{output_folder}/prd.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7]`
- Load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md`
+- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md`

 ## APPEND TO DOCUMENT:

@@ -252,6 +252,6 @@ When user selects 'C', append the content directly to the document using the str

 ## NEXT STEP:

-After user selects 'C' and content is saved to document, load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md` to define project scope.
+After user selects 'C' and content is saved to document, load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md` to define project scope.

 Remember: Do NOT proceed to step-08 (Scoping) until user explicitly selects 'C' from the A/P/C menu and content is saved!
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md
@@ -3,7 +3,7 @@ name: 'step-08-scoping'
 description: 'Define MVP boundaries and prioritize features across development phases'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
+workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd'

 # File References
 thisStepFile: '{workflow_path}/steps/step-08-scoping.md'
@@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/prd.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: Scoping Exercise - MVP & Future Features
@@ -50,8 +50,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding

@@ -243,7 +243,7 @@ Show the scoping decisions and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with current scoping analysis
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with current scoping analysis
 - Process enhanced scoping insights that come back
 - Ask user: "Accept these improvements to the scoping decisions? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -251,7 +251,7 @@ Show the scoping decisions and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with scoping context
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with scoping context
 - Process collaborative insights on MVP and roadmap decisions
 - Ask user: "Accept these changes to the scoping decisions? (y/n)"
 - If yes: Update content, then return to A/P/C menu
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-09-functional.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-09-functional.md
@@ -3,7 +3,7 @@ name: 'step-09-functional'
 description: 'Synthesize all discovery into comprehensive functional requirements'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
+workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd'

 # File References
 thisStepFile: '{workflow_path}/steps/step-09-functional.md'
@@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/prd.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: Functional Requirements Synthesis
@@ -49,8 +49,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding

@@ -209,7 +209,7 @@ Show the generated functional requirements and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current FR list
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current FR list
 - Process the enhanced capability coverage that comes back
 - Ask user: "Accept these additions to the functional requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -217,7 +217,7 @@ Show the generated functional requirements and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current FR list
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current FR list
 - Process the collaborative capability validation and additions
 - Ask user: "Accept these changes to the functional requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -227,7 +227,7 @@ Show the generated functional requirements and present choices:

 - Append the final content to `{output_folder}/prd.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8, 9]`
- Load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md`
+- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md`

 ## APPEND TO DOCUMENT:

@@ -264,6 +264,6 @@ Emphasize to user: "This FR list is now binding. Any feature not listed here wil

 ## NEXT STEP:

-After user selects 'C' and content is saved to document, load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md` to define non-functional requirements.
+After user selects 'C' and content is saved to document, load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md` to define non-functional requirements.

 Remember: Do NOT proceed to step-10 until user explicitly selects 'C' from the A/P/C menu and content is saved!
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md
@@ -3,7 +3,7 @@ name: 'step-10-nonfunctional'
 description: 'Define quality attributes that matter for this specific product'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
+workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd'

 # File References
 thisStepFile: '{workflow_path}/steps/step-10-nonfunctional.md'
@@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/prd.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: Non-Functional Requirements
@@ -49,8 +49,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding

@@ -209,7 +209,7 @@ Show the generated NFR content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current NFR content
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current NFR content
 - Process the enhanced quality attribute insights that come back
 - Ask user: "Accept these improvements to the non-functional requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -217,7 +217,7 @@ Show the generated NFR content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current NFR list
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current NFR list
 - Process the collaborative technical validation and additions
 - Ask user: "Accept these changes to the non-functional requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -227,7 +227,7 @@ Show the generated NFR content and present choices:

 - Append the final content to `{output_folder}/prd.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]`
- Load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md`
+- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md`

 ## APPEND TO DOCUMENT:

@@ -288,6 +288,6 @@ When user selects 'C', append the content directly to the document using the str

 ## NEXT STEP:

-After user selects 'C' and content is saved to document, load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md` to finalize the PRD and complete the workflow.
+After user selects 'C' and content is saved to document, load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md` to finalize the PRD and complete the workflow.

 Remember: Do NOT proceed to step-11 until user explicitly selects 'C' from the A/P/C menu and content is saved!
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md
@@ -3,7 +3,7 @@ name: 'step-11-complete'
 description: 'Complete the PRD workflow, update status files, and suggest next steps'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
+workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd'

 # File References
 thisStepFile: '{workflow_path}/steps/step-11-complete.md'
--- a/src/modules/bmm/workflows/2-plan-workflows/prd/workflow.md
+++ b/src/modules/bmm/workflows/2-plan-workflows/prd/workflow.md
@@ -1,7 +1,7 @@
 ---
 name: create-prd
 description: Creates a comprehensive PRDs through collaborative step-by-step discovery between two product managers working as peers.
-main_config: '{project-root}/{bmad_folder}/bmm/config.yaml'
+main_config: '{project-root}/.bmad/bmm/config.yaml'
 web_bundle: true
 ---

--- a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-02-context.md
+++ b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-02-context.md
@@ -30,8 +30,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding

@@ -169,7 +169,7 @@ Show the generated content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current context analysis
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current context analysis
 - Process the enhanced architectural insights that come back
 - Ask user: "Accept these enhancements to the project context analysis? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -177,7 +177,7 @@ Show the generated content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current project context
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current project context
 - Process the collaborative improvements to architectural understanding
 - Ask user: "Accept these changes to the project context analysis? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
--- a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-03-starter.md
+++ b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-03-starter.md
@@ -30,8 +30,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding

@@ -276,7 +276,7 @@ Show the generated content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with current starter analysis
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with current starter analysis
 - Process enhanced insights about starter options or custom approaches
 - Ask user: "Accept these changes to the starter template evaluation? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -284,7 +284,7 @@ Show the generated content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with starter evaluation context
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with starter evaluation context
 - Process collaborative insights about starter trade-offs
 - Ask user: "Accept these changes to the starter template evaluation? (y/n)"
 - If yes: Update content, then return to A/P/C menu
--- a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-04-decisions.md
+++ b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-04-decisions.md
@@ -31,8 +31,8 @@ This step will generate content and present choices for each decision category:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding

@@ -263,7 +263,7 @@ Show the generated decisions content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with specific decision categories
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with specific decision categories
 - Process enhanced insights about particular decisions
 - Ask user: "Accept these enhancements to the architectural decisions? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -271,7 +271,7 @@ Show the generated decisions content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with architectural decisions context
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with architectural decisions context
 - Process collaborative insights about decision trade-offs
 - Ask user: "Accept these changes to the architectural decisions? (y/n)"
 - If yes: Update content, then return to A/P/C menu
--- a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-05-patterns.md
+++ b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-05-patterns.md
@@ -31,8 +31,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding

@@ -304,7 +304,7 @@ Show the generated patterns content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with current patterns
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with current patterns
 - Process enhanced consistency rules that come back
 - Ask user: "Accept these additional pattern refinements? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -312,7 +312,7 @@ Show the generated patterns content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with implementation patterns context
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with implementation patterns context
 - Process collaborative insights about potential conflicts
 - Ask user: "Accept these changes to the implementation patterns? (y/n)"
 - If yes: Update content, then return to A/P/C menu
--- a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-06-structure.md
+++ b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-06-structure.md
@@ -31,8 +31,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding

@@ -324,7 +324,7 @@ Show the generated project structure content and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with current project structure
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with current project structure
 - Process enhanced organizational insights that come back
 - Ask user: "Accept these changes to the project structure? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -332,7 +332,7 @@ Show the generated project structure content and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with project structure context
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with project structure context
 - Process collaborative insights about organization trade-offs
 - Ask user: "Accept these changes to the project structure? (y/n)"
 - If yes: Update content, then return to A/P/C menu
--- a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-07-validation.md
+++ b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-07-validation.md
@@ -31,8 +31,8 @@ This step will generate content and present choices:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding

@@ -304,7 +304,7 @@ Show the validation results and present choices:

 #### If 'A' (Advanced Elicitation):

- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with validation issues
+- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with validation issues
 - Process enhanced solutions for complex concerns
 - Ask user: "Accept these architectural improvements? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -312,7 +312,7 @@ Show the validation results and present choices:

 #### If 'P' (Party Mode):

- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with validation context
+- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with validation context
 - Process collaborative insights on implementation readiness
 - Ask user: "Accept these changes to the validation results? (y/n)"
 - If yes: Update content, then return to A/P/C menu
--- a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-08-complete.md
+++ b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-08-complete.md
@@ -314,7 +314,7 @@ The workflow will collaborate with you to create an optimized `project_context.m

 **Execute the Generate Project Context workflow:**

- Load and execute: `{project-root}/{bmad_folder}/bmm/workflows/generate-project-context/workflow.md`
+- Load and execute: `{project-root}/.bmad/bmm/workflows/generate-project-context/workflow.md`
 - The workflow will handle discovery, generation, and completion of the project context file
 - After completion, return here for final handoff

--- a/src/modules/bmm/workflows/3-solutioning/architecture/workflow.md
+++ b/src/modules/bmm/workflows/3-solutioning/architecture/workflow.md
@@ -28,7 +28,7 @@ This uses **micro-file architecture** for disciplined execution:

 ### Configuration Loading

-Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:
+Load config from `{project-root}/.bmad/bmm/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}/bmm/config.yaml` and resolve:

 ### Paths

- `installed_path` = `{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture`
+- `installed_path` = `{project-root}/.bmad/bmm/workflows/3-solutioning/architecture`
 - `template_path` = `{installed_path}/architecture-decision-template.md`
 - `data_files_path` = `{installed_path}/data/`

--- a/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md
+++ b/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md
@@ -3,7 +3,7 @@ name: 'step-01-validate-prerequisites'
 description: 'Validate required documents exist and extract all requirements for epic and story creation'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories'
+workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/create-epics-and-stories'

 # File References
 thisStepFile: '{workflow_path}/steps/step-01-validate-prerequisites.md'
--- a/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-02-design-epics.md
+++ b/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-02-design-epics.md
@@ -3,7 +3,7 @@ name: 'step-02-design-epics'
 description: 'Design and approve the epics_list that will organize all requirements into user-value-focused epics'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories'
+workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/create-epics-and-stories'

 # File References
 thisStepFile: '{workflow_path}/steps/step-02-design-epics.md'
--- a/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md
+++ b/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md
@@ -3,7 +3,7 @@ name: 'step-03-create-stories'
 description: 'Generate all epics with their stories following the template structure'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories'
+workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/create-epics-and-stories'

 # File References
 thisStepFile: '{workflow_path}/steps/step-03-create-stories.md'
--- a/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
+++ b/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md
@@ -3,7 +3,7 @@ name: 'step-04-final-validation'
 description: 'Validate complete coverage of all requirements and ensure implementation readiness'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories'
+workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/create-epics-and-stories'

 # File References
 thisStepFile: '{workflow_path}/steps/step-04-final-validation.md'
--- a/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md
+++ b/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/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`

 ### 2. First Step EXECUTION

-Load, read the full file and then execute `{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md` to begin the workflow.
+Load, read the full file and then execute `{project-root}/.bmad/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md` to begin the workflow.
--- a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-01-document-discovery.md
+++ b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-01-document-discovery.md
@@ -3,7 +3,7 @@ name: 'step-01-document-discovery'
 description: 'Discover and inventory all project documents, handling duplicates and organizing file structure'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness'
+workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness'

 # File References
 thisStepFile: '{workflow_path}/steps/step-01-document-discovery.md'
--- a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-02-prd-analysis.md
+++ b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-02-prd-analysis.md
@@ -3,7 +3,7 @@ name: 'step-02-prd-analysis'
 description: 'Read and analyze PRD to extract all FRs and NFRs for coverage validation'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness'
+workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness'

 # File References
 thisStepFile: '{workflow_path}/steps/step-02-prd-analysis.md'
--- a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-03-epic-coverage-validation.md
+++ b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-03-epic-coverage-validation.md
@@ -3,7 +3,7 @@ name: 'step-03-epic-coverage-validation'
 description: 'Validate that all PRD FRs are covered in epics and stories'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness'
+workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness'

 # File References
 thisStepFile: '{workflow_path}/steps/step-03-epic-coverage-validation.md'
@@ -102,11 +102,11 @@ Create coverage matrix:
 ```
 ## FR Coverage Analysis

-| FR Number | PRD Requirement | Epic Coverage | Status |
-|-----------|----------------|---------------|---------|
-| FR1 | [PRD text] | Epic X Story Y | ✓ Covered |
-| FR2 | [PRD text] | **NOT FOUND** | ❌ MISSING |
-| FR3 | [PRD text] | Epic Z Story A | ✓ Covered |
+| FR Number | PRD Requirement | Epic Coverage  | Status    |
+| --------- | --------------- | -------------- | --------- |
+| FR1       | [PRD text]      | Epic X Story Y | ✓ Covered |
+| FR2       | [PRD text]      | **NOT FOUND**  | ❌ MISSING |
+| FR3       | [PRD text]      | Epic Z Story A | ✓ Covered |
 ```

 ### 5. Document Missing Coverage
--- a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-04-ux-alignment.md
+++ b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-04-ux-alignment.md
@@ -3,7 +3,7 @@ name: 'step-04-ux-alignment'
 description: 'Check for UX document and validate alignment with PRD and Architecture'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness'
+workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness'

 # File References
 thisStepFile: '{workflow_path}/steps/step-04-ux-alignment.md'
--- a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-05-epic-quality-review.md
+++ b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-05-epic-quality-review.md
@@ -3,14 +3,14 @@ name: 'step-05-epic-quality-review'
 description: 'Validate epics and stories against create-epics-and-stories best practices'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness'
+workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness'

 # File References
 thisStepFile: '{workflow_path}/steps/step-05-epic-quality-review.md'
 nextStepFile: '{workflow_path}/steps/step-06-final-assessment.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/implementation-readiness-report-{{date}}.md'
-epicsBestPractices: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories'
+epicsBestPractices: '{project-root}/.bmad/bmm/workflows/3-solutioning/create-epics-and-stories'
 ---

 # Step 5: Epic Quality Review
--- a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-06-final-assessment.md
+++ b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-06-final-assessment.md
@@ -3,7 +3,7 @@ name: 'step-06-final-assessment'
 description: 'Compile final assessment and polish the readiness report'

 # Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness'
+workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness'

 # File References
 thisStepFile: '{workflow_path}/steps/step-06-final-assessment.md'
--- a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/workflow.md
+++ b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/workflow.md
@@ -45,7 +45,7 @@ web_bundle: false

 ### 1. Module 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`

--- a/src/modules/bmm/workflows/4-implementation/code-review/instructions.xml
+++ b/src/modules/bmm/workflows/4-implementation/code-review/instructions.xml
@@ -1,5 +1,5 @@
 <workflow>
-  <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} and language MUST be tailored to {user_skill_level}</critical>
  <critical>Generate all documents in {document_output_language}</critical>
--- a/src/modules/bmm/workflows/4-implementation/code-review/workflow.yaml
+++ b/src/modules/bmm/workflows/4-implementation/code-review/workflow.yaml
@@ -4,7 +4,7 @@ description: "Perform an ADVERSARIAL Senior Developer code review that finds 3-1
 author: "BMad"

 # Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -15,7 +15,7 @@ sprint_artifacts: "{config_source}:sprint_artifacts"
 sprint_status: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"

 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/code-review"
+installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/code-review"
 instructions: "{installed_path}/instructions.xml"
 validation: "{installed_path}/checklist.md"
 template: false
--- a/src/modules/bmm/workflows/4-implementation/correct-course/checklist.md
+++ b/src/modules/bmm/workflows/4-implementation/correct-course/checklist.md
@@ -1,6 +1,6 @@
 # Change Navigation Checklist

-<critical>This checklist is executed as part of: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml</critical>
+<critical>This checklist is executed as part of: {project-root}/.bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml</critical>
 <critical>Work through each section systematically with the user, recording findings and impacts</critical>

 <checklist>
--- a/src/modules/bmm/workflows/4-implementation/correct-course/instructions.md
+++ b/src/modules/bmm/workflows/4-implementation/correct-course/instructions.md
@@ -1,7 +1,7 @@
 # Correct Course - Sprint Change Management 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}/bmm/workflows/4-implementation/correct-course/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/bmm/workflows/4-implementation/correct-course/workflow.yaml</critical>
 <critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
 <critical>Generate all documents in {document_output_language}</critical>

--- a/src/modules/bmm/workflows/4-implementation/correct-course/workflow.yaml
+++ b/src/modules/bmm/workflows/4-implementation/correct-course/workflow.yaml
@@ -3,7 +3,7 @@ name: "correct-course"
 description: "Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation"
 author: "BMad Method"

-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -46,7 +46,7 @@ input_file_patterns:
    sharded: "{output_folder}/index.md"
    load_strategy: "INDEX_GUIDED"

-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course"
+installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/correct-course"
 template: false
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
--- a/src/modules/bmm/workflows/4-implementation/create-story/checklist.md
+++ b/src/modules/bmm/workflows/4-implementation/create-story/checklist.md
@@ -33,7 +33,7 @@ This is a COMPETITION to create the **ULTIMATE story context** that makes LLM de

 ### **When Running from Create-Story Workflow:**

- The `{project_root}/{bmad_folder}/core/tasks/validate-workflow.xml` framework will automatically:
+- The `{project_root}/.bmad/core/tasks/validate-workflow.xml` framework will automatically:
  - Load this checklist file
  - Load the newly created story file (`{story_file_path}`)
  - Load workflow variables from `{installed_path}/workflow.yaml`
@@ -63,7 +63,7 @@ You will systematically re-do the entire story creation process, but with a crit

 1. **Load the workflow configuration**: `{installed_path}/workflow.yaml` for variable inclusion
 2. **Load the story file**: `{story_file_path}` (provided by user or discovered)
-3. **Load validation framework**: `{project_root}/{bmad_folder}/core/tasks/validate-workflow.xml`
+3. **Load validation framework**: `{project_root}/.bmad/core/tasks/validate-workflow.xml`
 4. **Extract metadata**: epic_num, story_num, story_key, story_title from story file
 5. **Resolve all workflow variables**: story_dir, output_folder, epics_file, architecture_file, etc.
 6. **Understand current status**: What story implementation guidance is currently provided?
--- a/src/modules/bmm/workflows/4-implementation/create-story/instructions.xml
+++ b/src/modules/bmm/workflows/4-implementation/create-story/instructions.xml
@@ -1,5 +1,5 @@
 <workflow>
-  <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} and generate all documents in {document_output_language}</critical>

@@ -310,7 +310,7 @@
  </step>

  <step n="6" goal="Update sprint status and finalize">
-    <invoke-task>Validate against checklist at {installed_path}/checklist.md using {bmad_folder}/core/tasks/validate-workflow.xml</invoke-task>
+    <invoke-task>Validate against checklist at {installed_path}/checklist.md using .bmad/core/tasks/validate-workflow.xml</invoke-task>
    <action>Save story document unconditionally</action>

    <!-- Update sprint status -->
--- a/src/modules/bmm/workflows/4-implementation/create-story/workflow.yaml
+++ b/src/modules/bmm/workflows/4-implementation/create-story/workflow.yaml
@@ -3,7 +3,7 @@ description: "Create the next user story from epics+stories with enhanced contex
 author: "BMad"

 # Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ sprint_artifacts: "{config_source}:sprint_artifacts"
 story_dir: "{sprint_artifacts}"

 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story"
+installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/create-story"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.xml"
 validation: "{installed_path}/checklist.md"
--- a/src/modules/bmm/workflows/4-implementation/dev-story/instructions.xml
+++ b/src/modules/bmm/workflows/4-implementation/dev-story/instructions.xml
@@ -1,5 +1,5 @@
 <workflow>
-  <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} and language MUST be tailored to {user_skill_level}</critical>
  <critical>Generate all documents in {document_output_language}</critical>
--- a/src/modules/bmm/workflows/4-implementation/dev-story/workflow.yaml
+++ b/src/modules/bmm/workflows/4-implementation/dev-story/workflow.yaml
@@ -3,7 +3,7 @@ description: "Execute a story by implementing tasks/subtasks, writing tests, val
 author: "BMad"

 # Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -13,7 +13,7 @@ story_dir: "{config_source}:sprint_artifacts"
 date: system-generated

 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/dev-story"
+installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/dev-story"
 instructions: "{installed_path}/instructions.xml"
 validation: "{installed_path}/checklist.md"

--- a/src/modules/bmm/workflows/4-implementation/retrospective/instructions.md
+++ b/src/modules/bmm/workflows/4-implementation/retrospective/instructions.md
@@ -1,7 +1,7 @@
 # Retrospective - Epic Completion Review 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}/bmm/workflows/4-implementation/retrospective/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/bmm/workflows/4-implementation/retrospective/workflow.yaml</critical>
 <critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
 <critical>Generate all documents in {document_output_language}</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>
--- a/src/modules/bmm/workflows/4-implementation/retrospective/workflow.yaml
+++ b/src/modules/bmm/workflows/4-implementation/retrospective/workflow.yaml
@@ -3,7 +3,7 @@ name: "retrospective"
 description: "Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic"
 author: "BMad"

-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,12 +12,12 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated
 sprint_artifacts: "{config_source}:sprint_artifacts"

-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/retrospective"
+installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/retrospective"
 template: false
 instructions: "{installed_path}/instructions.md"

 required_inputs:
-  - agent_manifest: "{project-root}/{bmad_folder}/_cfg/agent-manifest.csv"
+  - agent_manifest: "{project-root}/.bmad/_cfg/agent-manifest.csv"

 # Smart input file references - handles both whole docs and sharded docs
 # Priority: Whole document first, then sharded version
--- a/src/modules/bmm/workflows/4-implementation/sprint-planning/instructions.md
+++ b/src/modules/bmm/workflows/4-implementation/sprint-planning/instructions.md
@@ -1,7 +1,7 @@
 # Sprint Planning - Sprint Status Generator

-<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}/bmm/workflows/4-implementation/sprint-planning/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/bmm/workflows/4-implementation/sprint-planning/workflow.yaml</critical>

 ## 📚 Document Discovery - Full Epic Loading

--- a/src/modules/bmm/workflows/4-implementation/sprint-planning/workflow.yaml
+++ b/src/modules/bmm/workflows/4-implementation/sprint-planning/workflow.yaml
@@ -3,7 +3,7 @@ description: "Generate and manage the sprint status tracking file for Phase 4 im
 author: "BMad"

 # Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -11,7 +11,7 @@ date: system-generated
 sprint_artifacts: "{config_source}:sprint_artifacts"

 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-planning"
+installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/sprint-planning"
 instructions: "{installed_path}/instructions.md"
 template: "{installed_path}/sprint-status-template.yaml"
 validation: "{installed_path}/checklist.md"
--- a/src/modules/bmm/workflows/4-implementation/sprint-status/instructions.md
+++ b/src/modules/bmm/workflows/4-implementation/sprint-status/instructions.md
@@ -1,7 +1,7 @@
 # Sprint Status - Multi-Mode Service

-<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}/bmm/workflows/4-implementation/sprint-status/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/bmm/workflows/4-implementation/sprint-status/workflow.yaml</critical>
 <critical>Modes: interactive (default), validate, data</critical>
 <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES. Do NOT mention hours, days, weeks, or timelines.</critical>

--- a/src/modules/bmm/workflows/4-implementation/sprint-status/workflow.yaml
+++ b/src/modules/bmm/workflows/4-implementation/sprint-status/workflow.yaml
@@ -4,7 +4,7 @@ description: "Summarize sprint-status.yaml, surface risks, and route to the righ
 author: "BMad"

 # Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -13,7 +13,7 @@ date: system-generated
 sprint_artifacts: "{config_source}:sprint_artifacts"

 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-status"
+installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/sprint-status"
 instructions: "{installed_path}/instructions.md"

 # Inputs
--- a/src/modules/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml
+++ b/src/modules/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml
@@ -4,7 +4,7 @@ description: "Conversational spec engineering - ask questions, investigate code,
 author: "BMad"

 # Config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 sprint_artifacts: "{config_source}:sprint_artifacts"
 user_name: "{config_source}:user_name"
@@ -14,13 +14,13 @@ user_skill_level: "{config_source}:user_skill_level"
 date: system-generated

 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/bmad-quick-flow/create-tech-spec"
+installed_path: "{project-root}/.bmad/bmm/workflows/bmad-quick-flow/create-tech-spec"
 instructions: "{installed_path}/instructions.md"

 # Related workflows
-quick_dev_workflow: "{project-root}/{bmad_folder}/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml"
-party_mode_exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
-advanced_elicitation: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
+quick_dev_workflow: "{project-root}/.bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml"
+party_mode_exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
+advanced_elicitation: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"

 standalone: true
 web_bundle: false
--- a/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml
+++ b/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml
@@ -4,7 +4,7 @@ description: "Flexible development - execute tech-specs OR direct instructions w
 author: "BMad"

 # Config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 sprint_artifacts: "{config_source}:sprint_artifacts"
 user_name: "{config_source}:user_name"
@@ -16,18 +16,18 @@ date: system-generated
 project_context: "**/project-context.md"

 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/bmad-quick-flow/quick-dev"
+installed_path: "{project-root}/.bmad/bmm/workflows/bmad-quick-flow/quick-dev"
 instructions: "{installed_path}/instructions.md"
 checklist: "{installed_path}/checklist.md"

 # Related workflows
-create_tech_spec_workflow: "{project-root}/{bmad_folder}/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml"
-party_mode_exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
-advanced_elicitation: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
+create_tech_spec_workflow: "{project-root}/.bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml"
+party_mode_exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
+advanced_elicitation: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"

 # Routing resources (lazy-loaded)
-project_levels: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/project-levels.yaml"
-workflow_init: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/init/workflow.yaml"
+project_levels: "{project-root}/.bmad/bmm/workflows/workflow-status/project-levels.yaml"
+workflow_init: "{project-root}/.bmad/bmm/workflows/workflow-status/init/workflow.yaml"

 standalone: true
 web_bundle: false
--- a/src/modules/bmm/workflows/diagrams/create-dataflow/instructions.md
+++ b/src/modules/bmm/workflows/diagrams/create-dataflow/instructions.md
@@ -1,7 +1,7 @@
 # Create Data Flow Diagram - Workflow Instructions

 ```xml
-<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>This workflow creates data flow diagrams (DFD) in Excalidraw format.</critical>

--- a/src/modules/bmm/workflows/diagrams/create-dataflow/workflow.yaml
+++ b/src/modules/bmm/workflows/diagrams/create-dataflow/workflow.yaml
@@ -3,18 +3,18 @@ description: "Create data flow diagrams (DFD) in Excalidraw format"
 author: "BMad"

 # Config values
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"

 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-dataflow"
-shared_path: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/_shared"
+installed_path: "{project-root}/.bmad/bmm/workflows/diagrams/create-dataflow"
+shared_path: "{project-root}/.bmad/bmm/workflows/diagrams/_shared"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

 # Core Excalidraw resources (universal knowledge)
-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 resources (technical diagrams)
 templates: "{shared_path}/excalidraw-templates.yaml"
--- a/src/modules/bmm/workflows/diagrams/create-diagram/instructions.md
+++ b/src/modules/bmm/workflows/diagrams/create-diagram/instructions.md
@@ -1,7 +1,7 @@
 # Create Diagram - Workflow Instructions

 ```xml
-<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>This workflow creates system architecture diagrams, ERDs, UML diagrams, or general technical diagrams in Excalidraw format.</critical>

@@ -134,7 +134,7 @@
  </step>

  <step n="10" goal="Validate Content">
-    <invoke-task>Validate against {{validation}} using {{bmad_folder}}/core/tasks/validate-workflow.xml</invoke-task>
+    <invoke-task>Validate against {{validation}} using {.bmad}/core/tasks/validate-workflow.xml</invoke-task>
  </step>

 </workflow>
--- a/src/modules/bmm/workflows/diagrams/create-diagram/workflow.yaml
+++ b/src/modules/bmm/workflows/diagrams/create-diagram/workflow.yaml
@@ -3,18 +3,18 @@ description: "Create system architecture diagrams, ERDs, UML diagrams, or genera
 author: "BMad"

 # Config values
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"

 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-diagram"
-shared_path: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/_shared"
+installed_path: "{project-root}/.bmad/bmm/workflows/diagrams/create-diagram"
+shared_path: "{project-root}/.bmad/bmm/workflows/diagrams/_shared"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

 # Core Excalidraw resources (universal knowledge)
-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 resources (technical diagrams)
 templates: "{shared_path}/excalidraw-templates.yaml"
--- a/src/modules/bmm/workflows/diagrams/create-flowchart/instructions.md
+++ b/src/modules/bmm/workflows/diagrams/create-flowchart/instructions.md
@@ -1,7 +1,7 @@
 # Create Flowchart - Workflow Instructions

 ```xml
-<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>This workflow creates a flowchart visualization in Excalidraw format for processes, pipelines, or logic flows.</critical>

@@ -234,7 +234,7 @@
  </step>

  <step n="9" goal="Validate Content">
-    <invoke-task>Validate against checklist at {{validation}} using {{bmad_folder}}/core/tasks/validate-workflow.xml</invoke-task>
+    <invoke-task>Validate against checklist at {{validation}} using {.bmad}/core/tasks/validate-workflow.xml</invoke-task>
  </step>

 </workflow>
--- a/src/modules/bmm/workflows/diagrams/create-flowchart/workflow.yaml
+++ b/src/modules/bmm/workflows/diagrams/create-flowchart/workflow.yaml
@@ -3,18 +3,18 @@ description: "Create a flowchart visualization in Excalidraw format for processe
 author: "BMad"

 # Config values
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"

 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-flowchart"
-shared_path: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/_shared"
+installed_path: "{project-root}/.bmad/bmm/workflows/diagrams/create-flowchart"
+shared_path: "{project-root}/.bmad/bmm/workflows/diagrams/_shared"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

 # Core Excalidraw resources (universal knowledge)
-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 resources (technical diagrams)
 templates: "{shared_path}/excalidraw-templates.yaml"
--- a/src/modules/bmm/workflows/diagrams/create-wireframe/instructions.md
+++ b/src/modules/bmm/workflows/diagrams/create-wireframe/instructions.md
@@ -1,7 +1,7 @@
 # Create Wireframe - Workflow Instructions

 ```xml
-<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>This workflow creates website or app wireframes in Excalidraw format.</critical>

--- a/src/modules/bmm/workflows/diagrams/create-wireframe/workflow.yaml
+++ b/src/modules/bmm/workflows/diagrams/create-wireframe/workflow.yaml
@@ -3,18 +3,18 @@ description: "Create website or app wireframes in Excalidraw format"
 author: "BMad"

 # Config values
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"

 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-wireframe"
-shared_path: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/_shared"
+installed_path: "{project-root}/.bmad/bmm/workflows/diagrams/create-wireframe"
+shared_path: "{project-root}/.bmad/bmm/workflows/diagrams/_shared"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

 # Core Excalidraw resources (universal knowledge)
-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 resources (technical diagrams)
 templates: "{shared_path}/excalidraw-templates.yaml"
--- a/src/modules/bmm/workflows/document-project/instructions.md
+++ b/src/modules/bmm/workflows/document-project/instructions.md
@@ -1,7 +1,7 @@
 # Document Project Workflow Router

-<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}/bmm/workflows/document-project/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/bmm/workflows/document-project/workflow.yaml</critical>
 <critical>Communicate all responses in {communication_language}</critical>

 <workflow>
@@ -10,7 +10,7 @@

 <step n="1" goal="Validate workflow and get project info">

-<invoke-workflow path="{project-root}/{bmad_folder}/bmm/workflows/workflow-status">
+<invoke-workflow path="{project-root}/.bmad/bmm/workflows/workflow-status">
  <param>mode: data</param>
  <param>data_request: project_config</param>
 </invoke-workflow>
@@ -36,7 +36,7 @@
  </check>

  <!-- Now validate sequencing -->
-  <invoke-workflow path="{project-root}/{bmad_folder}/bmm/workflows/workflow-status">
+  <invoke-workflow path="{project-root}/.bmad/bmm/workflows/workflow-status">
    <param>mode: validate</param>
    <param>calling_workflow: document-project</param>
  </invoke-workflow>
@@ -179,7 +179,7 @@ Your choice [1/2/3]:
 <step n="4" goal="Update status and complete">

 <check if="status_file_found == true">
-  <invoke-workflow path="{project-root}/{bmad_folder}/bmm/workflows/workflow-status">
+  <invoke-workflow path="{project-root}/.bmad/bmm/workflows/workflow-status">
    <param>mode: update</param>
    <param>action: complete_workflow</param>
    <param>workflow_name: document-project</param>
--- a/src/modules/bmm/workflows/document-project/workflow.yaml
+++ b/src/modules/bmm/workflows/document-project/workflow.yaml
@@ -5,7 +5,7 @@ description: "Analyzes and documents brownfield projects by scanning codebase, a
 author: "BMad"

 # Critical variables
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -14,7 +14,7 @@ user_skill_level: "{config_source}:user_skill_level"
 date: system-generated

 # Module path and component files
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/document-project"
+installed_path: "{project-root}/.bmad/bmm/workflows/document-project"
 template: false # This is an action workflow with multiple output files
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
--- a/src/modules/bmm/workflows/document-project/workflows/deep-dive.yaml
+++ b/src/modules/bmm/workflows/document-project/workflows/deep-dive.yaml
@@ -4,22 +4,22 @@ description: "Exhaustive deep-dive documentation of specific project areas"
 author: "BMad"

 # This is a sub-workflow called by document-project/workflow.yaml
-parent_workflow: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml"
+parent_workflow: "{project-root}/.bmad/bmm/workflows/document-project/workflow.yaml"

 # Critical variables inherited from parent
-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"
 date: system-generated

 # Module path and component files
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflows"
+installed_path: "{project-root}/.bmad/bmm/workflows/document-project/workflows"
 template: false # Action workflow
 instructions: "{installed_path}/deep-dive-instructions.md"
-validation: "{project-root}/{bmad_folder}/bmm/workflows/document-project/checklist.md"
+validation: "{project-root}/.bmad/bmm/workflows/document-project/checklist.md"

 # Templates
-deep_dive_template: "{project-root}/{bmad_folder}/bmm/workflows/document-project/templates/deep-dive-template.md"
+deep_dive_template: "{project-root}/.bmad/bmm/workflows/document-project/templates/deep-dive-template.md"

 # Runtime inputs (passed from parent workflow)
 workflow_mode: "deep_dive"
--- a/src/modules/bmm/workflows/document-project/workflows/full-scan.yaml
+++ b/src/modules/bmm/workflows/document-project/workflows/full-scan.yaml
@@ -4,22 +4,22 @@ description: "Complete project documentation workflow (initial scan or full resc
 author: "BMad"

 # This is a sub-workflow called by document-project/workflow.yaml
-parent_workflow: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml"
+parent_workflow: "{project-root}/.bmad/bmm/workflows/document-project/workflow.yaml"

 # Critical variables inherited from parent
-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"
 date: system-generated

 # Data files
-documentation_requirements_csv: "{project-root}/{bmad_folder}/bmm/workflows/document-project/documentation-requirements.csv"
+documentation_requirements_csv: "{project-root}/.bmad/bmm/workflows/document-project/documentation-requirements.csv"

 # Module path and component files
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflows"
+installed_path: "{project-root}/.bmad/bmm/workflows/document-project/workflows"
 template: false # Action workflow
 instructions: "{installed_path}/full-scan-instructions.md"
-validation: "{project-root}/{bmad_folder}/bmm/workflows/document-project/checklist.md"
+validation: "{project-root}/.bmad/bmm/workflows/document-project/checklist.md"

 # Runtime inputs (passed from parent workflow)
 workflow_mode: "" # "initial_scan" or "full_rescan"
--- a/src/modules/bmm/workflows/generate-project-context/steps/step-02-generate.md
+++ b/src/modules/bmm/workflows/generate-project-context/steps/step-02-generate.md
@@ -28,8 +28,8 @@ This step will generate content and present choices for each rule category:

 ## PROTOCOL INTEGRATION:

- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode
+- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding

--- a/src/modules/bmm/workflows/generate-project-context/workflow.md
+++ b/src/modules/bmm/workflows/generate-project-context/workflow.md
@@ -27,7 +27,7 @@ This uses **micro-file architecture** for disciplined execution:

 ### Configuration Loading

-Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:
+Load config from `{project-root}/.bmad/bmm/config.yaml` and resolve:

 - `project_name`, `output_folder`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
@@ -35,7 +35,7 @@ Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:

 ### Paths

- `installed_path` = `{project-root}/{bmad_folder}/bmm/workflows/generate-project-context`
+- `installed_path` = `{project-root}/.bmad/bmm/workflows/generate-project-context`
 - `template_path` = `{installed_path}/project-context-template.md`
 - `output_file` = `{output_folder}/project_context.md`

--- a/src/modules/bmm/workflows/testarch/atdd/instructions.md
+++ b/src/modules/bmm/workflows/testarch/atdd/instructions.md
@@ -2,7 +2,7 @@

 # Acceptance Test-Driven Development (ATDD)

-**Workflow ID**: `{bmad_folder}/bmm/testarch/atdd`
+**Workflow ID**: `.bmad/bmm/testarch/atdd`
 **Version**: 4.0 (BMad v6)

 ---
@@ -54,7 +54,7 @@ Generates failing acceptance tests BEFORE implementation following TDD's red-gre

 5. **Load Knowledge Base Fragments**

-   **Critical:** Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` to load:
+   **Critical:** Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` to load:

   **Core Patterns (Always load):**
   - `data-factories.md` - Factory patterns using faker (override patterns, nested factories, API seeding, 498 lines, 5 examples)
--- a/src/modules/bmm/workflows/testarch/atdd/workflow.yaml
+++ b/src/modules/bmm/workflows/testarch/atdd/workflow.yaml
@@ -4,7 +4,7 @@ description: "Generate failing acceptance tests before implementation using TDD
 author: "BMad"

 # Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated

 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/atdd"
+installed_path: "{project-root}/.bmad/bmm/workflows/testarch/atdd"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 template: "{installed_path}/atdd-checklist-template.md"
--- a/src/modules/bmm/workflows/testarch/automate/instructions.md
+++ b/src/modules/bmm/workflows/testarch/automate/instructions.md
@@ -2,7 +2,7 @@

 # Test Automation Expansion

-**Workflow ID**: `{bmad_folder}/bmm/testarch/automate`
+**Workflow ID**: `.bmad/bmm/testarch/automate`
 **Version**: 4.0 (BMad v6)

 ---
@@ -87,7 +87,7 @@ Expands test automation coverage by generating comprehensive test suites at appr

 6. **Load Knowledge Base Fragments**

-   **Critical:** Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` to load:
+   **Critical:** Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` to load:

   **Core Testing Patterns (Always load):**
   - `test-levels-framework.md` - Test level selection (E2E vs API vs Component vs Unit with decision matrix, 467 lines, 4 examples)
--- a/src/modules/bmm/workflows/testarch/automate/workflow.yaml
+++ b/src/modules/bmm/workflows/testarch/automate/workflow.yaml
@@ -4,7 +4,7 @@ description: "Expand test automation coverage after implementation or analyze ex
 author: "BMad"

 # Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated

 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/automate"
+installed_path: "{project-root}/.bmad/bmm/workflows/testarch/automate"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 template: false
--- a/src/modules/bmm/workflows/testarch/ci/instructions.md
+++ b/src/modules/bmm/workflows/testarch/ci/instructions.md
@@ -2,7 +2,7 @@

 # CI/CD Pipeline Setup

-**Workflow ID**: `{bmad_folder}/bmm/testarch/ci`
+**Workflow ID**: `.bmad/bmm/testarch/ci`
 **Version**: 4.0 (BMad v6)

 ---
--- a/src/modules/bmm/workflows/testarch/ci/workflow.yaml
+++ b/src/modules/bmm/workflows/testarch/ci/workflow.yaml
@@ -4,7 +4,7 @@ description: "Scaffold CI/CD quality pipeline with test execution, burn-in loops
 author: "BMad"

 # Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated

 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/ci"
+installed_path: "{project-root}/.bmad/bmm/workflows/testarch/ci"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

--- a/src/modules/bmm/workflows/testarch/framework/instructions.md
+++ b/src/modules/bmm/workflows/testarch/framework/instructions.md
@@ -2,7 +2,7 @@

 # Test Framework Setup

-**Workflow ID**: `{bmad_folder}/bmm/testarch/framework`
+**Workflow ID**: `.bmad/bmm/testarch/framework`
 **Version**: 4.0 (BMad v6)

 ---
@@ -355,7 +355,7 @@ Read `{config_source}` and check `config.tea_use_playwright_utils`.

 **If `config.tea_use_playwright_utils: true` (Playwright Utils Integration):**

-Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` and load:
+Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` and load:

 - `overview.md` - Playwright utils installation and design principles
 - `fixtures-composition.md` - mergeTests composition with playwright-utils
@@ -375,7 +375,7 @@ Recommend adding burn-in and network-error-monitor to merged fixtures for enhanc

 **If `config.tea_use_playwright_utils: false` (Traditional Patterns):**

-Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` and load:
+Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` and load:

 - `fixture-architecture.md` - Pure function → fixture → `mergeTests` composition with auto-cleanup (406 lines, 5 examples)
 - `data-factories.md` - Faker-based factories with overrides, nested factories, API seeding, auto-cleanup (498 lines, 5 examples)
--- a/src/modules/bmm/workflows/testarch/framework/workflow.yaml
+++ b/src/modules/bmm/workflows/testarch/framework/workflow.yaml
@@ -4,7 +4,7 @@ description: "Initialize production-ready test framework architecture (Playwrigh
 author: "BMad"

 # Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated

 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/framework"
+installed_path: "{project-root}/.bmad/bmm/workflows/testarch/framework"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

--- a/src/modules/bmm/workflows/testarch/nfr-assess/instructions.md
+++ b/src/modules/bmm/workflows/testarch/nfr-assess/instructions.md
@@ -50,7 +50,7 @@ This workflow performs a comprehensive assessment of non-functional requirements

 **Actions:**

-1. Load relevant knowledge fragments from `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv`:
+1. Load relevant knowledge fragments from `{project-root}/.bmad/bmm/testarch/tea-index.csv`:
   - `nfr-criteria.md` - Non-functional requirements criteria and thresholds (security, performance, reliability, maintainability with code examples, 658 lines, 4 examples)
   - `ci-burn-in.md` - CI/CD burn-in patterns for reliability validation (10-iteration detection, sharding, selective execution, 678 lines, 4 examples)
   - `test-quality.md` - Test quality expectations for maintainability (deterministic, isolated, explicit assertions, length/time limits, 658 lines, 5 examples)
--- a/src/modules/bmm/workflows/testarch/nfr-assess/workflow.yaml
+++ b/src/modules/bmm/workflows/testarch/nfr-assess/workflow.yaml
@@ -4,7 +4,7 @@ description: "Assess non-functional requirements (performance, security, reliabi
 author: "BMad"

 # Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated

 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/nfr-assess"
+installed_path: "{project-root}/.bmad/bmm/workflows/testarch/nfr-assess"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 template: "{installed_path}/nfr-report-template.md"
--- a/src/modules/bmm/workflows/testarch/test-design/instructions.md
+++ b/src/modules/bmm/workflows/testarch/test-design/instructions.md
@@ -2,7 +2,7 @@

 # Test Design and Risk Assessment

-**Workflow ID**: `{bmad_folder}/bmm/testarch/test-design`
+**Workflow ID**: `.bmad/bmm/testarch/test-design`
 **Version**: 4.0 (BMad v6)

 ---
@@ -74,7 +74,7 @@ The workflow auto-detects which mode to use based on project phase.

 3. **Load Knowledge Base Fragments (System-Level)**

-   **Critical:** Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` to load:
+   **Critical:** Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` to load:
   - `nfr-criteria.md` - NFR validation approach (security, performance, reliability, maintainability)
   - `test-levels-framework.md` - Test levels strategy guidance
   - `risk-governance.md` - Testability risk identification
@@ -108,7 +108,7 @@ The workflow auto-detects which mode to use based on project phase.

 4. **Load Knowledge Base Fragments (Epic-Level)**

-   **Critical:** Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` to load:
+   **Critical:** Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` to load:
   - `risk-governance.md` - Risk classification framework (6 categories: TECH, SEC, PERF, DATA, BUS, OPS), automated scoring, gate decision engine, owner tracking (625 lines, 4 examples)
   - `probability-impact.md` - Risk scoring methodology (probability × impact matrix, automated classification, dynamic re-assessment, gate integration, 604 lines, 4 examples)
   - `test-levels-framework.md` - Test level selection guidance (E2E vs API vs Component vs Unit with decision matrix, characteristics, when to use each, 467 lines, 4 examples)
--- a/src/modules/bmm/workflows/testarch/test-design/test-design-template.md
+++ b/src/modules/bmm/workflows/testarch/test-design/test-design-template.md
@@ -281,5 +281,5 @@
 ---

 **Generated by**: BMad TEA Agent - Test Architect Module
-**Workflow**: `{bmad_folder}/bmm/testarch/test-design`
+**Workflow**: `.bmad/bmm/testarch/test-design`
 **Version**: 4.0 (BMad v6)
--- a/src/modules/bmm/workflows/testarch/test-design/workflow.yaml
+++ b/src/modules/bmm/workflows/testarch/test-design/workflow.yaml
@@ -4,7 +4,7 @@ description: "Dual-mode workflow: (1) System-level testability review in Solutio
 author: "BMad"

 # Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated

 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/test-design"
+installed_path: "{project-root}/.bmad/bmm/workflows/testarch/test-design"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 template: "{installed_path}/test-design-template.md"
--- a/Show More
+++ b/Show More