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

package/{bmad → .bmad}/bmm/workflows/1-analysis/research/instructions-deep-prompt.md

@@ -1,6 +1,6 @@
 # Deep Research Prompt Generator Instructions
 
-<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>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
 <critical>This workflow generates structured research prompts optimized for AI platforms</critical>
@@ -211,7 +211,7 @@ Examples:
 
 <template-output>special_requirements</template-output>
 
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 

package/{bmad → .bmad}/bmm/workflows/1-analysis/research/instructions-market.md

@@ -1,6 +1,6 @@
 # Market Research Workflow Instructions
 
-<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>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
 <critical>This is a HIGHLY INTERACTIVE workflow - collaborate with user throughout, don't just gather info and disappear</critical>
@@ -114,7 +114,7 @@ Work with the user to establish:
 
 <action if="user_has_questions">Explore surprising data points together</action>
 
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 <template-output>sources_market_size</template-output>
 </step>
@@ -239,7 +239,7 @@ For each major segment, research and define:
 - Purchasing frequency
 - Budget allocation
 
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 <template-output>segment*profile*{{segment_number}}</template-output>
 </step>
 
@@ -313,7 +313,7 @@ Use {{current_year}} in all searches.
 
 <action if="user has follow-up questions">Dig deeper based on their interests</action>
 
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 <template-output>competitor*analysis*{{competitor_name}}</template-output>
 </step>
 
@@ -437,7 +437,7 @@ For each opportunity:
 - Risk assessment
 - Success criteria
 
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 <template-output>market_opportunities</template-output>
 </step>
 
