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

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

@@ -2,7 +2,7 @@
 
 # CI/CD Pipeline Setup
 
-**Workflow ID**: `bmad/bmm/testarch/ci`
+**Workflow ID**: `.bmad/bmm/testarch/ci`
 **Version**: 4.0 (BMad v6)
 
 ---
@@ -353,7 +353,7 @@ Scaffolds a production-ready CI/CD quality pipeline with test execution, burn-in
 
 ### Knowledge Base Integration
 
-**Critical:** Consult `{project-root}/bmad/bmm/testarch/tea-index.csv` to identify and load relevant knowledge fragments:
+**Critical:** Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` to identify and load relevant knowledge fragments:
 
 - `ci-burn-in.md` - Burn-in loop patterns: 10-iteration detection, GitHub Actions workflow, shard orchestration, selective execution (678 lines, 4 examples)
 - `selective-testing.md` - Changed test detection strategies: tag-based, spec filters, diff-based selection, promotion rules (727 lines, 4 examples)

package/{bmad → .bmad}/bmm/workflows/testarch/ci/workflow.yaml

@@ -4,7 +4,7 @@ description: "Scaffold CI/CD quality pipeline with test execution, burn-in loops
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/testarch/ci"
+installed_path: "{project-root}/.bmad/bmm/workflows/testarch/ci"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 

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

@@ -2,7 +2,7 @@
 
 # Test Framework Setup
 
-**Workflow ID**: `bmad/bmm/testarch/framework`
+**Workflow ID**: `.bmad/bmm/testarch/framework`
 **Version**: 4.0 (BMad v6)
 
 ---
@@ -349,7 +349,7 @@ The generated `tests/README.md` should include:
 
 ### Knowledge Base Integration
 
-**Critical:** Consult `{project-root}/bmad/bmm/testarch/tea-index.csv` to identify and load relevant knowledge fragments:
+**Critical:** Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` to identify and load relevant knowledge fragments:
 
 - `fixture-architecture.md` - Pure function → fixture → `mergeTests` composition with auto-cleanup (406 lines, 5 examples)
 - `data-factories.md` - Faker-based factories with overrides, nested factories, API seeding, auto-cleanup (498 lines, 5 examples)

package/{bmad → .bmad}/bmm/workflows/testarch/framework/workflow.yaml

@@ -4,7 +4,7 @@ description: "Initialize production-ready test framework architecture (Playwrigh
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/testarch/framework"
+installed_path: "{project-root}/.bmad/bmm/workflows/testarch/framework"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 

package/{bmad → .bmad}/bmm/workflows/testarch/nfr-assess/instructions.md

@@ -50,7 +50,7 @@ This workflow performs a comprehensive assessment of non-functional requirements
 
 **Actions:**
 
-1. Load relevant knowledge fragments from `{project-root}/bmad/bmm/testarch/tea-index.csv`:
+1. Load relevant knowledge fragments from `{project-root}/.bmad/bmm/testarch/tea-index.csv`:
    - `nfr-criteria.md` - Non-functional requirements criteria and thresholds (security, performance, reliability, maintainability with code examples, 658 lines, 4 examples)
    - `ci-burn-in.md` - CI/CD burn-in patterns for reliability validation (10-iteration detection, sharding, selective execution, 678 lines, 4 examples)
    - `test-quality.md` - Test quality expectations for maintainability (deterministic, isolated, explicit assertions, length/time limits, 658 lines, 5 examples)

package/{bmad → .bmad}/bmm/workflows/testarch/nfr-assess/workflow.yaml

@@ -4,7 +4,7 @@ description: "Assess non-functional requirements (performance, security, reliabi
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/testarch/nfr-assess"
+installed_path: "{project-root}/.bmad/bmm/workflows/testarch/nfr-assess"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 template: "{installed_path}/nfr-report-template.md"

package/{bmad → .bmad}/bmm/workflows/testarch/test-design/instructions.md

@@ -2,7 +2,7 @@
 
 # Test Design and Risk Assessment
 
-**Workflow ID**: `bmad/bmm/testarch/test-design`
+**Workflow ID**: `.bmad/bmm/testarch/test-design`
 **Version**: 4.0 (BMad v6)
 
 ---
@@ -48,7 +48,7 @@ Plans comprehensive test coverage strategy with risk assessment, priority classi
 
 4. **Load Knowledge Base Fragments**
 
