bmad-method 6.0.0-alpha.5 → 6.0.0-alpha.7

package/src/modules/bmm/workflows/1-analysis/domain-research/workflow.yaml

@@ -1,36 +1,69 @@
-workflow:
-  id: domain-research
-  name: "Domain Research"
-  module: bmm
-  version: "6.0.0-alpha"
+# Domain Research Workflow Configuration
+name: domain-research
+description: "Collaborative exploration of domain-specific requirements, regulations, and patterns for complex projects"
+author: "BMad"
+
+# Critical variables from config
+config_source: "{project-root}/bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+user_skill_level: "{config_source}:user_skill_level"
+date: system-generated
+
+# Module path and component files
+installed_path: "{project-root}/bmad/bmm/workflows/1-analysis/domain-research"
+instructions: "{installed_path}/instructions.md"
+template: "{installed_path}/template.md"
+
+# Optional knowledge base (if exists)
+domain_knowledge_base: "{installed_path}/domain-knowledge-base.md"
+
+# Output configuration
+default_output_file: "{output_folder}/domain-brief.md"
+
+# Workflow metadata
+version: "6.0.0-alpha"
+category: "analysis"
+complexity: "medium"
+execution_time: "30-45 minutes"
+prerequisites:
+  - "Basic project understanding"
+when_to_use:
+  - "Complex regulated domains (healthcare, finance, aerospace)"
+  - "Novel technical domains requiring deep understanding"
+  - "Before PRD when domain expertise needed"
+  - "When compliance and regulations matter"
+
+standalone: true
+
+# Web bundle configuration for standalone deployment
+web_bundle:
+  name: "domain-research"
   description: "Collaborative exploration of domain-specific requirements, regulations, and patterns for complex projects"
+  author: "BMad"
 
-  environment:
-    # Inherit from parent workflow or set defaults
-    user_name: "partner"
-    user_skill_level: "intermediate"
+  # Core workflow files (bmad/-relative paths)
+  instructions: "bmad/bmm/workflows/1-analysis/domain-research/instructions.md"
+  template: "bmad/bmm/workflows/1-analysis/domain-research/template.md"
+
+  # Default configuration values (can be overridden during bundle setup)
+  defaults:
+    user_name: "User"
     communication_language: "English"
     document_output_language: "English"
-    date: "{system.date}"
-
-  required_files:
-    - instructions.md
-    - template.md
-
-  optional_files:
-    - domain-knowledge-base.md
-
-  outputs:
-    - domain-brief.md
-
-  metadata:
-    category: "analysis"
-    complexity: "medium"
-    estimated_time: "30-45 minutes"
-    prerequisites:
-      - "Basic project understanding"
-    when_to_use:
-      - "Complex regulated domains (healthcare, finance, aerospace)"
-      - "Novel technical domains requiring deep understanding"
-      - "Before PRD when domain expertise needed"
-      - "When compliance and regulations matter"
+    user_skill_level: "intermediate"
+    output_folder: "./output"
+
+  # Input/output configuration for web deployment
+  default_output_file: "{output_folder}/domain-brief.md"
+
+  # Complete file list - ALL files this workflow depends on
+  web_bundle_files:
+    # Core workflow files
+    - "bmad/bmm/workflows/1-analysis/domain-research/instructions.md"
+    - "bmad/bmm/workflows/1-analysis/domain-research/template.md"
+
+    # Task dependencies (referenced in instructions.md)
+    - "bmad/core/tasks/workflow.xml"

package/src/modules/bmm/workflows/1-analysis/product-brief/workflow.yaml

@@ -52,6 +52,10 @@ web_bundle:
   validation: "bmad/bmm/workflows/1-analysis/product-brief/checklist.md"
   template: "bmad/bmm/workflows/1-analysis/product-brief/template.md"
   web_bundle_files:
+    # Core workflow files
     - "bmad/bmm/workflows/1-analysis/product-brief/template.md"
     - "bmad/bmm/workflows/1-analysis/product-brief/instructions.md"
     - "bmad/bmm/workflows/1-analysis/product-brief/checklist.md"
+
+    # Task dependencies (referenced in instructions.md)
+    - "bmad/core/tasks/workflow.xml"

