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

package/src/modules/bmgd/workflows/4-production/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_folder}/core/tasks/workflow.xml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
 <critical>Communicate all responses in {communication_language}</critical>
 

package/src/modules/bmgd/workflows/4-production/story-done/workflow.yaml

@@ -4,7 +4,7 @@ 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_folder}/bmgd/config.yaml"
+config_source: "{project-root}/.bmad/bmgd/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -13,7 +13,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/story-done"
+installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/story-done"
 instructions: "{installed_path}/instructions.md"
 
 # Variables and inputs

package/src/modules/bmgd/workflows/4-production/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_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>

package/src/modules/bmgd/workflows/4-production/story-ready/workflow.yaml

@@ -4,7 +4,7 @@ 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_folder}/bmgd/config.yaml"
+config_source: "{project-root}/.bmad/bmgd/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -13,7 +13,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/story-ready"
+installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/story-ready"
 instructions: "{installed_path}/instructions.md"
 
 # Variables and inputs

package/src/modules/bmm/agents/analyst.agent.yaml

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: "{bmad_folder}/bmm/agents/analyst.md"
+    id: ".bmad/bmm/agents/analyst.md"
     name: Mary
     title: Business Analyst
     icon: 📊
@@ -19,31 +19,31 @@ agent:
 
   menu:
     - trigger: workflow-status
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml"
       description: Get workflow status or initialize a workflow if not already done (optional)
 
     - trigger: brainstorm-project
-      exec: "{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.md"
-      data: "{project-root}/{bmad_folder}/bmm/data/project-context-template.md"
+      exec: "{project-root}/.bmad/core/workflows/brainstorming/workflow.md"
+      data: "{project-root}/.bmad/bmm/data/project-context-template.md"
       description: Guided Project Brainstorming session with final report (optional)
 
     - trigger: research
-      exec: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research/workflow.md"
+      exec: "{project-root}/.bmad/bmm/workflows/1-analysis/research/workflow.md"
       description: Guided Research scoped to market, domain, competitive analysis, or technical research (optional)
 
     - trigger: product-brief
-      exec: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief/workflow.md"
+      exec: "{project-root}/.bmad/bmm/workflows/1-analysis/product-brief/workflow.md"
       description: Create a Product Brief (recommended input for PRD)
 
     - trigger: document-project
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/document-project/workflow.yaml"
       description: Document your existing project (optional, but recommended for existing brownfield project efforts)
 
     - multi: "[SPM] Start Party Mode (optionally suggest attendees and topic), [CH] Chat"
       triggers:
         - party-mode:
             - input: SPM or fuzzy match start party mode
-            - route: "{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md"
+            - route: "{project-root}/.bmad/core/workflows/edit-agent/workflow.md"
             - data: what is being discussed or suggested with the command, along with custom party custom agents if specified
             - type: exec
         - expert-chat:

package/src/modules/bmm/agents/architect.agent.yaml

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: "{bmad_folder}/bmm/agents/architect.md"
+    id: ".bmad/bmm/agents/architect.md"
     name: Winston
     title: Architect
     icon: 🏗️
@@ -19,30 +19,30 @@ agent:
 
   menu:
     - trigger: workflow-status
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml"
       description: Get workflow status or initialize a workflow if not already done (optional)
 
     - trigger: create-architecture
-      exec: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture/workflow.md"
+      exec: "{project-root}/.bmad/bmm/workflows/3-solutioning/architecture/workflow.md"
       description: Create an Architecture Document to Guide Development of a PRD (required for BMad Method projects)
 
     - trigger: implementation-readiness
-      exec: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness/workflow.md"
+      exec: "{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness/workflow.md"
       description: Validate PRD, UX, Architecture, Epics and stories aligned (Optional but recommended before development)
 
     - trigger: create-excalidraw-diagram
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-diagram/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/diagrams/create-diagram/workflow.yaml"
       description: Create system architecture or technical diagram (Excalidraw) (Use any time you need a diagram)
 
     - trigger: create-excalidraw-dataflow
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-dataflow/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/diagrams/create-dataflow/workflow.yaml"
       description: Create data flow diagram (Excalidraw) (Use any time you need a diagram)
 
     - trigger: party-mode
