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

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

@@ -0,0 +1,75 @@
+# Game Design - All Levels
+# Game development follows a different path than software
+
+project_type: "game"
+level: "all"
+field_type: "any"
+description: "Game development workflow - applies to all complexity levels"
+
+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"
+
+  - 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"
+
+  - 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"
+
+  - phase: 4
+    name: "Implementation"
+    required: true
+    workflows:
+      - id: "sprint-planning"
+        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"

package/{src/modules/bmm/workflows/workflow-status/paths/brownfield-level-3.yaml → bmad/bmm/workflows/workflow-status/paths/method-brownfield.yaml}

@@ -1,43 +1,49 @@
-# Brownfield Level 3 - Complex Integration with Existing System
-# Major feature addition requiring architectural integration
+# BMad Method - Brownfield
+# Full product + architecture planning for complex brownfield additions (10-50+ stories typically)
 
-project_type: "software"
-level: 3
+method_name: "BMad Method"
+track: "method"
 field_type: "brownfield"
-description: "Complex integration with existing system architecture"
+description: "Complete product and system design for complex brownfield work"
 
 phases:
   - prerequisite: true
     name: "Documentation"
     conditional: "if_undocumented"
-    note: "NOT a phase - prerequisite for brownfield without docs OR post-completion cleanup"
+    note: "NOT a phase - prerequisite for brownfield without docs"
     workflows:
       - id: "document-project"
         required: true
         agent: "analyst"
         command: "document-project"
         output: "Comprehensive project documentation"
-        purpose: "Understand existing codebase before planning OR create superior final docs after Phase 4"
+        purpose: "Understand existing codebase before planning"
 
-  - phase: 1
-    name: "Analysis"
-    recommended: true
+  - phase: 0
+    name: "Discovery (Optional)"
+    optional: true
+    note: "User-selected during workflow-init"
     workflows:
       - id: "brainstorm-project"
         optional: true
         agent: "analyst"
         command: "brainstorm-project"
+        included_by: "user_choice"
+
       - id: "research"
-        recommended: true
+        optional: true
         agent: "analyst"
         command: "research"
-        note: "Research existing architecture patterns"
+        included_by: "user_choice"
+
       - id: "product-brief"
-        recommended: true
+        optional: true
         agent: "analyst"
         command: "product-brief"
+        included_by: "user_choice"
+        note: "Optional for brownfield, less common than greenfield"
 
-  - phase: 2
+  - phase: 1
     name: "Planning"
     required: true
     workflows:
@@ -45,46 +51,42 @@ phases:
         required: true
         agent: "pm"
         command: "prd"
-        output: "Requirements with integration points"
+        output: "PRD focused on new features/changes"
+        note: "Must consider existing system constraints"
+
       - id: "validate-prd"
         optional: true
         agent: "pm"
         command: "validate-prd"
+
       - id: "create-design"
         conditional: "if_has_ui"
         agent: "ux-designer"
         command: "create-design"
-        note: "Must align with existing UI patterns"
 
-  - phase: 3
+  - phase: 2
     name: "Solutioning"
     required: true
     workflows:
-      - id: "architecture-review"
-        required: true
-        agent: "architect"
-        command: "architecture-review"
-        note: "Review existing architecture first"
-      - id: "integration-planning"
-        required: true
-        agent: "architect"
-        command: "integration-planning"
-        output: "Integration strategy document"
       - id: "create-architecture"
-        required: true
+        recommended: true
         agent: "architect"
         command: "create-architecture"
-        note: "Extension of existing architecture"
+        output: "Integration architecture - solution design for THIS project"
+        note: "HIGHLY RECOMMENDED: Distills massive brownfield context into focused solution design. Prevents agent confusion."
+
       - id: "validate-architecture"
         optional: true
         agent: "architect"
         command: "validate-architecture"
+
       - id: "solutioning-gate-check"
         required: true
         agent: "architect"
         command: "solutioning-gate-check"
+        note: "Validates PRD + UX + Architecture (if created) cohesion"
 
-  - phase: 4
+  - phase: 3
     name: "Implementation"
     required: true
     workflows:
@@ -92,4 +94,4 @@ phases:
         required: true
         agent: "sm"
         command: "sprint-planning"
-        note: "Creates sprint plan with all stories - subsequent work tracked in sprint plan output, not workflow-status"
+        note: "Creates sprint plan with stories"

package/{src/modules/bmm/workflows/workflow-status/paths/greenfield-level-2.yaml → bmad/bmm/workflows/workflow-status/paths/method-greenfield.yaml}