package/src/modules/bmm/workflows/1-analysis/research/instructions-market.md

@@ -663,7 +663,7 @@ Would you like me to strengthen any areas with additional research?"
 {{#if standalone_mode != true}}
 
 - **Next workflow:** {{next_workflow}} ({{next_agent}} agent)
-- **Optional:** Review findings with stakeholders, or run additional analysis workflows (product-brief, game-brief, etc.)
+- **Optional:** Review findings with stakeholders, or run additional analysis workflows (product-brief for software, or install BMGD module for game-brief)
 
 Check status anytime with: `workflow-status`
 {{else}}

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml

@@ -51,14 +51,43 @@ instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 template: "{installed_path}/ux-design-template.md"
 
-# Knowledge bases for intelligent UX decisions
-ux_pattern_catalog: "{installed_path}/ux-pattern-catalog.yaml"
-color_psychology: "{installed_path}/color-psychology.yaml"
-layout_patterns: "{installed_path}/layout-patterns.yaml"
-
 # Output configuration - Progressive saves throughout workflow
 default_output_file: "{output_folder}/ux-design-specification.md"
 color_themes_html: "{output_folder}/ux-color-themes.html"
 design_directions_html: "{output_folder}/ux-design-directions.html"
 
 standalone: true
+
+# Web bundle configuration for standalone deployment
+web_bundle:
+  name: "create-ux-design"
+  description: "Collaborative UX design facilitation workflow that creates exceptional user experiences through visual exploration and informed decision-making. Unlike template-driven approaches, this workflow facilitates discovery, generates visual options, and collaboratively designs the UX with the user at every step."
+  author: "BMad"
+
+  # Core workflow files (bmad/-relative paths)
+  instructions: "bmad/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md"
+  validation: "bmad/bmm/workflows/2-plan-workflows/create-ux-design/checklist.md"
+  template: "bmad/bmm/workflows/2-plan-workflows/create-ux-design/ux-design-template.md"
+
+  # Default configuration values (can be overridden during bundle setup)
+  defaults:
+    user_name: "User"
+    communication_language: "English"
+    document_output_language: "English"
+    user_skill_level: "intermediate"
+    output_folder: "./output"
+
+  # Input/output configuration for web deployment
+  default_output_file: "{output_folder}/ux-design-specification.md"
+  color_themes_html: "{output_folder}/ux-color-themes.html"
+  design_directions_html: "{output_folder}/ux-design-directions.html"
+
+  # Complete file list - ALL files this workflow depends on
+  web_bundle_files:
+    # Core workflow files
+    - "bmad/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md"
+    - "bmad/bmm/workflows/2-plan-workflows/create-ux-design/checklist.md"
+    - "bmad/bmm/workflows/2-plan-workflows/create-ux-design/ux-design-template.md"
+
+    # Task dependencies (referenced in instructions.md)
+    - "bmad/core/tasks/workflow.xml"

package/src/modules/bmm/workflows/2-plan-workflows/prd/instructions.md

@@ -62,7 +62,7 @@ Project type signals: API, mobile, web, CLI, SDK, SaaS
 Domain complexity signals: medical, finance, government, education, aerospace
 
 SPECIAL ROUTING:
-If game detected → Suggest game-brief and GDD workflows
+If game detected → Inform user that game development requires the BMGD module (BMad Game Development)
 If complex domain detected → Offer domain research options:
 A) Run domain-research workflow (thorough)
 B) Quick web search (basic)

package/src/modules/bmm/workflows/2-plan-workflows/prd/workflow.yaml

@@ -52,13 +52,21 @@ web_bundle:
   instructions: "bmad/bmm/workflows/2-plan-workflows/prd/instructions.md"
   validation: "bmad/bmm/workflows/2-plan-workflows/prd/checklist.md"
   web_bundle_files:
+    # Core workflow files
     - "bmad/bmm/workflows/2-plan-workflows/prd/instructions.md"
     - "bmad/bmm/workflows/2-plan-workflows/prd/prd-template.md"
     - "bmad/bmm/workflows/2-plan-workflows/prd/project-types.csv"
     - "bmad/bmm/workflows/2-plan-workflows/prd/domain-complexity.csv"
     - "bmad/bmm/workflows/2-plan-workflows/prd/checklist.md"
