bmad-method 6.0.0-alpha.6 → 6.0.0-alpha.8

package/{bmad → .bmad}/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/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>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>
 

package/{bmad → .bmad}/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/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 @@ user_skill_level: "{config_source}:user_skill_level"
 document_output_language: "{config_source}:document_output_language"
 date: system-generated
 
-installed_path: "{project-root}/bmad/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"

package/{bmad → .bmad}/bmm/workflows/4-implementation/create-story/instructions.md

@@ -1,7 +1,7 @@
 # Create Story - Workflow Instructions (Spec-compliant, non-interactive by default)
 
 ````xml
-<critical>The workflow execution engine is governed by: {project_root}/bmad/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>Generate all documents in {document_output_language}</critical>
 <critical>This workflow creates or updates the next user story from epics/PRD and architecture context, saving to the configured stories directory and optionally invoking Story Context.</critical>
@@ -39,7 +39,7 @@
 <workflow>
 
   <step n="1" goal="Load config and initialize">
-    <action>Resolve variables from config_source: story_dir (dev_story_location), output_folder, user_name, communication_language. If story_dir missing and {{non_interactive}} == false → ASK user to provide a stories directory and update variable. If {{non_interactive}} == true and missing, HALT with a clear message.</action>
+    <action>Resolve variables from config_source: story_dir (dev_ephemeral_location), output_folder, user_name, communication_language. If story_dir missing and {{non_interactive}} == false → ASK user to provide a stories directory and update variable. If {{non_interactive}} == true and missing, HALT with a clear message.</action>
     <action>Create {{story_dir}} if it does not exist</action>
     <action>Resolve installed component paths from workflow.yaml: template, instructions, validation</action>
     <action>Resolve recommended inputs if present: epics_file, prd_file, architecture_file</action>
@@ -240,7 +240,7 @@ Will update existing story file rather than creating new one.
   </step>
 
   <step n="8" goal="Validate, save, and mark story drafted" tag="sprint-status">
-    <invoke-task>Validate against checklist at {installed_path}/checklist.md using bmad/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 document unconditionally (non-interactive default). In interactive mode, allow user confirmation.</action>
 
     <!-- Mark story as drafted in sprint status -->

package/{bmad → .bmad}/bmm/workflows/4-implementation/create-story/workflow.yaml

@@ -3,21 +3,21 @@ description: "Create the next user story markdown from epics/PRD and architectur
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/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"
 date: system-generated
 
 # Workflow components
-installed_path: "{project-root}/bmad/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.md"
 validation: "{installed_path}/checklist.md"
 
 # Variables and inputs
 variables:
-  story_dir: "{config_source}:dev_story_location" # Directory where stories are stored
+  story_dir: "{config_source}:dev_ephemeral_location" # Directory where stories are stored
   epics_file: "{output_folder}/epics.md" # Preferred source for epic/story breakdown
   prd_file: "{output_folder}/PRD.md" # Fallback for requirements
   architecture_file: "{output_folder}/architecture.md" # Optional architecture context

package/{bmad → .bmad}/bmm/workflows/4-implementation/dev-story/AUDIT-REPORT.md

@@ -26,7 +26,7 @@ The dev-story workflow is well-structured and follows most BMAD v6 standards. Th
 
 The workflow.yaml contains all required standard config variables:
 
-- ✓ `config_source: "{project-root}/bmad/bmm/config.yaml"` - Correctly defined
+- ✓ `config_source: "{project-root}/.bmad/bmm/config.yaml"` - Correctly defined
 - ✓ `output_folder: "{config_source}:output_folder"` - Pulls from config_source
 - ✓ `user_name: "{config_source}:user_name"` - Pulls from config_source
 - ✓ `communication_language: "{config_source}:communication_language"` - Pulls from config_source
@@ -67,7 +67,7 @@ These variables appear to be pulling from config.yaml but are not explicitly def
 
 ### Unused Variables (Bloat)
 
-1. **context_path** - Defined as `"{config_source}:dev_story_location"` but never used. This duplicates `story_dir` functionality.
+1. **context_path** - Defined as `"{config_source}:dev_ephemeral_location"` but never used. This duplicates `story_dir` functionality.
 
 ---
 
@@ -140,7 +140,7 @@ The workflow correctly sets `web_bundle: false`. This is the expected configurat
 ### Unused YAML Fields
 
 1. **context_path** (line 11 in workflow.yaml)