@@ -1,31 +1,38 @@
-# Greenfield Level 2 - Medium Project
-# Multiple epics with 10+ stories total
+# BMad Method - Greenfield
+# Full product + architecture planning for greenfield projects (10-50+ stories typically)
 
-project_type: "software"
-level: 2
+method_name: "BMad Method"
+track: "method"
 field_type: "greenfield"
-description: "Medium project - multiple epics, 10+ stories"
+description: "Complete product and system design methodology for greenfield projects"
 
 phases:
-  - phase: 1
-    name: "Analysis"
+  - phase: 0
+    name: "Discovery (Optional)"
     optional: true
+    note: "User-selected during workflow-init"
     workflows:
       - id: "brainstorm-project"
         optional: true
         agent: "analyst"
         command: "brainstorm-project"
+        included_by: "user_choice"
+
       - id: "research"
         optional: true
         agent: "analyst"
         command: "research"
-        note: "Can have multiple research docs"
+        included_by: "user_choice"
+        note: "Can have multiple research workflows"
+
       - id: "product-brief"
-        recommended: true
+        optional: true
         agent: "analyst"
         command: "product-brief"
+        included_by: "user_choice"
+        note: "Recommended for greenfield Method projects"
 
-  - phase: 2
+  - phase: 1
     name: "Planning"
     required: true
     workflows:
@@ -33,22 +40,21 @@ phases:
         required: true
         agent: "pm"
         command: "prd"
-        output: "Creates PRD with epics.md and story list"
+        output: "Product Requirements Document with epics and stories"
+
       - id: "validate-prd"
         optional: true
         agent: "pm"
         command: "validate-prd"
+        note: "Quality check for PRD completeness"
+
       - id: "create-design"
         conditional: "if_has_ui"
         agent: "ux-designer"
         command: "create-design"
-      - id: "tech-spec"
-        optional: true
-        agent: "pm"
-        command: "tech-spec"
-        note: "Lightweight Technical Specification planning"
+        note: "Determined after PRD - user/agent decides if needed"
 
-  - phase: 3
+  - phase: 2
     name: "Solutioning"
     required: true
     workflows:
@@ -56,18 +62,22 @@ phases:
         required: true
         agent: "architect"
         command: "create-architecture"
-        output: "System-wide architecture document"
+        output: "System architecture document"
+        note: "Complete system design for greenfield projects"
+
       - id: "validate-architecture"
         optional: true
         agent: "architect"
         command: "validate-architecture"
+        note: "Quality check for architecture completeness"
+
       - id: "solutioning-gate-check"
         required: true
         agent: "architect"
         command: "solutioning-gate-check"
-        note: "Validate PRD + UX + architecture cohesion before implementation"
+        note: "Validates PRD + UX + Architecture cohesion before implementation"
 
-  - phase: 4
+  - phase: 3
     name: "Implementation"
     required: true
     workflows:
@@ -75,4 +85,4 @@ phases:
         required: true
         agent: "sm"
         command: "sprint-planning"
-        note: "Creates sprint plan with all stories - subsequent work tracked in sprint plan output, not workflow-status"
+        note: "Creates sprint plan - subsequent work tracked there"

package/{src/modules/bmm/workflows/workflow-status/paths/brownfield-level-1.yaml → bmad/bmm/workflows/workflow-status/paths/quick-flow-brownfield.yaml}

@@ -1,38 +1,42 @@
-# Brownfield Level 1 - Small Feature in Existing Codebase
-# 1-10 stories adding to existing system
+# BMad Quick Flow - Brownfield
+# Fast implementation path for existing codebases (1-15 stories typically)
 
-project_type: "software"
-level: 1
+method_name: "BMad Quick Flow"
+track: "quick-flow"
 field_type: "brownfield"
-description: "Small feature addition to existing codebase"
+description: "Fast tech-spec based implementation for brownfield projects"
 
 phases:
   - prerequisite: true
     name: "Documentation"
     conditional: "if_undocumented"
-    note: "NOT a phase - prerequisite for brownfield without docs OR post-completion cleanup"
+    note: "NOT a phase - prerequisite for brownfield without docs"
     workflows:
       - id: "document-project"
         required: true
         agent: "analyst"
         command: "document-project"
         output: "Comprehensive project documentation"
-        purpose: "Understand existing codebase before planning OR create superior final docs after Phase 4"
+        purpose: "Understand existing codebase before planning"
 
-  - phase: 1
-    name: "Analysis"
+  - phase: 0
+    name: "Discovery (Optional)"
     optional: true