-      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
       description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation
-      exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/bmm/agents/dev.agent.yaml

@@ -3,7 +3,7 @@
 agent:
   webskip: true
   metadata:
-    id: "{bmad_folder}/bmm/agents/dev.md"
+    id: ".bmad/bmm/agents/dev.md"
     name: Amelia
     title: Developer Agent
     icon: 💻
@@ -36,9 +36,9 @@ agent:
 
   menu:
     - trigger: develop-story
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/dev-story/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
       description: "Execute Dev Story workflow (full BMM path with sprint-status)"
 
     - trigger: code-review
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/code-review/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
       description: "Perform a thorough clean context code review (Highly Recommended, use fresh context and different LLM)"

package/src/modules/bmm/agents/pm.agent.yaml

@@ -3,7 +3,7 @@
 
 agent:
   metadata:
-    id: "{bmad_folder}/bmm/agents/pm.md"
+    id: ".bmad/bmm/agents/pm.md"
     name: John
     title: Product Manager
     icon: 📋
@@ -20,31 +20,31 @@ agent:
 
   menu:
     - trigger: workflow-status
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml"
       description: Get workflow status or initialize a workflow if not already done (optional)
 
     - trigger: create-prd
-      exec: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/workflow.md"
+      exec: "{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/workflow.md"
       description: Create Product Requirements Document (PRD) (Required for BMad Method flow)
 
     - trigger: create-epics-and-stories
-      exec: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md"
+      exec: "{project-root}/.bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md"
       description: Create Epics and User Stories from PRD (Required for BMad Method flow AFTER the Architecture is completed)
 
     - trigger: implementation-readiness
-      exec: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness/workflow.md"
+      exec: "{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness/workflow.md"
       description: Validate PRD, UX, Architecture, Epics and stories aligned (Optional but recommended before development)
 
     - trigger: correct-course
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
       description: Course Correction Analysis (optional during implementation when things go off track)
       ide-only: true
 
     - trigger: party-mode
-      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
       description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation
-      exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/bmm/agents/quick-flow-solo-dev.agent.yaml

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: "{bmad_folder}/bmm/agents/quick-flow-solo-dev.md"
+    id: ".bmad/bmm/agents/quick-flow-solo-dev.md"
     name: Barry
     title: Quick Flow Solo Dev
     icon: 🚀
@@ -20,17 +20,17 @@ agent:
 
   menu:
     - trigger: create-tech-spec
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml"
       description: Architect a technical spec with implementation-ready stories (Required first step)
 
     - trigger: quick-dev
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml"
       description: Implement the tech spec end-to-end solo (Core of Quick Flow)
 
     - trigger: code-review
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/code-review/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
       description: Review code and improve it (Highly Recommended, use fresh context and different LLM for best results)
 
     - trigger: party-mode
-      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
       description: Bring in other experts when I need specialized backup

package/src/modules/bmm/agents/sm.agent.yaml

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: "{bmad_folder}/bmm/agents/sm.md"
+    id: ".bmad/bmm/agents/sm.md"
     name: Bob
     title: Scrum Master
     icon: 🏃
@@ -25,31 +25,31 @@ agent:
 
   menu:
     - trigger: sprint-planning
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-planning/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml"
       description: Generate or re-generate sprint-status.yaml from epic files (Required after Epics+Stories are created)
 
     - trigger: create-story
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
       description: Create a Draft Story (Required to prepare stories for development)
 
     - trigger: validate-create-story
-      validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story/workflow.yaml"
+      validate-workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
       description: Validate Story Draft (Highly Recommended, use fresh context and different LLM for best results)
 
     - trigger: epic-retrospective
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/retrospective/workflow.yaml"
-      data: "{project-root}/{bmad_folder}/_cfg/agent-manifest.csv"
+      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml"
+      data: "{project-root}/.bmad/_cfg/agent-manifest.csv"
       description: Facilitate team retrospective after an epic is completed (Optional)
 
     - trigger: correct-course
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
       description: Execute correct-course task (When implementation is off-track)
 
     - trigger: party-mode