-   - Defined as: `"{config_source}:dev_story_location"`
+   - Defined as: `"{config_source}:dev_ephemeral_location"`
    - Never referenced in instructions.md
    - Duplicates functionality of `story_dir` variable
    - **Recommendation:** Remove this variable as `story_dir` serves the same purpose

package/{bmad → .bmad}/bmm/workflows/4-implementation/dev-story/instructions.md

@@ -1,7 +1,7 @@
 # Develop Story - Workflow Instructions
 
 ```xml
-<critical>The workflow execution engine is governed by: {project-root}/bmad/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>
@@ -227,7 +227,7 @@ Story is marked Ready for Review in file, but sprint-status.yaml may be out of s
   </step>
 
   <step n="7" goal="Completion communication and user support">
-    <action>Optionally run the workflow validation task against the story using {project-root}/bmad/core/tasks/validate-workflow.xml</action>
+    <action>Optionally run the workflow validation task against the story using {project-root}/.bmad/core/tasks/validate-workflow.xml</action>
     <action>Prepare a concise summary in Dev Agent Record → Completion Notes</action>
 
     <action>Communicate to {user_name} that story implementation is complete and ready for review</action>

package/{bmad → .bmad}/bmm/workflows/4-implementation/dev-story/workflow.yaml

@@ -3,13 +3,13 @@ description: "Execute a story by implementing tasks/subtasks, writing tests, val
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/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"
 user_skill_level: "{config_source}:user_skill_level"
 document_output_language: "{config_source}:document_output_language"
-story_dir: "{config_source}:dev_story_location"
+story_dir: "{config_source}:dev_ephemeral_location"
 run_until_complete: "{config_source}:run_until_complete"
 run_tests_command: "{config_source}:run_tests_command"
 date: system-generated
@@ -19,7 +19,7 @@ story_file: "" # Explicit story path; auto-discovered if empty
 context_file: "{story_dir}/{{story_key}}.context.xml"
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/dev-story"
+installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/dev-story"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 

package/{bmad → .bmad}/bmm/workflows/4-implementation/epic-tech-context/checklist.md

@@ -1,7 +1,7 @@
 # Tech Spec Validation Checklist
 
 ```xml
-<checklist id="bmad/bmm/workflows/4-implementation/epic-tech-context/checklist">
+<checklist id=".bmad/bmm/workflows/4-implementation/epic-tech-context/checklist">
   <item>Overview clearly ties to PRD goals</item>
   <item>Scope explicitly lists in-scope and out-of-scope</item>
   <item>Design lists all services/modules with responsibilities</item>

package/{bmad → .bmad}/bmm/workflows/4-implementation/epic-tech-context/instructions.md

@@ -1,7 +1,7 @@
 <!-- BMAD BMM Tech Spec Workflow Instructions (v6) -->
 
 ```xml
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
+<critical>The workflow execution engine is governed by: {project_root}/.bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
 <critical>Communicate all responses in {communication_language}</critical>
 <critical>This workflow generates a comprehensive Technical Specification from PRD and Architecture, including detailed design, NFRs, acceptance criteria, and traceability mapping.</critical>
@@ -157,7 +157,7 @@ Continuing to regenerate tech spec...
   </step>
 
   <step n="9" goal="Validate and mark epic contexted" tag="sprint-status">
-    <invoke-task>Validate against checklist at {installed_path}/checklist.md using bmad/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>
 
     <!-- Mark epic as contexted -->
     <action>Load the FULL file: {{output_folder}}/sprint-status.yaml</action>

package/{bmad → .bmad}/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml

@@ -3,7 +3,7 @@ description: "Generate a comprehensive Technical Specification from PRD and Arch
 author: "BMAD BMM"
 
 # Critical variables
-config_source: "{project-root}/bmad/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"
@@ -47,7 +47,7 @@ input_file_patterns:
     sharded: "{output_folder}/docs/index.md"
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/epic-tech-context"
+installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/epic-tech-context"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

package/{bmad → .bmad}/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/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>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>
 

package/{bmad → .bmad}/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/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 @@ user_skill_level: "{config_source}:user_skill_level"
 document_output_language: "{config_source}:document_output_language"
 date: system-generated
 
-installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/retrospective"
+installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/retrospective"
 template: false
 instructions: "{installed_path}/instructions.md"
 
@@ -19,7 +19,7 @@ mode: interactive
 trigger: "Run AFTER completing an epic"
 
 required_inputs:
-  - agent_manifest: "{project-root}/bmad/_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
@@ -46,7 +46,7 @@ input_file_patterns:
 
 # Required files
 sprint_status_file: "{output_folder}/sprint-status.yaml"
-story_directory: "{config_source}:dev_story_location"
+story_directory: "{config_source}:dev_ephemeral_location"
 retrospectives_folder: "{output_folder}/retrospectives"
 
 output_artifacts:

package/{bmad → .bmad}/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/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>
+<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
 

package/{bmad → .bmad}/bmm/workflows/4-implementation/sprint-planning/workflow.yaml

@@ -3,14 +3,14 @@ description: "Generate and manage the sprint status tracking file for Phase 4 im
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/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"
 date: system-generated
 
 # Workflow components
-installed_path: "{project-root}/bmad/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"
@@ -24,7 +24,7 @@ variables:
   # Tracking system configuration
   tracking_system: "file-system" # Options: file-system, Future will support other options from config of mcp such as jira, linear, trello
   story_location: "{project-root}/docs/stories" # Relative path for file-system, Future will support URL for Jira/Linear/Trello
-  story_location_absolute: "{config_source}:dev_story_location" # Absolute path for file operations
+  story_location_absolute: "{config_source}:dev_ephemeral_location" # Absolute path for file operations
 
   # Source files (file-system only)
   epics_location: "{output_folder}" # Directory containing epic*.md files

package/{bmad → .bmad}/bmm/workflows/4-implementation/story-context/checklist.md

@@ -1,7 +1,7 @@
 # Story Context Assembly Checklist
 
 ```xml