+    note: "User-selected during workflow-init"
     workflows:
       - id: "brainstorm-project"
         optional: true
         agent: "analyst"
         command: "brainstorm-project"
+        included_by: "user_choice"
+
       - id: "research"
         optional: true
         agent: "analyst"
         command: "research"
+        included_by: "user_choice"
 
-  - phase: 2
+  - phase: 1
     name: "Planning"
     required: true
     workflows:
@@ -40,14 +44,10 @@ phases:
         required: true
         agent: "pm"
         command: "tech-spec"
-        output: "Creates story files for feature"
-        note: "Must integrate with existing architecture"
-
-  - phase: 3
-    name: "Solutioning"
-    skip: true
+        output: "Technical Specification with stories (auto-detects epic if 2+ stories)"
+        note: "Integrates with existing codebase patterns from document-project"
 
-  - phase: 4
+  - phase: 2
     name: "Implementation"
     required: true
     workflows:
@@ -55,4 +55,4 @@ phases:
         required: true
         agent: "sm"
         command: "sprint-planning"
-        note: "Creates sprint plan with all stories - subsequent work tracked in sprint plan output, not workflow-status"
+        note: "Creates sprint plan with all stories"

package/{src/modules/bmm/workflows/workflow-status/paths/greenfield-level-1.yaml → bmad/bmm/workflows/workflow-status/paths/quick-flow-greenfield.yaml}

@@ -1,30 +1,31 @@
-# Greenfield Level 1 - Small Feature
-# Coherent feature with 2-3 stories in a single epic
+# BMad Quick Flow - Greenfield
+# Fast implementation path with tech-spec planning (1-15 stories typically)
 
-project_type: "software"
-level: 1
+method_name: "BMad Quick Flow"
+track: "quick-flow"
 field_type: "greenfield"
-description: "Small coherent feature - 2-3 stories, single epic"
+description: "Fast tech-spec based implementation for greenfield projects"
 
 phases:
-  - phase: 1
-    name: "Analysis"
+  - phase: 0
+    name: "Discovery (Optional)"
     optional: true
+    note: "User-selected during workflow-init"
     workflows:
       - id: "brainstorm-project"
         optional: true
         agent: "analyst"
         command: "brainstorm-project"
+        included_by: "user_choice"
+
       - id: "research"
         optional: true
         agent: "analyst"
         command: "research"
-      - id: "product-brief"
-        optional: true
-        agent: "analyst"
-        command: "product-brief"
+        included_by: "user_choice"
+        note: "Can have multiple research workflows"
 
-  - phase: 2
+  - phase: 1
     name: "Planning"
     required: true
     workflows:
@@ -32,13 +33,10 @@ phases:
         required: true
         agent: "pm"
         command: "tech-spec"
-        output: "Creates Technical Specification with an epic and 2-3 story files"
+        output: "Technical Specification with stories (auto-detects epic if 2+ stories)"
+        note: "Quick Spec Flow - implementation-focused planning"
 
-  - phase: 3
-    name: "Solutioning"
-    skip: true
-
-  - phase: 4
+  - phase: 2
     name: "Implementation"
     required: true
     workflows:

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

@@ -0,0 +1,59 @@
+# BMM Project Scale Levels - Source of Truth
+# Reference: /bmad/bmm/README.md lines 77-85
+
+levels:
+  0:
+    name: "Level 0"
+    title: "Single Atomic Change"
+    stories: "1 story"
+    description: "Bug fix, tiny feature, one small change"
+    documentation: "Minimal - tech spec only"
+    architecture: false
+
+  1:
+    name: "Level 1"
+    title: "Small Feature"
+    stories: "1-10 stories"
+    description: "Small coherent feature, minimal documentation"
+    documentation: "Tech spec"
+    architecture: false
+
+  2:
+    name: "Level 2"
+    title: "Medium Project"
+    stories: "5-15 stories"
+    description: "Multiple features, focused PRD"
+    documentation: "PRD + optional tech spec"
+    architecture: false
+
+  3:
+    name: "Level 3"
+    title: "Complex System"
+    stories: "12-40 stories"
+    description: "Subsystems, integrations, full architecture"
+    documentation: "PRD + architecture + JIT tech specs"
+    architecture: true
+
+  4:
+    name: "Level 4"
+    title: "Enterprise Scale"
+    stories: "40+ stories"
+    description: "Multiple products, enterprise architecture"
+    documentation: "PRD + architecture + JIT tech specs"
+    architecture: true
+
+# Quick detection hints for workflow-init
+detection_hints:
+  keywords:
+    level_0: ["fix", "bug", "typo", "small change", "quick update", "patch"]
+    level_1: ["simple", "basic", "small feature", "add", "minor"]
+    level_2: ["dashboard", "several features", "admin panel", "medium"]
+    level_3: ["platform", "integration", "complex", "system", "architecture"]
+    level_4: ["enterprise", "multi-tenant", "multiple products", "ecosystem", "scale"]
+
+  story_counts:
+    level_0: [1, 1]
+    level_1: [1, 10]
+    level_2: [5, 15]
+    level_3: [12, 40]
+    level_4: [40, 999]