@@ -663,7 +663,7 @@ Would you like me to strengthen any areas with additional research?"
 {{#if standalone_mode != true}}
 
 - **Next workflow:** {{next_workflow}} ({{next_agent}} agent)
-- **Optional:** Review findings with stakeholders, or run additional analysis workflows (product-brief, game-brief, etc.)
+- **Optional:** Review findings with stakeholders, or run additional analysis workflows (product-brief for software, or install BMGD module for game-brief)
 
 Check status anytime with: `workflow-status`
 {{else}}

package/{bmad → .bmad}/bmm/workflows/1-analysis/research/instructions-router.md

@@ -1,6 +1,6 @@
 # Research Workflow Router Instructions
 
-<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 in {communication_language}, generate documents in {document_output_language}</critical>
 <critical>Web research is ENABLED - always use current {{current_year}} data</critical>

package/{bmad → .bmad}/bmm/workflows/1-analysis/research/instructions-technical.md

@@ -1,6 +1,6 @@
 # Technical/Architecture Research Instructions
 
-<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>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
 <critical>This is a HIGHLY INTERACTIVE workflow - make technical decisions WITH user, not FOR them</critical>
@@ -143,7 +143,7 @@ Each of these is popular for different reasons. Let me know if you want me to ex
 </check>
 </action>
 
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 <template-output>technology_options</template-output>
 
@@ -221,7 +221,7 @@ Each of these is popular for different reasons. Let me know if you want me to ex
 - Training costs
 - Total cost of ownership estimate
 
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 <template-output>tech*profile*{{option_number}}</template-output>
 
 </step>
@@ -392,7 +392,7 @@ Research and document:
 - Contingency options if primary choice doesn't work
 - Exit strategy considerations
 
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 <template-output>recommendations</template-output>
 

package/{bmad → .bmad}/bmm/workflows/1-analysis/research/workflow.yaml

@@ -4,7 +4,7 @@ description: "Adaptive research workflow supporting multiple research types: mar
 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"
@@ -24,7 +24,7 @@ minimum_sources_per_claim: 2
 fact_check_critical_data: true
 
 # Workflow components - ROUTER PATTERN
-installed_path: "{project-root}/bmad/bmm/workflows/1-analysis/research"
+installed_path: "{project-root}/.bmad/bmm/workflows/1-analysis/research"
 instructions: "{installed_path}/instructions-router.md" # Router loads specific instruction sets
 validation: "{installed_path}/checklist.md"
 

package/{bmad → .bmad}/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md

@@ -2,7 +2,7 @@
 
 <workflow name="create-ux-design">
 
-<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>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
 <critical>The goal is COLLABORATIVE UX DESIGN through visual exploration, not content generation</critical>

package/{bmad → .bmad}/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml

@@ -4,7 +4,7 @@ description: "Collaborative UX design facilitation workflow that creates excepti
 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"
@@ -46,19 +46,15 @@ input_file_patterns:
     sharded: "{output_folder}/docs/index.md"
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmm/workflows/2-plan-workflows/create-ux-design"
+installed_path: "{project-root}/.bmad/bmm/workflows/2-plan-workflows/create-ux-design"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 template: "{installed_path}/ux-design-template.md"
 
-# Knowledge bases for intelligent UX decisions
-ux_pattern_catalog: "{installed_path}/ux-pattern-catalog.yaml"
-color_psychology: "{installed_path}/color-psychology.yaml"
-layout_patterns: "{installed_path}/layout-patterns.yaml"
-
 # Output configuration - Progressive saves throughout workflow
 default_output_file: "{output_folder}/ux-design-specification.md"
 color_themes_html: "{output_folder}/ux-color-themes.html"
 design_directions_html: "{output_folder}/ux-design-directions.html"
 
 standalone: true
+# Web bundle configuration for standalone deployment

package/{bmad → .bmad}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md

@@ -1,6 +1,6 @@
 # Epic and Story Decomposition - Intent-Based Implementation Planning
 
-<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>This workflow transforms requirements into BITE-SIZED STORIES for development agents</critical>
 <critical>EVERY story must be completable by a single dev agent in one focused session</critical>
@@ -80,7 +80,7 @@ Present proposed epic structure showing:
 - Why this grouping makes sense</action>
 
 <template-output>epics_summary</template-output>
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="3" goal="Decompose each epic into bite-sized stories" repeat="for-each-epic">
@@ -138,7 +138,7 @@ For each story in epic {{N}}, output variables following this pattern:
 <action>For each story M in epic {{N}}, generate story content</action>
 <template-output>story*title*{{N}}\_{{M}}</template-output>
 
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="4" goal="Review and finalize epic breakdown">

package/{bmad → .bmad}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml

@@ -4,7 +4,7 @@ description: "Transform PRD requirements into bite-sized stories organized in ep
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 project_name: "{config_source}:project_name"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
@@ -35,7 +35,7 @@ input_file_patterns:
     sharded: "{output_folder}/*domain*brief*/index.md"
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories"
+installed_path: "{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories"
 instructions: "{installed_path}/instructions.md"
 template: "{installed_path}/epics-template.md"
 

package/{bmad → .bmad}/bmm/workflows/2-plan-workflows/prd/instructions.md

@@ -1,6 +1,6 @@
 # PRD Workflow - Intent-Driven Product Planning
 
-<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>This workflow uses INTENT-DRIVEN PLANNING - adapt organically to product type and context</critical>
 <critical>Communicate all responses in {communication_language} and adapt deeply to {user_skill_level}</critical>
@@ -62,7 +62,7 @@ Project type signals: API, mobile, web, CLI, SDK, SaaS
 Domain complexity signals: medical, finance, government, education, aerospace
 
 SPECIAL ROUTING:
-If game detected → Suggest game-brief and GDD workflows
+If game detected → Inform user that game development requires the BMGD module (BMad Game Development)
 If complex domain detected → Offer domain research options:
 A) Run domain-research workflow (thorough)
 B) Quick web search (basic)
@@ -115,7 +115,7 @@ Weave in the magic:
 <check if="business focus">
 <template-output>business_metrics</template-output>
 </check>
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="3" goal="Scope Definition">
@@ -140,7 +140,7 @@ For complex domains:
 <template-output>mvp_scope</template-output>
 <template-output>growth_features</template-output>
 <template-output>vision_features</template-output>
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="4" goal="Domain-Specific Exploration" optional="true">
@@ -289,7 +289,7 @@ The magic thread:
 Highlight which requirements deliver the special experience</action>
 
 <template-output>functional_requirements_complete</template-output>
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="9" goal="Non-Functional Requirements Discovery">
@@ -341,7 +341,7 @@ Skip categories that don't apply!</action>
 Does this capture your product vision?"</action>
 
 <template-output>prd_summary</template-output>
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 <action>After PRD review and refinement complete:
 