-      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
       description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation
-      exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/bmm/agents/tea.agent.yaml

@@ -3,7 +3,7 @@
 agent:
   webskip: true
   metadata:
-    id: "{bmad_folder}/bmm/agents/tea.md"
+    id: ".bmad/bmm/agents/tea.md"
     name: Murat
     title: Master Test Architect
     icon: 🧪
@@ -22,49 +22,49 @@ agent:
       - Calculate risk vs value for every testing decision
 
   critical_actions:
-    - "Consult {project-root}/{bmad_folder}/bmm/testarch/tea-index.csv to select knowledge fragments under knowledge/ and load only the files needed for the current task"
-    - "Load the referenced fragment(s) from {project-root}/{bmad_folder}/bmm/testarch/knowledge/ before giving recommendations"
+    - "Consult {project-root}/.bmad/bmm/testarch/tea-index.csv to select knowledge fragments under knowledge/ and load only the files needed for the current task"
+    - "Load the referenced fragment(s) from {project-root}/.bmad/bmm/testarch/knowledge/ before giving recommendations"
     - "Cross-check recommendations with the current official Playwright, Cypress, Pact, and CI platform documentation"
     - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
 
   menu:
     - trigger: framework
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/framework/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/testarch/framework/workflow.yaml"
       description: Initialize production-ready test framework architecture
 
     - trigger: atdd
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/atdd/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/testarch/atdd/workflow.yaml"
       description: Generate E2E tests first, before starting implementation
 
     - trigger: automate
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/automate/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/testarch/automate/workflow.yaml"
       description: Generate comprehensive test automation
 
     - trigger: test-design
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/test-design/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/testarch/test-design/workflow.yaml"
       description: Create comprehensive test scenarios
 
     - trigger: trace
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/trace/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/testarch/trace/workflow.yaml"
       description: Map requirements to tests (Phase 1) and make quality gate decision (Phase 2)
 
     - trigger: nfr-assess
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/nfr-assess/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml"
       description: Validate non-functional requirements
 
     - trigger: ci
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/ci/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/testarch/ci/workflow.yaml"
       description: Scaffold CI/CD quality pipeline
 
     - trigger: test-review
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/test-review/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/testarch/test-review/workflow.yaml"
       description: Review test quality using comprehensive knowledge base and best practices
 
     - trigger: party-mode
-      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
       description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation
-      exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/bmm/agents/tech-writer.agent.yaml

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: "{bmad_folder}/bmm/agents/tech-writer.md"
+    id: ".bmad/bmm/agents/tech-writer.md"
     name: Paige
     title: Technical Writer
     icon: 📚
@@ -17,12 +17,12 @@ agent:
       - Docs are living artifacts that evolve with code. Know when to simplify vs when to be detailed.
 
   critical_actions:
-    - "CRITICAL: Load COMPLETE file {project-root}/{bmad_folder}/bmm/data/documentation-standards.md into permanent memory and follow ALL rules within"
+    - "CRITICAL: Load COMPLETE file {project-root}/.bmad/bmm/data/documentation-standards.md into permanent memory and follow ALL rules within"
     - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
 
   menu:
     - trigger: document-project
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/document-project/workflow.yaml"
       description: Comprehensive project documentation (brownfield analysis, architecture scanning)
 
     - trigger: generate-mermaid
@@ -30,15 +30,15 @@ agent:
       description: Generate Mermaid diagrams (architecture, sequence, flow, ER, class, state)
 
     - trigger: create-excalidraw-flowchart
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-flowchart/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/diagrams/create-flowchart/workflow.yaml"
       description: Create Excalidraw flowchart for processes and logic flows
 
     - trigger: create-excalidraw-diagram
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-diagram/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/diagrams/create-diagram/workflow.yaml"
       description: Create Excalidraw system architecture or technical diagram
 
     - trigger: create-excalidraw-dataflow
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-dataflow/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/diagrams/create-dataflow/workflow.yaml"
       description: Create Excalidraw data flow diagram
 
     - trigger: validate-doc