-   **Critical:** Consult `{project-root}/bmad/bmm/testarch/tea-index.csv` to load:
+   **Critical:** Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` to load:
    - `risk-governance.md` - Risk classification framework (6 categories: TECH, SEC, PERF, DATA, BUS, OPS), automated scoring, gate decision engine, owner tracking (625 lines, 4 examples)
    - `probability-impact.md` - Risk scoring methodology (probability × impact matrix, automated classification, dynamic re-assessment, gate integration, 604 lines, 4 examples)
    - `test-levels-framework.md` - Test level selection guidance (E2E vs API vs Component vs Unit with decision matrix, characteristics, when to use each, 467 lines, 4 examples)

package/{bmad → .bmad}/bmm/workflows/testarch/test-design/test-design-template.md

@@ -281,5 +281,5 @@
 ---
 
 **Generated by**: BMad TEA Agent - Test Architect Module
-**Workflow**: `bmad/bmm/testarch/test-design`
+**Workflow**: `.bmad/bmm/testarch/test-design`
 **Version**: 4.0 (BMad v6)

package/{bmad → .bmad}/bmm/workflows/testarch/test-design/workflow.yaml

@@ -4,7 +4,7 @@ description: "Plan risk mitigation and test coverage strategy before development
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/testarch/test-design"
+installed_path: "{project-root}/.bmad/bmm/workflows/testarch/test-design"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 template: "{installed_path}/test-design-template.md"

package/{bmad → .bmad}/bmm/workflows/testarch/test-review/instructions.md

@@ -49,7 +49,7 @@ This workflow performs comprehensive test quality reviews using TEA's knowledge
 
 **Actions:**
 
-1. Load relevant knowledge fragments from `{project-root}/bmad/bmm/testarch/tea-index.csv`:
+1. Load relevant knowledge fragments from `{project-root}/.bmad/bmm/testarch/tea-index.csv`:
    - `test-quality.md` - Definition of Done (deterministic tests, isolated with cleanup, explicit assertions, <300 lines, <1.5 min, 658 lines, 5 examples)
    - `fixture-architecture.md` - Pure function → Fixture → mergeTests composition with auto-cleanup (406 lines, 5 examples)
    - `network-first.md` - Route intercept before navigate to prevent race conditions (intercept before navigate, HAR capture, deterministic waiting, 489 lines, 5 examples)

package/{bmad → .bmad}/bmm/workflows/testarch/test-review/workflow.yaml

@@ -4,7 +4,7 @@ description: "Review test quality using comprehensive knowledge base and best pr
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/testarch/test-review"
+installed_path: "{project-root}/.bmad/bmm/workflows/testarch/test-review"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 template: "{installed_path}/test-review-template.md"

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

@@ -64,7 +64,7 @@ This phase focuses on mapping requirements to tests, analyzing coverage, and ide
 
 **Actions:**
 
-1. Load relevant knowledge fragments from `{project-root}/bmad/bmm/testarch/tea-index.csv`:
+1. Load relevant knowledge fragments from `{project-root}/.bmad/bmm/testarch/tea-index.csv`:
    - `test-priorities-matrix.md` - P0/P1/P2/P3 risk framework with automated priority calculation, risk-based mapping, tagging strategy (389 lines, 2 examples)
    - `risk-governance.md` - Risk-based testing approach: 6 categories (TECH, SEC, PERF, DATA, BUS, OPS), automated scoring, gate decision engine, coverage traceability (625 lines, 4 examples)
    - `probability-impact.md` - Risk scoring methodology: probability × impact matrix, automated classification, dynamic re-assessment, gate integration (604 lines, 4 examples)
@@ -126,9 +126,9 @@ This phase focuses on mapping requirements to tests, analyzing coverage, and ide
 2. Build traceability matrix:
 
    ```