package/{bmad → .bmad}/bmm/workflows/2-plan-workflows/prd/workflow.yaml

@@ -4,7 +4,7 @@ description: "Unified PRD workflow for BMad Method and Enterprise Method tracks.
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 project_name: "{config_source}:project_name"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
@@ -14,7 +14,7 @@ user_skill_level: "{config_source}:user_skill_level"
 date: system-generated
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/2-plan-workflows/prd"
+installed_path: "{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd"
 instructions: "{installed_path}/instructions.md"
 
 # Templates

package/{bmad → .bmad}/bmm/workflows/2-plan-workflows/tech-spec/checklist.md

@@ -13,7 +13,7 @@
 ## 1. Output Files Exist
 
 - [ ] tech-spec.md created in output folder
-- [ ] Story file(s) created in dev_story_location
+- [ ] Story file(s) created in dev_ephemeral_location
   - Level 0: 1 story file (story-{slug}.md)
   - Level 1: epics.md + 2-3 story files (story-{epic-slug}-N.md)
 - [ ] bmm-workflow-status.yaml updated (if not standalone mode)

package/{bmad → .bmad}/bmm/workflows/2-plan-workflows/tech-spec/instructions-level0-story.md

@@ -11,7 +11,7 @@
 
 <action>Read the completed tech-spec.md file from {output_folder}/tech-spec.md</action>
 <action>Load bmm-workflow-status.yaml from {output_folder}/bmm-workflow-status.yaml (if exists)</action>
-<action>Extract dev_story_location from config (where stories are stored)</action>
+<action>Extract dev_ephemeral_location from config (where stories are stored)</action>
 
 <action>Extract from the ENHANCED tech-spec structure:
 
@@ -42,7 +42,7 @@
 </example>
 
 <action>Set story_filename = "story-{slug}.md"</action>
-<action>Set story_path = "{dev_story_location}/story-{slug}.md"</action>
+<action>Set story_path = "{dev_ephemeral_location}/story-{slug}.md"</action>
 
 </step>
 
@@ -122,7 +122,7 @@ Since tech-spec is now context-rich, populate all new template fields:
 
 <step n="4" goal="Update status - Level 0 single story">
 
-<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: tech-spec</param>
@@ -170,7 +170,7 @@ Since the tech-spec is now CONTEXT-RICH with:
 
 **You can skip story-context and go straight to dev!**
 
-1. Load DEV agent: `{project-root}/bmad/bmm/agents/dev.md`
+1. Load DEV agent: `{project-root}/.bmad/bmm/agents/dev.md`
 2. Run `dev-story` workflow
 3. Begin implementation immediately
 
@@ -178,7 +178,7 @@ Since the tech-spec is now CONTEXT-RICH with:
 
 Only needed for extremely complex scenarios:
 
-1. Load SM agent: `{project-root}/bmad/bmm/agents/sm.md`
+1. Load SM agent: `{project-root}/.bmad/bmm/agents/sm.md`
 2. Run `story-context` workflow (generates additional XML context)
 3. Then load DEV agent and run `dev-story` workflow
 

package/{bmad → .bmad}/bmm/workflows/2-plan-workflows/tech-spec/instructions-level1-stories.md

@@ -12,7 +12,7 @@
 
 <action>Read the completed tech-spec.md file from {output_folder}/tech-spec.md</action>
 <action>Load bmm-workflow-status.yaml from {output_folder}/bmm-workflow-status.yaml (if exists)</action>
-<action>Extract dev_story_location from config (where stories are stored)</action>
+<action>Extract dev_ephemeral_location from config (where stories are stored)</action>
 
 <action>Extract from the ENHANCED tech-spec structure:
 
@@ -178,7 +178,7 @@ Since tech-spec is context-rich, populate ALL template fields:
   </guidelines>
 
 <for-each story="1 to story_count">