@@ -54,14 +54,14 @@ agent:
       description: Create clear technical explanations with examples
 
     - trigger: standards-guide
-      action: "Display the complete documentation standards from {project-root}/{bmad_folder}bmm/data/documentation-standards.md in a clear, formatted way for the user."
+      action: "Display the complete documentation standards from {project-root}/.bmadbmm/data/documentation-standards.md in a clear, formatted way for the user."
       description: Show BMAD documentation standards reference (CommonMark, Mermaid, OpenAPI)
 
     - trigger: party-mode
-      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
       description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation
-      exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/bmm/agents/ux-designer.agent.yaml

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: "{bmad_folder}/bmm/agents/ux-designer.md"
+    id: ".bmad/bmm/agents/ux-designer.md"
     name: Sally
     title: UX Designer
     icon: 🎨
@@ -24,22 +24,22 @@ agent:
 
   menu:
     - trigger: create-ux-design
-      exec: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md"
+      exec: "{project-root}/.bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md"
       description: Generate a UX Design and UI Plan from a PRD (Recommended before creating Architecture)
 
     - trigger: validate-design
-      validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml"
+      validate-workflow: "{project-root}/.bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml"
       description: Validate UX Specification and Design Artifacts
 
     - trigger: create-excalidraw-wireframe
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-wireframe/workflow.yaml"
+      workflow: "{project-root}/.bmad/bmm/workflows/diagrams/create-wireframe/workflow.yaml"
       description: Create website or app wireframe (Excalidraw)
 
     - trigger: party-mode
-      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
       description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation
-      exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/bmm/docs/README.md

@@ -139,9 +139,6 @@ Comprehensive documentation for all BMM workflows organized by phase:
   - Complete story lifecycle
   - One-story-at-a-time discipline
 
-<<<<<<< Updated upstream
-<<<<<<< Updated upstream
-
 - **[Testing & QA Workflows](./test-architecture.md)** - Comprehensive quality assurance (1,420 lines)
   - Test strategy, automation, quality gates
   - TEA agent and test healing
@@ -149,14 +146,6 @@ Comprehensive documentation for all BMM workflows organized by phase:
 
 **Total: 34 workflows documented across all phases**
 
-=======
-
-> > > > > > > Stashed changes
-
-=======
-
-> > > > > > > Stashed changes
-
 ### Advanced Workflow References
 
 For detailed technical documentation on specific complex workflows:
@@ -181,23 +170,9 @@ Quality assurance guidance:
 
 <!-- Test Architect documentation to be added -->
 
-<<<<<<< Updated upstream
-
-<<<<<<< Updated upstream
-
 - Test design workflows
 - Quality gates
 - Risk assessment
-- # NFR validation
-  =======
-  > > > > > > > Stashed changes
-  - Test design workflows
-  - Quality gates
-  - Risk assessment
-  - NFR validation
-    > > > > > > > Stashed changes
-
----
 
 ## 🏗️ Module Structure
 

package/src/modules/bmm/docs/agents-guide.md

@@ -661,14 +661,14 @@ You can customize any agent's personality without modifying core agent files.
 
 ### Location
 
-**Customization Directory:** `{project-root}/{bmad_folder}/_cfg/agents/`
+**Customization Directory:** `{project-root}/.bmad/_cfg/agents/`
 
 **Naming Convention:** `{module}-{agent-name}.customize.yaml`
 
 **Examples:**
 
 ```
-{bmad_folder}/_cfg/agents/
+.bmad/_cfg/agents/
 ├── bmm-pm.customize.yaml
 ├── bmm-dev.customize.yaml
 ├── cis-storyteller.customize.yaml
@@ -768,9 +768,9 @@ Other agents collaborate with PM's specialized perspective.
 
 ```bash
 # Create customization file at:
