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

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

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: ".bmad/bmm/agents/analyst.md"
+    id: "_bmad/bmm/agents/analyst.md"
     name: Mary
     title: Business Analyst
     icon: 📊
@@ -19,34 +19,34 @@ agent:
 
   menu:
     - trigger: workflow-status
-      workflow: "{project-root}/.bmad/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/core/workflows/brainstorming/workflow.md"
-      data: "{project-root}/.bmad/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/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/bmm/workflows/1-analysis/product-brief/workflow.md"
+      exec: "{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md"
       description: Create a Product Brief (recommended input for PRD)
 
     - trigger: document-project
-      workflow: "{project-root}/.bmad/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/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:
             - input: CH or fuzzy match validate agent
-            - action: agent responds as expert based on its personal to converse
+            - action: agent responds as expert based on its persona to converse
             - type: action

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

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: ".bmad/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/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/bmm/workflows/3-solutioning/architecture/workflow.md"
+      exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/create-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/bmm/workflows/3-solutioning/implementation-readiness/workflow.md"
+      exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/check-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/bmm/workflows/diagrams/create-diagram/workflow.yaml"
+      workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-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/bmm/workflows/diagrams/create-dataflow/workflow.yaml"
+      workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-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/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/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/bmm/agents/dev.md"
+    id: "_bmad/bmm/agents/dev.md"
     name: Amelia
     title: Developer Agent
     icon: 💻
@@ -24,7 +24,7 @@ agent:
 
   critical_actions:
     - "READ the entire story file BEFORE any implementation - tasks/subtasks sequence is your authoritative implementation guide"
-    - "Load project_context.md if available for coding standards only - never let it override story requirements"
+    - "Load project-context.md if available for coding standards only - never let it override story requirements"
     - "Execute tasks/subtasks IN ORDER as written in story file - no skipping, no reordering, no doing what you want"
     - "For each task/subtask: follow red-green-refactor cycle - write failing test first, then implementation"
     - "Mark task/subtask [x] ONLY when both implementation AND tests are complete and passing"
@@ -35,10 +35,10 @@ agent:
     - "NEVER lie about tests being written or passing - tests must actually exist and pass 100%"
 
   menu:
-    - trigger: develop-story
-      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
+    - trigger: dev-story
+      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/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/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/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/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/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/bmm/workflows/3-solutioning/implementation-readiness/workflow.md"
+      exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/check-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/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/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/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/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/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/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/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/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/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/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/bmm/workflows/4-implementation/create-story/workflow.yaml"
-      description: Create a Draft Story (Required to prepare stories for development)
+      workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
+      description: Create Story (Required to prepare stories for development)
 
     - trigger: validate-create-story
-      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)
+      validate-workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
+      description: Validate Story (Highly Recommended, use fresh context and different LLM for best results)
 
     - trigger: epic-retrospective
-      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml"
-      data: "{project-root}/.bmad/_cfg/agent-manifest.csv"
+      workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml"
+      data: "{project-root}/_bmad/_config/agent-manifest.csv"
       description: Facilitate team retrospective after an epic is completed (Optional)
 
     - trigger: correct-course
-      workflow: "{project-root}/.bmad/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/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/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/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/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"
+    - "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/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/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/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/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/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/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/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/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/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/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/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/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/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/bmm/workflows/diagrams/create-flowchart/workflow.yaml"
+      workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml"
       description: Create Excalidraw flowchart for processes and logic flows
 
     - trigger: create-excalidraw-diagram
-      workflow: "{project-root}/.bmad/bmm/workflows/diagrams/create-diagram/workflow.yaml"
+      workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml"
       description: Create Excalidraw system architecture or technical diagram
 
     - trigger: create-excalidraw-dataflow
-      workflow: "{project-root}/.bmad/bmm/workflows/diagrams/create-dataflow/workflow.yaml"
+      workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-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}/.bmadbmm/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/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/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/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/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/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/bmm/workflows/diagrams/create-wireframe/workflow.yaml"
+      workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml"
       description: Create website or app wireframe (Excalidraw)
 
     - trigger: party-mode
-      exec: "{project-root}/.bmad/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/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/agents-guide.md

@@ -180,11 +180,13 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 
 - `workflow-status` - Check what to do next
 - `sprint-planning` - Initialize `sprint-status.yaml` tracking
-- `create-story` - Draft next story from epic
-- `validate-create-story` - Independent story validation
+- `create-story` - Create next story from epic (sets status to `ready-for-dev`)
+- `validate-create-story` - Optional quality check (does not change status; run before dev-story for extra validation)
 - `epic-retrospective` - Post-epic review
 - `correct-course` - Handle changes during implementation
 
+**Story handoff sequence:** `create-story` → (optional) `validate-create-story` → `dev-story`
+
 **Communication Style:** Task-oriented and efficient. Direct and eliminates ambiguity. Focuses on clear handoffs and developer-ready specifications.
 
 **Expertise:**
@@ -212,7 +214,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 **Workflows:**
 
 - `workflow-status` - Check what to do next
-- `develop-story` - Implement story with:
+- `dev-story` - Implement story with:
   - Task-by-task iteration
   - Test-driven development
   - Multi-run capability (initial + fixes)
@@ -449,7 +451,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 **Workflows:**
 
 - `workflow-status` - Check what to do next
-- `develop-story` - Execute Dev Story workflow, implementing tasks and tests
+- `dev-story` - Execute Dev Story workflow, implementing tasks and tests
 - `code-review` - Perform thorough clean context QA code review on a story
 
 **Communication Style:** Direct and energetic. Execution-focused. Breaks down complex game challenges into actionable steps. Celebrates performance wins.