-  <action>Set story_path_{n} = "{dev_story_location}/story-{epic_slug}-{n}.md"</action>
+  <action>Set story_path_{n} = "{dev_ephemeral_location}/story-{epic_slug}-{n}.md"</action>
   <action>Create story file from user_story_template with the following content:</action>
 
   <template-output file="{story_path_{n}}">
@@ -271,7 +271,7 @@ Epic: Icon Reliability
 
 <step n="6" goal="Update status and populate story backlog">
 
-<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: tech-spec</param>
@@ -391,7 +391,7 @@ Stories are implementation-ready!</output>
 - `story-{epic_slug}-3.md` → Third story
   {{/if}}
 
-**Story Location:** `{dev_story_location}/`
+**Story Location:** `{dev_ephemeral_location}/`
 
 **Next Steps - Iterative Implementation:**
 
@@ -408,7 +408,7 @@ Since the tech-spec is now CONTEXT-RICH with:
 **You can skip story-context for most Level 1 stories!**
 
 **1. Start with Story 1:**
-a. Load DEV agent: `{project-root}/bmad/bmm/agents/dev.md`
+a. Load DEV agent: `{project-root}/.bmad/bmm/agents/dev.md`
 b. Run `dev-story` workflow (select story-{epic_slug}-1.md)
 c. Tech-spec provides all context needed
 d. Implement story 1
@@ -429,7 +429,7 @@ d. Implement story 1
 
 Only needed for extremely complex multi-story dependencies:
 
-1. Load SM agent: `{project-root}/bmad/bmm/agents/sm.md`
+1. Load SM agent: `{project-root}/.bmad/bmm/agents/sm.md`
 2. Run `story-context` workflow for complex stories
 3. Then load DEV agent and run `dev-story`
 

package/{bmad → .bmad}/bmm/workflows/2-plan-workflows/tech-spec/instructions.md

@@ -2,7 +2,7 @@
 
 <workflow>
 
-<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>
@@ -914,7 +914,7 @@ What to watch after deployment:
 <template-output file="tech-spec.md">rollback_plan</template-output>
 <template-output file="tech-spec.md">monitoring_approach</template-output>
 
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 

package/{bmad → .bmad}/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml

@@ -4,7 +4,7 @@ description: "Technical specification workflow for Level 0 projects (single atom
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 project_name: "{config_source}:project_name"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
@@ -21,7 +21,7 @@ change_type: runtime-captured
 field_type: runtime-captured
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/2-plan-workflows/tech-spec"
+installed_path: "{project-root}/.bmad/bmm/workflows/2-plan-workflows/tech-spec"
 instructions: "{installed_path}/instructions.md"
 template: "{installed_path}/tech-spec-template.md"
 

package/{bmad → .bmad}/bmm/workflows/3-solutioning/architecture/instructions.md

@@ -2,7 +2,7 @@
 
 <workflow name="architecture">
 
-<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>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
 <critical>The goal is ARCHITECTURAL DECISIONS that prevent AI agent conflicts, not detailed implementation specs</critical>
@@ -363,7 +363,7 @@ Provided by Starter: {{yes_if_from_starter}}
 </action>
 
 <template-output>decision_record</template-output>
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="5" goal="Address cross-cutting concerns">
@@ -393,7 +393,7 @@ Provided by Starter: {{yes_if_from_starter}}
 </action>
 
 <template-output>project_structure</template-output>
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="7" goal="Design novel architectural patterns" optional="true">
@@ -467,7 +467,7 @@ Provided by Starter: {{yes_if_from_starter}}
   </check>
 
 <template-output>novel_pattern_designs</template-output>
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="8" goal="Define implementation patterns to prevent agent conflicts">
@@ -560,7 +560,7 @@ Enforcement: "All agents MUST follow this pattern"
 </action>
 
 <template-output>implementation_patterns</template-output>
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="9" goal="Validate architectural coherence">
@@ -614,7 +614,7 @@ Enforcement: "All agents MUST follow this pattern"
   </action>
 
 <template-output>architecture_document</template-output>
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="11" goal="Validate document completeness">

package/{bmad → .bmad}/bmm/workflows/3-solutioning/architecture/workflow.yaml

@@ -4,7 +4,7 @@ description: "Collaborative architectural decision facilitation for AI-agent con
 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"