-# {project-root}/{bmad_folder}/_cfg/agents/{module}-{agent-name}.customize.yaml
+# {project-root}/.bmad/_cfg/agents/{module}-{agent-name}.customize.yaml
 
-# Example: {bmad_folder}/_cfg/agents/bmm-pm.customize.yaml
+# Example: .bmad/_cfg/agents/bmm-pm.customize.yaml
 ```
 
 **Step 2: Regenerate Agent Manifest**

package/src/modules/bmm/docs/brownfield-guide.md

@@ -137,7 +137,7 @@ If you have documentation but files are huge (>500 lines, 10+ level 2 sections):
 
    ```bash
    # Load BMad Master or any agent
-   {bmad_folder}/core/tools/shard-doc.xml --input docs/massive-doc.md
+   .bmad/core/tools/shard-doc.xml --input docs/massive-doc.md
    ```
 
    - Splits on level 2 sections by default
@@ -147,7 +147,7 @@ If you have documentation but files are huge (>500 lines, 10+ level 2 sections):
 2. **Then:** Run `index-docs` task to create navigation:
 
    ```bash
-   {bmad_folder}/core/tasks/index-docs.xml --directory ./docs
+   .bmad/core/tasks/index-docs.xml --directory ./docs
    ```
 
 3. **Finally:** Validate quality - if sharded docs still seem incomplete/outdated → Run `document-project`
@@ -210,7 +210,7 @@ If you have **good, current documentation** but it's in massive files:
 
 ```bash
 # For each massive doc (>500 lines or 10+ level 2 sections)
-{bmad_folder}/core/tools/shard-doc.xml \
+.bmad/core/tools/shard-doc.xml \
   --input docs/api-documentation.md \
   --output docs/api/ \
   --level 2  # Split on ## headers (default)
@@ -219,7 +219,7 @@ If you have **good, current documentation** but it's in massive files:
 **Step 2: Generate index**
 
 ```bash
-{bmad_folder}/core/tasks/index-docs.xml --directory ./docs
+.bmad/core/tasks/index-docs.xml --directory ./docs
 ```
 
 **Step 3: Validate**

package/src/modules/bmm/docs/enterprise-agentic-development.md

@@ -425,7 +425,7 @@ Team C (2 devs): Analytics feature (3 epics)
 
 **Problem:** Teams customize BMad (agents, workflows, configs) but don't want personal tooling in main repo.
 
-**Anti-pattern:** Adding `{bmad_folder}/` to `.gitignore` breaks IDE tools, submodule management.
+**Anti-pattern:** Adding `.bmad/` to `.gitignore` breaks IDE tools, submodule management.
 
 ### The Solution: Git Submodules
 
@@ -463,7 +463,7 @@ git commit -m "Add BMM as submodule"
 git clone https://github.com/your-org/your-project.git
 cd your-project
 git submodule update --init --recursive
-# Make personal customizations in {bmad_folder}/
+# Make personal customizations in .bmad/
 ```
 
 ### Daily Workflow
@@ -472,7 +472,7 @@ git submodule update --init --recursive
 
 ```bash
 cd /path/to/your-project
-# BMad available at ./{bmad_folder}/, load agents normally
+# BMad available at ./.bmad/, load agents normally
 ```
 
 **Update personal config:**

package/src/modules/bmm/docs/faq.md

@@ -371,7 +371,7 @@ See [IDE Setup Guides](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/do
 
 ### Q: Can I customize agents?
 
-**A:** Yes! Agents are installed as markdown files with XML-style content (optimized for LLMs, readable by any model). Create customization files in `{bmad_folder}/_cfg/agents/[agent-name].customize.yaml` to override default behaviors while keeping core functionality intact. See agent documentation for customization options.
+**A:** Yes! Agents are installed as markdown files with XML-style content (optimized for LLMs, readable by any model). Create customization files in `.bmad/_cfg/agents/[agent-name].customize.yaml` to override default behaviors while keeping core functionality intact. See agent documentation for customization options.
 
 **Note:** While source agents in this repo are YAML, they install as `.md` files with XML-style tags - a format any LLM can read and follow.