+
+    # Child workflow and its files
     - "bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml"
     - "bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md"
     - "bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/epics-template.md"
+
+    # Task dependencies (referenced in instructions.md)
+    - "bmad/core/tasks/workflow.xml"
+    - "bmad/core/tasks/adv-elicit.xml"
+    - "bmad/core/tasks/adv-elicit-methods.csv"
   child_workflows:
     - create-epics-and-stories: "bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml"

package/src/modules/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml

@@ -65,9 +65,15 @@ web_bundle:
   author: "BMad"
   instructions: "bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions.md"
   web_bundle_files:
+    # Core workflow files
     - "bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions.md"
     - "bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions-level0-story.md"
     - "bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions-level1-stories.md"
     - "bmad/bmm/workflows/2-plan-workflows/tech-spec/tech-spec-template.md"
     - "bmad/bmm/workflows/2-plan-workflows/tech-spec/user-story-template.md"
     - "bmad/bmm/workflows/2-plan-workflows/tech-spec/epics-template.md"
+
+    # Task dependencies (referenced in instructions.md)
+    - "bmad/core/tasks/workflow.xml"
+    - "bmad/core/tasks/adv-elicit.xml"
+    - "bmad/core/tasks/adv-elicit-methods.csv"

package/src/modules/bmm/workflows/3-solutioning/architecture/workflow.yaml

@@ -65,3 +65,50 @@ features:
   - "Implementation patterns for agent consistency"
 
 standalone: true
+
+# Web bundle configuration for standalone deployment
+web_bundle:
+  name: "architecture"
+  description: "Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts."
+  author: "BMad"
+
+  # Core workflow files (bmad/-relative paths)
+  instructions: "bmad/bmm/workflows/3-solutioning/architecture/instructions.md"
+  validation: "bmad/bmm/workflows/3-solutioning/architecture/checklist.md"
+  template: "bmad/bmm/workflows/3-solutioning/architecture/architecture-template.md"
+
+  # Knowledge base files for decision making
+  decision_catalog: "bmad/bmm/workflows/3-solutioning/architecture/decision-catalog.yaml"
+  architecture_patterns: "bmad/bmm/workflows/3-solutioning/architecture/architecture-patterns.yaml"
+  pattern_categories: "bmad/bmm/workflows/3-solutioning/architecture/pattern-categories.csv"
+
+  # Task dependencies
+  adv_elicit_task: "bmad/core/tasks/adv-elicit.xml"
+
+  # Default configuration values (can be overridden during bundle setup)
+  defaults:
+    user_name: "User"
+    communication_language: "English"
+    document_output_language: "English"
+    user_skill_level: "intermediate"
+    output_folder: "./output"
+
+  # Input/output configuration for web deployment
+  default_output_file: "{output_folder}/architecture.md"
+
+  # Complete file list - ALL files this workflow depends on
+  web_bundle_files:
+    # Core workflow files
+    - "bmad/bmm/workflows/3-solutioning/architecture/instructions.md"
+    - "bmad/bmm/workflows/3-solutioning/architecture/checklist.md"
+    - "bmad/bmm/workflows/3-solutioning/architecture/architecture-template.md"
+
+    # Knowledge base data files
+    - "bmad/bmm/workflows/3-solutioning/architecture/decision-catalog.yaml"
+    - "bmad/bmm/workflows/3-solutioning/architecture/architecture-patterns.yaml"
+    - "bmad/bmm/workflows/3-solutioning/architecture/pattern-categories.csv"
+
+    # Task dependencies (referenced in instructions.md)
+    - "bmad/core/tasks/workflow.xml"
+    - "bmad/core/tasks/adv-elicit.xml"
+    - "bmad/core/tasks/adv-elicit-methods.csv"

package/src/modules/bmm/workflows/techdoc/documentation-standards.md

@@ -5,10 +5,32 @@
 
 ---
 