@@ -37,7 +37,7 @@ input_file_patterns:
     sharded: "{output_folder}/docs/index.md"
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmm/workflows/3-solutioning/architecture"
+installed_path: "{project-root}/.bmad/bmm/workflows/3-solutioning/architecture"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 template: "{installed_path}/architecture-template.md"
@@ -65,3 +65,4 @@ features:
   - "Implementation patterns for agent consistency"
 
 standalone: true
+# Web bundle configuration for standalone deployment

package/{bmad → .bmad}/bmm/workflows/3-solutioning/solutioning-gate-check/instructions.md

@@ -1,7 +1,7 @@
 # Implementation Ready Check - Workflow 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/3-solutioning/solutioning-gate-check/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/3-solutioning/solutioning-gate-check/workflow.yaml</critical>
 <critical>Communicate all findings and analysis in {communication_language} throughout the assessment</critical>
 <critical>Input documents specified in workflow.yaml input_file_patterns - workflow engine handles fuzzy matching, whole vs sharded document discovery automatically</critical>
 

package/{bmad → .bmad}/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml

@@ -4,7 +4,7 @@ description: "Systematically validate that all planning and solutioning phases a
 author: "BMad Builder"
 
 # 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,11 +12,11 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated
 
 # Workflow status integration
-workflow_status_workflow: "{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml"
-workflow_paths_dir: "{project-root}/bmad/bmm/workflows/workflow-status/paths"
+workflow_status_workflow: "{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml"
+workflow_paths_dir: "{project-root}/.bmad/bmm/workflows/workflow-status/paths"
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmm/workflows/3-solutioning/solutioning-gate-check"
+installed_path: "{project-root}/.bmad/bmm/workflows/3-solutioning/solutioning-gate-check"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

package/{bmad → .bmad}/bmm/workflows/4-implementation/code-review/instructions.md

@@ -1,7 +1,7 @@
 # Senior Developer Review - 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>
@@ -376,7 +376,7 @@ Review was saved to story file, but sprint-status.yaml may be out of sync.
   </step>
 
   <step n="10" goal="Validation and completion">
-    <invoke-task>Run validation checklist at {installed_path}/checklist.md using {project-root}/bmad/core/tasks/validate-workflow.xml</invoke-task>
+    <invoke-task>Run validation checklist at {installed_path}/checklist.md using {project-root}/.bmad/core/tasks/validate-workflow.xml</invoke-task>
     <action>Report workflow completion.</action>
 
     <check if="ad_hoc_review_mode == true">

package/{bmad → .bmad}/bmm/workflows/4-implementation/code-review/workflow.yaml

@@ -4,7 +4,7 @@ description: "Perform a Senior Developer code review on a completed story flagge
 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"
@@ -13,7 +13,7 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/code-review"
+installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/code-review"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 
@@ -23,7 +23,7 @@ template: false
 # Variables (can be provided by caller)
 variables:
   story_path: "" # Optional: Explicit path to story file. If not provided, finds first story with status "review"
-  story_dir: "{config_source}:dev_story_location" # Directory containing story files
+  story_dir: "{config_source}:dev_ephemeral_location" # Directory containing story files
   tech_spec_search_dir: "{project-root}/docs"
   tech_spec_glob_template: "tech-spec-epic-{{epic_num}}*.md"
   arch_docs_search_dirs: |
@@ -31,16 +31,7 @@ variables:
     - "{output_folder}"
   arch_docs_file_names: |
     - architecture.md
-  enable_mcp_doc_search: true # Prefer enabled MCP servers for doc/best-practice lookup
-  enable_web_fallback: true # Fallback to web search/read-url if MCP not available
-  # Persistence controls for review action items and notes
-  persist_action_items: true
-  # Valid targets: story_tasks, story_review_section, backlog_file, epic_followups
-  persist_targets: |
-    - story_review_section
-    - story_tasks
-    - backlog_file
-    - epic_followups
+
   backlog_file: "{project-root}/docs/backlog.md"
   update_epic_followups: true
   epic_followups_section_title: "Post-Review Follow-ups"

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