@@ -644,7 +646,7 @@ Many workflows have optional validation workflows that perform independent revie
 | -------------------------- | ----------- | ------------------------------------------ |
 | `implementation-readiness` | Architect   | PRD + Architecture + Epics + UX (optional) |
 | `validate-design`          | UX Designer | UX specification and artifacts             |
-| `validate-create-story`    | SM          | Story draft                                |
+| `validate-create-story`    | SM          | Story file                                 |
 
 **When to use validation:**
 
@@ -661,14 +663,14 @@ You can customize any agent's personality without modifying core agent files.
 
 ### Location
 
-**Customization Directory:** `{project-root}/.bmad/_cfg/agents/`
+**Customization Directory:** `{project-root}/_bmad/_config/agents/`
 
 **Naming Convention:** `{module}-{agent-name}.customize.yaml`
 
 **Examples:**
 
 ```
-.bmad/_cfg/agents/
+_bmad/_config/agents/
 ├── bmm-pm.customize.yaml
 ├── bmm-dev.customize.yaml
 ├── cis-storyteller.customize.yaml
@@ -768,9 +770,9 @@ Other agents collaborate with PM's specialized perspective.
 
 ```bash
 # Create customization file at:
-# {project-root}/.bmad/_cfg/agents/{module}-{agent-name}.customize.yaml
+# {project-root}/_bmad/_config/agents/{module}-{agent-name}.customize.yaml
 
-# Example: .bmad/_cfg/agents/bmm-pm.customize.yaml
+# Example: _bmad/_config/agents/bmm-pm.customize.yaml
 ```
 
 **Step 2: Regenerate Agent Manifest**
@@ -900,7 +902,7 @@ Load the customized agent and verify the changes are reflected in its behavior a
 
 ```
 1. SM: *create-story
-2. DEV: *develop-story
+2. DEV: *dev-story
 3. DEV: *code-review
 4. Repeat steps 1-3 for next story
 ```
@@ -910,7 +912,7 @@ Load the customized agent and verify the changes are reflected in its behavior a
 ```
 1. TEA: *framework (once per project, early)
 2. TEA: *atdd (before implementing features)
-3. DEV: *develop-story (includes tests)
+3. DEV: *dev-story (includes tests)
 4. TEA: *automate (comprehensive test suite)
 5. TEA: *trace (quality gate)
 6. TEA: *ci (pipeline setup)
@@ -975,12 +977,12 @@ Quick reference for agent selection:
 | **UX Designer**         | 🎨   | 2 (Planning)            | create-ux-design, validate-design             | UX-heavy projects, design               |
 | **Architect**           | 🏗️   | 3 (Solutioning)         | architecture, implementation-readiness        | Technical design, architecture          |
 | **SM**                  | 🏃   | 4 (Implementation)      | sprint-planning, create-story                 | Story management, sprint coordination   |
-| **DEV**                 | 💻   | 4 (Implementation)      | develop-story, code-review                    | Implementation, coding                  |
+| **DEV**                 | 💻   | 4 (Implementation)      | dev-story, code-review                        | Implementation, coding                  |
 | **TEA**                 | 🧪   | All Phases              | framework, atdd, automate, trace, ci          | Testing, quality assurance              |
 | **Paige (Tech Writer)** | 📚   | All Phases              | document-project, diagrams, validation        | Documentation, diagrams                 |
 | **Principal Engineer**  | ⚡   | Quick Flow (All phases) | create-tech-spec, quick-dev, code-review      | Rapid development, technical leadership |
 | **Game Designer**       | 🎲   | 1-2 (Games)             | brainstorm-game, gdd, narrative               | Game design, creative vision            |
-| **Game Developer**      | 🕹️   | 4 (Games)               | develop-story, code-review                    | Game implementation                     |
+| **Game Developer**      | 🕹️   | 4 (Games)               | dev-story, code-review                        | Game implementation                     |
 | **Game Architect**      | 🏛️   | 3 (Games)               | architecture, implementation-readiness        | Game systems architecture               |
 | **BMad Master**         | 🧙   | Meta                    | party-mode, list tasks/workflows              | Orchestration, multi-agent              |
 
@@ -1070,7 +1072,7 @@ Quick reference for agent selection:
 
 - [ ] SM: `*sprint-planning` (once)
 - [ ] SM: `*create-story`
-- [ ] DEV: `*develop-story`
+- [ ] DEV: `*dev-story`
 - [ ] DEV: `*code-review`
 
 **Testing Strategy:**

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/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/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/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/core/tasks/index-docs.xml --directory ./docs
+_bmad/core/tasks/index-docs.xml --directory ./docs
 ```
 
 **Step 3: Validate**
@@ -340,7 +340,7 @@ flowchart TD
 **Status Progression:**
 
 - Epic: `backlog → in-progress → done`
-- Story: `backlog → drafted → ready-for-dev → in-progress → review → done`
+- Story: `backlog → ready-for-dev → in-progress → review → done`
 
 **Brownfield-Specific Implementation Tips:**
 
@@ -397,7 +397,7 @@ Document in tech-spec/architecture:
 ### 8. Use Sprint Planning Effectively
 
 - Run `sprint-planning` at Phase 4 start
-- Context epics before drafting stories
+- Context epics before creating stories
 - Update `sprint-status.yaml` as work progresses
 
 ### 9. Learn Continuously

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/` 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/
+# 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/, load agents normally
+# BMad available at ./_bmad/, load agents normally
 ```
 
 **Update personal config:**