-<checklist id="bmad/bmm/workflows/4-implementation/story-context/checklist">
+<checklist id=".bmad/bmm/workflows/4-implementation/story-context/checklist">
   <item>Story fields (asA/iWant/soThat) captured</item>
   <item>Acceptance criteria list matches story draft exactly (no invention)</item>
   <item>Tasks/subtasks captured as task list</item>

package/{bmad → .bmad}/bmm/workflows/4-implementation/story-context/context-template.xml

@@ -1,4 +1,4 @@
-<story-context id="bmad/bmm/workflows/4-implementation/story-context/template" v="1.0">
+<story-context id="{bmad_folder}/bmm/workflows/4-implementation/story-context/template" v="1.0">
   <metadata>
     <epicId>{{epic_id}}</epicId>
     <storyId>{{story_id}}</storyId>

package/{bmad → .bmad}/bmm/workflows/4-implementation/story-context/instructions.md

@@ -1,7 +1,7 @@
 <!-- BMAD BMM Story Context Assembly Instructions (v6) -->
 
 ```xml
-<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
 <critical>Communicate all responses in {communication_language}</critical>
 <critical>Generate all documents in {document_output_language}</critical>
@@ -181,7 +181,7 @@ All stories are either still in backlog or already marked ready/in-progress/done
   <step n="6" goal="Validate and save">
     <anchor id="validation_step" />
     <action>Validate output context file structure and content</action>
-    <invoke-task>Validate against checklist at {installed_path}/checklist.md using bmad/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>
   </step>
 
   <step n="7" goal="Update story file and mark ready for dev" tag="sprint-status">

package/{bmad → .bmad}/bmm/workflows/4-implementation/story-context/workflow.yaml

@@ -4,16 +4,16 @@ description: "Assemble a dynamic Story Context XML by pulling latest documentati
 author: "BMad"
 
 # Critical variables
-config_source: "{project-root}/bmad/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"
 document_output_language: "{config_source}:document_output_language"
-story_path: "{config_source}:dev_story_location"
+story_path: "{config_source}:dev_ephemeral_location"
 date: system-generated
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/story-context"
+installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/story-context"
 template: "{installed_path}/context-template.xml"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
@@ -21,7 +21,7 @@ validation: "{installed_path}/checklist.md"
 # Variables and inputs
 variables:
   story_path: "" # Optional: Explicit story path. If not provided, finds first story with status "drafted"
-  story_dir: "{config_source}:dev_story_location"
+  story_dir: "{config_source}:dev_ephemeral_location"
 
 # Smart input file references - handles both whole docs and sharded docs
 # Priority: Whole document first, then sharded version

package/{bmad → .bmad}/bmm/workflows/4-implementation/story-done/instructions.md

@@ -1,6 +1,6 @@
 # Story Approved Workflow Instructions (DEV Agent)
 
-<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
 <critical>Communicate all responses in {communication_language}</critical>
 

package/{bmad → .bmad}/bmm/workflows/4-implementation/story-done/workflow.yaml

@@ -4,20 +4,20 @@ description: "Marks a story as done (DoD complete) and moves it from its current
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/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"
 date: system-generated
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/story-done"
+installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/story-done"
 instructions: "{installed_path}/instructions.md"
 
 # Variables and inputs
 variables:
   story_path: "" # Explicit path to story file
-  story_dir: "{config_source}:dev_story_location" # Directory where stories are stored
+  story_dir: "{config_source}:dev_ephemeral_location" # Directory where stories are stored
 
 # Output configuration - no output file, just status updates
 default_output_file: ""

package/{bmad → .bmad}/bmm/workflows/4-implementation/story-ready/instructions.md

@@ -1,6 +1,6 @@
 # Story Ready Workflow Instructions (SM Agent)
 
-<critical>The workflow execution engine is governed by: {project_root}/bmad/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>

package/{bmad → .bmad}/bmm/workflows/4-implementation/story-ready/workflow.yaml

@@ -4,20 +4,20 @@ description: "Marks a drafted story as ready for development and moves it from T
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/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"
 date: system-generated
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/story-ready"
+installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/story-ready"
 instructions: "{installed_path}/instructions.md"
 
 # Variables and inputs
 variables:
   story_path: "" # Explicit path to story file
-  story_dir: "{config_source}:dev_story_location" # Directory where stories are stored
+  story_dir: "{config_source}:dev_ephemeral_location" # Directory where stories are stored
 
 # Output configuration - no output file, just status updates
 default_output_file: ""

package/{bmad → .bmad}/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/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project-root}/bmad/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/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/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/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>

package/{bmad → .bmad}/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/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/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"

package/{bmad → .bmad}/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/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/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/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/bmm/workflows/document-project/checklist.md"
+validation: "{project-root}/.bmad/bmm/workflows/document-project/checklist.md"
 
 # Templates
-deep_dive_template: "{project-root}/bmad/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"

package/{bmad → .bmad}/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/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/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/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/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/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"

package/{bmad → .bmad}/bmm/workflows/testarch/atdd/instructions.md

@@ -2,7 +2,7 @@
 
 # Acceptance Test-Driven Development (ATDD)
 
-**Workflow ID**: `bmad/bmm/testarch/atdd`
+**Workflow ID**: `.bmad/bmm/testarch/atdd`
 **Version**: 4.0 (BMad v6)
 
 ---
@@ -50,7 +50,7 @@ Generates failing acceptance tests BEFORE implementation following TDD's red-gre
 
 4. **Load Knowledge Base Fragments**
 
-   **Critical:** Consult `{project-root}/bmad/bmm/testarch/tea-index.csv` to load:
+   **Critical:** Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` to load:
    - `fixture-architecture.md` - Test fixture patterns with auto-cleanup (pure function → fixture → mergeTests composition, 406 lines, 5 examples)
    - `data-factories.md` - Factory patterns using faker (override patterns, nested factories, API seeding, 498 lines, 5 examples)
    - `component-tdd.md` - Component test strategies (red-green-refactor, provider isolation, accessibility, visual regression, 480 lines, 4 examples)

package/{bmad → .bmad}/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/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/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"

package/{bmad → .bmad}/bmm/workflows/testarch/automate/instructions.md

@@ -2,7 +2,7 @@
 
 # Test Automation Expansion
 
-**Workflow ID**: `bmad/bmm/testarch/automate`
+**Workflow ID**: `.bmad/bmm/testarch/automate`
 **Version**: 4.0 (BMad v6)
 
 ---
@@ -83,7 +83,7 @@ Expands test automation coverage by generating comprehensive test suites at appr
 
 5. **Load Knowledge Base Fragments**
 
-   **Critical:** Consult `{project-root}/bmad/bmm/testarch/tea-index.csv` to load:
+   **Critical:** Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` to load:
    - `test-levels-framework.md` - Test level selection (E2E vs API vs Component vs Unit with decision matrix, 467 lines, 4 examples)
    - `test-priorities-matrix.md` - Priority classification (P0-P3 with automated scoring, risk mapping, 389 lines, 2 examples)
    - `fixture-architecture.md` - Test fixture patterns (pure function → fixture → mergeTests, auto-cleanup, 406 lines, 5 examples)

package/{bmad → .bmad}/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/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/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