-   | Criterion ID | Description | Test ID | Test File | Test Level | Coverage Status |
-   |--------------|-------------|---------|-----------|------------|-----------------|
-   | AC-1         | User can... | 1.3-E2E-001 | e2e/auth.spec.ts | E2E | FULL |
+   | Criterion ID | Description | Test ID     | Test File        | Test Level | Coverage Status |
+   | ------------ | ----------- | ----------- | ---------------- | ---------- | --------------- |
+   | AC-1         | User can... | 1.3-E2E-001 | e2e/auth.spec.ts | E2E        | FULL            |
    ```
 
 3. Classify coverage status for each criterion:
@@ -476,10 +476,10 @@ This phase uses traceability results to make a quality gate decision (PASS/CONCE
 
 ## References
 
-- Traceability Matrix: `bmad/output/traceability-matrix.md`
-- Test Design: `bmad/output/test-design-epic-2.md`
+- Traceability Matrix: `.bmad/output/traceability-matrix.md`
+- Test Design: `.bmad/output/test-design-epic-2.md`
 - Test Results: `ci-artifacts/test-report-2025-01-15.xml`
-- NFR Assessment: `bmad/output/nfr-assessment-release-1.2.md`
+- NFR Assessment: `.bmad/output/nfr-assessment-release-1.2.md`
 ```
 
 3. **Include evidence links** (if `require_evidence: true`):
@@ -515,7 +515,7 @@ This phase uses traceability results to make a quality gate decision (PASS/CONCE
 
      - **Decision**: CONCERNS
      - **Reason**: P1 coverage 88% (below 90%)
-     - **Document**: [gate-decision-story-1.3.md](bmad/output/gate-decision-story-1.3.md)
+     - **Document**: [gate-decision-story-1.3.md](.bmad/output/gate-decision-story-1.3.md)
      - **Action**: Deploy with follow-up story for AC-5
      ```
 
@@ -536,7 +536,7 @@ This phase uses traceability results to make a quality gate decision (PASS/CONCE
    - Create follow-up story for AC-5 E2E test
    - Deploy to staging for validation
 
-   Full Report: bmad/output/gate-decision-story-1.3.md
+   Full Report: .bmad/output/gate-decision-story-1.3.md
    ```
 
 3. **Request sign-off** (if `require_sign_off: true`):

package/{bmad → .bmad}/bmm/workflows/testarch/trace/workflow.yaml

@@ -4,7 +4,7 @@ description: "Generate requirements-to-tests traceability matrix, analyze covera
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/testarch/trace"
+installed_path: "{project-root}/.bmad/bmm/workflows/testarch/trace"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 template: "{installed_path}/trace-template.md"

package/{bmad → .bmad}/bmm/workflows/workflow-status/init/instructions.md

@@ -1,6 +1,6 @@
 # Workflow Init - Project Setup 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: workflow-init/workflow.yaml</critical>
 <critical>Communicate in {communication_language} with {user_name}</critical>
 <critical>This workflow handles BOTH new projects AND legacy projects being migrated to BMad Method</critical>
@@ -317,6 +317,56 @@ Your choice [1/2/3]:</ask>
 - Default to "software" if not clearly a game
   </action>
 
+<check if="project_type == game">
+  <output>
+  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+🎮 **GAME DEVELOPMENT DETECTED**
+
+Game development workflows are now part of the **BMad Game Development (BMGD)** module.
+
+The BMM module is designed for software development. For game development, you'll need
+the BMGD module which provides specialized game development workflows and agents.
+
+**Would you like to:**
+a) Install BMGD module now (recommended for game projects)
+b) Continue with BMM workflows (for software projects only)
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+</output>
+
+<ask>Your choice [a/b]:</ask>
+
+  <check if="choice == a">
+    <output>
+    Please run the following command to install the BMGD module:
+
+    ```bash
+    bmad install bmgd
+    ```
+
+    After installation, you can start your game development workflow with the Game Designer agent.
+
+    This workflow-init will now exit. Re-run it after installing BMGD.
+    </output>
+    <action>Exit workflow with success status</action>
+
+  </check>
+
+  <check if="choice == b">
+    <output>
+    ⚠️ **Warning:** BMM workflows are optimized for software development, not game development.
+
+    You may encounter mismatched terminology and workflows. Consider installing BMGD for
+    a better game development experience.
+
+    Continuing with software development workflows...
+    </output>
+    <action>Set project_type = "software" (override game detection)</action>
+
+  </check>
+</check>
+
 <template-output>user_description</template-output>
 <template-output>field_type</template-output>
 <template-output>project_type</template-output>
@@ -597,8 +647,9 @@ For each phase in path file:
 2. Add comment header: `  # Phase {n}: {Phase Name}`
 3. For each workflow in phase:
    - Check if workflow should be included based on user choices