-## CRITICAL RULE: CommonMark Strict Compliance
+## CRITICAL RULES
+
+### Rule 1: CommonMark Strict Compliance
 
 ALL documentation MUST follow CommonMark specification exactly. No exceptions.
 
+### Rule 2: NO TIME ESTIMATES
+
+NEVER document time estimates, durations, or completion times for any workflow, task, or activity. This includes:
+
+- Workflow execution time (e.g., "30-60 min", "2-8 hours")
+- Task duration estimates
+- Reading time estimates
+- Implementation time ranges
+- Any temporal measurements
+
+Time varies dramatically based on:
+
+- Project complexity
+- Team experience
+- Tooling and environment
+- Context switching
+- Unforeseen blockers
+
+**Instead:** Focus on workflow steps, dependencies, and outputs. Let users determine their own timelines.
+
 ### CommonMark Essentials
 
 **Headers:**
@@ -194,6 +216,7 @@ Apply in this hierarchy:
 Before finalizing ANY documentation:
 
 - [ ] CommonMark compliant (no violations)
+- [ ] NO time estimates anywhere (Critical Rule 2)
 - [ ] Headers in proper hierarchy
 - [ ] All code blocks have language tags
 - [ ] Links work and have descriptive text

package/src/modules/bmm/workflows/testarch/atdd/atdd-checklist-template.md

@@ -355,8 +355,8 @@ See `tea-index.csv` for complete knowledge fragment mapping.
 
 - Ask in team standup
 - Tag @{tea_agent_username} in Slack/Discord
-- Refer to `testarch/README.md` for workflow documentation
-- Consult `testarch/knowledge/` for testing best practices
+- Refer to `./bmm/docs/tea-README.md` for workflow documentation
+- Consult `./bmm/testarch/knowledge` for testing best practices
 
 ---
 

package/src/modules/bmm/workflows/workflow-status/init/instructions.md

@@ -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>

package/src/modules/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/src/modules/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/src/modules/bmm/workflows/workflow-status/paths/game-design.yaml

@@ -1,75 +1,52 @@
-# Game Design - All Levels
-# Game development follows a different path than software
+# 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 workflow - applies to all complexity levels"
+description: "⚠️ Game development requires the BMGD module"
 
-phases:
-  - phase: 1
-    name: "Analysis"
-    optional: true
-    workflows:
-      - id: "brainstorm-game"
-        optional: true
-        agent: "game-designer"
-        command: "brainstorm-game"
-      - id: "research"
-        optional: true
-        agent: "analyst"
-        command: "research"
-        note: "Market research, competitive analysis"
-      - id: "game-brief"
-        recommended: true
-        agent: "game-designer"
-        command: "game-brief"
-        output: "Game concept and vision document"
+error_message: |
+  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-  - phase: 2
-    name: "Planning"
-    required: true
-    workflows:
-      - id: "gdd"
-        required: true
-        agent: "pm"
-        command: "gdd"
-        output: "Game Design Document with features and mechanics"
-      - id: "tech-spec"
-        conditional: "if_level_0_1"
-        agent: "architect"
-        command: "tech-spec"
-        note: "For simpler games, jump to implementation"
+  🎮 **GAME DEVELOPMENT DETECTED**
 
-  - phase: 3
-    name: "Solutioning"
-    conditional: "if_level_3_4"
-    workflows:
-      - id: "create-architecture"
-        required: true
-        agent: "architect"
-        command: "create-architecture"
-        note: "Engine architecture, networking, systems"
-      - id: "validate-architecture"
-        optional: true
-        agent: "architect"
-        command: "validate-architecture"
-      - id: "solutioning-gate-check"
-        required: true
-        agent: "architect"
-        command: "solutioning-gate-check"
+  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:**
 
-  - phase: 4
-    name: "Implementation"
-    required: true
+  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: "sprint-planning"
+      - id: "install-bmgd"
         required: true
-        agent: "sm"
-        command: "sprint-planning"
-        note: "Creates sprint plan with all stories - subsequent work tracked in sprint plan output, not workflow-status"
-
-special_considerations:
-  - "Iterative playtesting throughout development"
-  - "Art and audio pipelines run parallel to code"
-  - "Balance and tuning as ongoing process"
+        note: "Run: bmad install bmgd"