package/bmad/bmm/workflows/workflow-status/sample-level-3-workflow.yaml

@@ -0,0 +1,49 @@
+# Workflow Status Template
+# This tracks progress through phases 1-3 of the BMM methodology
+# Phase 4 (Implementation) is tracked separately in sprint-status.yaml
+
+# generated: 2025-10-29
+# project: Enterprise Customer Portal
+# project_type: software
+# project_level: 3
+# field_type: greenfield
+# workflow_path: greenfield-level-3.yaml
+
+# STATUS DEFINITIONS:
+# ==================
+# Initial Status (before completion):
+#   - required: Must be completed to progress
+#   - optional: Can be completed but not required
+#   - recommended: Strongly suggested but not required
+#   - conditional: Required only if certain conditions met (e.g., if_has_ui)
+#
+# Completion Status:
+#   - {file-path}: File created/found (e.g., "docs/product-brief.md")
+#   - skipped: Optional/conditional workflow that was skipped
+
+generated: 2025-10-29
+project: Enterprise Customer Portal
+project_type: software
+project_level: 3
+field_type: greenfield
+workflow_path: greenfield-level-3.yaml
+
+workflow_status:
+  # Phase 1: Analysis
+  brainstorm-project: docs/brainstorm-session-2025-10-15.md
+  research: docs/research-api-patterns.md
+  product-brief: docs/product-brief.md
+
+  # Phase 2: Planning
+  prd: docs/prd.md
+  validate-prd: skipped
+  create-design: docs/ux-design.md
+
+  # Phase 3: Solutioning
+  create-architecture: required
+  validate-architecture: optional
+  solutioning-gate-check: recommended
+
+  # Phase 4: Implementation
+  sprint-planning: required
+  # Note: Subsequent implementation workflows tracked in sprint-status.yaml

package/bmad/bmm/workflows/workflow-status/workflow-status-template.yaml

@@ -0,0 +1,31 @@
+# Workflow Status Template
+# This tracks progress through BMM methodology phases
+# Phase 3/4 (Implementation) is tracked separately in sprint-status.yaml
+
+# generated: {{generated}}
+# project: {{project_name}}
+# project_type: {{project_type}}
+# selected_track: {{selected_track}}
+# field_type: {{field_type}}
+# workflow_path: {{workflow_path_file}}
+
+# STATUS DEFINITIONS:
+# ==================
+# Initial Status (before completion):
+#   - required: Must be completed to progress
+#   - optional: Can be completed but not required
+#   - recommended: Strongly suggested but not required
+#   - conditional: Required only if certain conditions met (e.g., if_has_ui)
+#
+# Completion Status:
+#   - {file-path}: File created/found (e.g., "docs/product-brief.md")
+#   - skipped: Optional/conditional workflow that was skipped
+
+generated: "{{generated}}"
+project: "{{project_name}}"
+project_type: "{{project_type}}"
+selected_track: "{{selected_track}}"
+field_type: "{{field_type}}"
+workflow_path: "{{workflow_path_file}}"
+
+workflow_status: "{{workflow_items}}"

package/bmad/bmm/workflows/workflow-status/workflow.yaml

@@ -0,0 +1,28 @@
+# Workflow Status - Master Router and Status Tracker
+name: workflow-status
+description: 'Lightweight status checker - answers "what should I do now?" for any agent. Reads YAML status file for workflow tracking. Use workflow-init for new 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
+
+# Workflow components
+installed_path: "{project-root}/bmad/bmm/workflows/workflow-status"
+instructions: "{installed_path}/instructions.md"
+
+# Template for status file creation (used by workflow-init)
+template: "{installed_path}/workflow-status-template.yaml"
+
+# Path definitions for project types
+path_files: "{installed_path}/paths/"
+
+# Output configuration - reads existing status
+default_output_file: "{output_folder}/bmm-workflow-status.yaml"
+
+standalone: true