-   - Add entry: `  {workflow-id}: {default_status}`
+   - Add entry: `  {workflow-id}: {default_status}  # agent: {agent}`
    - Default status from path file (required/optional/recommended/conditional)
+   - Agent from path file (pm/architect/ux-designer/sm/analyst/etc.)
 4. Add blank line between phases
    </action>
 
@@ -616,8 +667,8 @@ For each phase in path file:
 - Architecture: {output*folder}/\_architecture*.md or {output*folder}/\_arch*.md
 - Sprint Planning: {output*folder}/\_sprint*.yaml
 
-**CRITICAL:** If file exists, replace workflow status with ONLY the file path.
-Example: `prd: docs/prd.md` (NOT "completed - docs/prd.md")
+**CRITICAL:** If file exists, replace workflow status with ONLY the file path, preserving agent comment.
+Example: `prd: docs/prd.md  # agent: pm` (NOT "completed - docs/prd.md")
 </action>
 
 <template-output>workflow_path_file</template-output>
@@ -642,60 +693,60 @@ Example: `prd: docs/prd.md` (NOT "completed - docs/prd.md")
 
 {{#if brownfield AND needs_documentation}}
 🔧 **Prerequisites:**
-✅ document-project - Create comprehensive codebase documentation
+✅ document-project - Create comprehensive codebase documentation (analyst agent)
 (Required before planning workflows)
 {{/if}}
 
 {{#if has_discovery_phase}}
 🧠 **Phase 0: Discovery** (Optional - based on your choices)
 {{#if brainstorm_requested}}
-✅ Brainstorm - Creative exploration session
+✅ Brainstorm - Creative exploration session (analyst agent)
 {{/if}}
 {{#if research_requested}}
-✅ Research - Domain and technical research
+✅ Research - Domain and technical research (analyst agent)
 {{/if}}
 {{#if product_brief_requested}}
-✅ Product Brief - Strategic product planning
+✅ Product Brief - Strategic product planning (analyst agent)
 {{/if}}
 {{/if}}
 
 {{#if selected_track == quick-flow}}
 📝 **Phase 1: Planning**
-✅ Tech-Spec - Implementation-focused specification
+✅ Tech-Spec - Implementation-focused specification (pm agent)
 (Auto-detects epic structure if 2+ stories)
 
 🚀 **Phase 2: Implementation**
-✅ Sprint Planning - Create sprint tracking
-✅ Story Development - Implement story-by-story
+✅ Sprint Planning - Create sprint tracking (sm agent)
+✅ Story Development - Implement story-by-story (sm agent)
 {{/if}}
 
 {{#if selected_track in [method, enterprise]}}
 📋 **Phase 1: Planning**
-✅ PRD - Product Requirements Document
-✅ Validate PRD (optional quality check)
-✅ UX Design (if UI components - determined after PRD)
+✅ PRD - Product Requirements Document (pm agent)
+✅ Validate PRD (optional quality check) (pm agent)
+✅ UX Design (if UI components - determined after PRD) (ux-designer agent)
 
 🏗️ **Phase 2: Solutioning**
 {{#if brownfield}}
-✅ Architecture - Integration design (RECOMMENDED for brownfield)
+✅ Architecture - Integration design (RECOMMENDED for brownfield) (architect agent)
 Creates focused solution design from your existing codebase context
 {{else}}
-✅ Architecture - System design document
+✅ Architecture - System design document (architect agent)
 {{/if}}
-✅ Validate Architecture (optional quality check)
-✅ Solutioning Gate Check - Validate all planning aligns before coding
+✅ Validate Architecture (optional quality check) (architect agent)
+✅ Solutioning Gate Check - Validate all planning aligns before coding (architect agent)
 
 🚀 **Phase 3: Implementation**
-✅ Sprint Planning - Create sprint tracking
-✅ Story Development - Implement story-by-story with epic-tech-specs
+✅ Sprint Planning - Create sprint tracking (sm agent)
+✅ Story Development - Implement story-by-story with epic-tech-specs (sm agent)
 {{/if}}
 
 {{#if selected_track == enterprise}}
 
 🏢 **Additional Enterprise Planning:**
-✅ Security Architecture - Threat modeling and security design
-✅ DevOps Strategy - Pipeline and infrastructure planning
-✅ Test Strategy - Comprehensive testing approach
+✅ Security Architecture - Threat modeling and security design (architect agent)
+✅ DevOps Strategy - Pipeline and infrastructure planning (architect agent)
+✅ Test Strategy - Comprehensive testing approach (tea agent)
 {{/if}}
 
 {{#if found_existing_artifacts}}

package/{bmad → .bmad}/bmm/workflows/workflow-status/init/workflow.yaml

@@ -4,7 +4,7 @@ description: "Initialize a new BMM project by determining level, type, and creat
 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"
 project_name: "{config_source}:project_name"
@@ -14,12 +14,12 @@ user_skill_level: "{config_source}:user_skill_level"
 date: system-generated
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/workflow-status/init"
+installed_path: "{project-root}/.bmad/bmm/workflows/workflow-status/init"
 instructions: "{installed_path}/instructions.md"
-template: "{project-root}/bmad/bmm/workflows/workflow-status/workflow-status-template.yaml"
+template: "{project-root}/.bmad/bmm/workflows/workflow-status/workflow-status-template.yaml"
 
 # Path data files
-path_files: "{project-root}/bmad/bmm/workflows/workflow-status/paths/"
+path_files: "{project-root}/.bmad/bmm/workflows/workflow-status/paths/"
 
 # Output configuration
 default_output_file: "{output_folder}/bmm-workflow-status.yaml"

package/{bmad → .bmad}/bmm/workflows/workflow-status/instructions.md

@@ -1,7 +1,7 @@
 # Workflow Status Check - Multi-Mode Service
 
-<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/workflow-status/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml</critical>
 <critical>This workflow operates in multiple modes: interactive (default), validate, data, init-check, update</critical>
 <critical>Other workflows can call this as a service to avoid duplicating status logic</critical>
 
@@ -79,6 +79,7 @@ Parse these fields from YAML comments and metadata:
 <action>Load workflow path file based on workflow_path field</action>
 <action>Identify current phase from next workflow to be done</action>
 <action>Build list of completed, pending, and optional workflows</action>
+<action>For each workflow, look up its agent from the path file</action>
 
 <output>
 ## 📊 Current Status
@@ -93,7 +94,7 @@ Parse these fields from YAML comments and metadata:
 {{phase_name}}:
 {{#each workflows_in_phase}}
 
-- {{workflow_name}}: {{status_display}}
+- {{workflow_name}} ({{agent}}): {{status_display}}
   {{/each}}
   {{/each}}
 
@@ -118,7 +119,7 @@ Parse these fields from YAML comments and metadata:
 <step n="4" goal="Offer actions">
 <ask>What would you like to do?
 
-1. **Start next workflow** - {{next_workflow_name}} ({{next_agent}} agent)
+1. **Start next workflow** - {{next_workflow_name}} ({{next_agent}})
    {{#if optional_workflows_available}}
 2. **Run optional workflow** - Choose from available options
    {{/if}}

package/{bmad → .bmad}/bmm/workflows/workflow-status/paths/enterprise-brownfield.yaml

@@ -66,6 +66,20 @@ phases:
         command: "create-design"
         note: "Recommended - must integrate with existing UX patterns"
 
+      - id: "framework"
+        optional: true
+        agent: "tea"
+        command: "framework"
+        output: "Test framework scaffold (Playwright/Cypress)"
+        note: "Initialize or modernize test framework - critical if brownfield lacks proper test infrastructure"
+
+      - id: "ci"
+        optional: true
+        agent: "tea"
+        command: "ci"
+        output: "CI/CD test pipeline configuration"
+        note: "Establish or enhance CI pipeline with regression testing strategy"
+
   - phase: 2
     name: "Solutioning"
     required: true
@@ -78,25 +92,18 @@ phases:
         note: "Distills brownfield context + adds security/scalability/compliance design"
 
       - id: "create-security-architecture"
-        required: true
+        optional: true
         agent: "architect"
         command: "create-security-architecture"
         output: "Security architecture for brownfield integration"
-        note: "Future workflow - threat model, auth integration, audit requirements"
+        note: "Future workflow - optional extended enterprise workflow for threat model, auth integration, audit requirements"
 
       - id: "create-devops-strategy"
-        required: true
+        optional: true
         agent: "architect"
         command: "create-devops-strategy"
         output: "DevOps strategy for brownfield deployment"
-        note: "Future workflow - CI/CD integration, deployment strategy, monitoring"
-
-      - id: "create-test-strategy"
-        required: true
-        agent: "tea"
-        command: "create-test-strategy"
-        output: "Test strategy including regression testing"
-        note: "Future workflow - critical for brownfield to prevent breaking existing functionality"
+        note: "Future workflow - optional extended enterprise workflow for CI/CD integration, deployment strategy, monitoring"
 
       - id: "validate-architecture"
         optional: true

package/{bmad → .bmad}/bmm/workflows/workflow-status/paths/enterprise-greenfield.yaml

@@ -54,6 +54,20 @@ phases:
         command: "create-design"
         note: "Highly recommended for enterprise - design system and patterns"
 
+      - id: "framework"
+        optional: true
+        agent: "tea"
+        command: "framework"
+        output: "Test framework scaffold (Playwright/Cypress)"
+        note: "Initialize production-ready test framework - run once per project"
+
+      - id: "ci"
+        optional: true
+        agent: "tea"
+        command: "ci"
+        output: "CI/CD test pipeline configuration"
+        note: "Scaffold CI workflow with selective testing, burn-in, caching"
+
   - phase: 2
     name: "Solutioning"
     required: true
@@ -66,25 +80,18 @@ phases:
         note: "Includes scalability, multi-tenancy, integration architecture"
 
       - id: "create-security-architecture"
-        required: true
+        optional: true
         agent: "architect"
         command: "create-security-architecture"
         output: "Security architecture and threat model"
-        note: "Future workflow - security design, auth, compliance"
+        note: "Future workflow - optional extended enterprise workflow for security design, auth, compliance"
 
       - id: "create-devops-strategy"
-        required: true
+        optional: true
         agent: "architect"
         command: "create-devops-strategy"
         output: "DevOps pipeline and infrastructure plan"
-        note: "Future workflow - CI/CD, deployment, monitoring"
-
-      - id: "create-test-strategy"
-        required: true
-        agent: "tea"
-        command: "create-test-strategy"
-        output: "Comprehensive test strategy"
-        note: "Future workflow - test approach, automation, quality gates"
+        note: "Future workflow - optional extended enterprise workflow for CI/CD, deployment, monitoring"
 
       - id: "validate-architecture"
         optional: true

package/.bmad/bmm/workflows/workflow-status/paths/game-design.yaml

@@ -0,0 +1,52 @@
+# Game Development - Use BMGD Module
+# Game development workflows have been moved to the BMad Game Development module
+
+project_type: "game"
+level: "all"
+field_type: "any"
+description: "⚠️ Game development requires the BMGD module"
+
+error_message: |
+  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+  🎮 **GAME DEVELOPMENT DETECTED**
+
+  Game development workflows are now part of the **BMad Game Development (BMGD)** module,
+  which provides specialized workflows and agents for game creation.
+
+  **To proceed with game development:**
+
+  1. Install the BMGD module:
+     ```bash
+     bmad install bmgd
+     ```
+
+  2. The BMGD module includes:
+     - Game Designer, Game Developer, Game Architect agents
+     - Game Dev Scrum Master for sprint coordination
+     - Industry-standard game dev workflows:
+       • Phase 1 (Preproduction): brainstorm-game, game-brief
+       • Phase 2 (Design): GDD, narrative design
+       • Phase 3 (Technical): game architecture
+       • Phase 4 (Production): sprint planning, story management
+
+  3. After installation, load the Game Designer or Game Dev Scrum Master agent
+     to begin your game development workflow
+
+  **Why a separate module?**
+  - Game development follows different phases than software development
+  - Specialized agents understand game-specific terminology and patterns
+  - Workflows configured for game development needs (playtesting, balancing, etc.)
+  - Can be used standalone or alongside BMM for complete coverage
+
+  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+# Placeholder phases - this file should not be used for actual workflow tracking
+# Users should install BMGD module instead
+phases:
+  - phase: 1
+    name: "ERROR - Install BMGD Module"
+    workflows:
+      - id: "install-bmgd"
+        required: true
+        note: "Run: bmad install bmgd"

package/{bmad → .bmad}/bmm/workflows/workflow-status/project-levels.yaml

@@ -1,5 +1,5 @@
 # BMM Project Scale Levels - Source of Truth
-# Reference: /bmad/bmm/README.md lines 77-85
+# Reference: /.bmad/bmm/README.md lines 77-85
 
 levels:
   0: