bmad-method 6.0.0-alpha.0 → 6.0.0-alpha.1

package/src/modules/bmm/workflows/1-analysis/brainstorm-game/instructions.md

@@ -1,13 +1,42 @@
-# Brainstorm Game - Workflow Instructions
-
-```xml
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
+<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
+<critical>Communicate all responses in {communication_language}</critical>
 <critical>This is a meta-workflow that orchestrates the CIS brainstorming workflow with game-specific context and additional game design techniques</critical>
 
 <workflow>
 
-  <step n="1" goal="Load game brainstorming context and techniques">
+  <step n="1" goal="Validate workflow readiness">
+    <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
+      <param>mode: validate</param>
+      <param>calling_workflow: brainstorm-game</param>
+    </invoke-workflow>
+
+    <check if="status_exists == false">
+      <output>{{suggestion}}</output>
+      <output>Note: Game brainstorming is optional. Continuing without progress tracking.</output>
+      <action>Set standalone_mode = true</action>
+    </check>
+
+    <check if="status_exists == true">
+      <action>Store {{status_file_path}} for later updates</action>
+
+      <check if="project_type != 'game'">
+        <output>Note: This is a {{project_type}} project. Game brainstorming is designed for game projects.</output>
+        <ask>Continue with game brainstorming anyway? (y/n)</ask>
+        <check if="n">
+          <action>Exit workflow</action>
+        </check>
+      </check>
+
+      <check if="warning != ''">
+        <output>{{warning}}</output>
+        <output>Note: Game brainstorming can be valuable at any project stage.</output>
+      </check>
+    </check>
+
+  </step>
+
+  <step n="2" goal="Load game brainstorming context and techniques">
     <action>Read the game context document from: {game_context}</action>
     <action>This context provides game-specific guidance including:
       - Focus areas for game ideation (mechanics, narrative, experience, etc.)
@@ -25,9 +54,9 @@
     </action>
   </step>
 
-  <step n="2" goal="Invoke CIS brainstorming with game context">
+  <step n="3" goal="Invoke CIS brainstorming with game context">
     <action>Execute the CIS brainstorming workflow with game context and additional techniques</action>
-    <invoke-workflow path="{cis_brainstorming}" data="{game_context}" techniques="{game_brain_methods}">
+    <invoke-workflow path="{core_brainstorming}" data="{game_context}" techniques="{game_brain_methods}">
       The CIS brainstorming workflow will:
       - Merge game-specific techniques with standard techniques
       - Present interactive brainstorming techniques menu
@@ -37,11 +66,44 @@
     </invoke-workflow>
   </step>
 
-  <step n="3" goal="Completion">
-    <action>Confirm brainstorming session completed successfully</action>
-    <action>Brainstorming results saved by CIS workflow</action>
-    <action>Report workflow completion</action>
+  <step n="4" goal="Update status and complete">
+    <check if="standalone_mode != true">
+      <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
+        <param>mode: update</param>
+        <param>action: complete_workflow</param>
+        <param>workflow_name: brainstorm-game</param>
+      </invoke-workflow>
+
+      <check if="success == true">
+        <output>Status updated! Next: {{next_workflow}}</output>
+      </check>
+    </check>
+
+    <output>**✅ Game Brainstorming Session Complete, {user_name}!**
+
+**Session Results:**
+
+- Game brainstorming results saved to: {output_folder}/bmm-brainstorming-session-{{date}}.md
+
+{{#if standalone_mode != true}}
+**Status Updated:**
+
+- Progress tracking updated
+
+**Next Steps:**
+
+- **Next required:** {{next_workflow}} ({{next_agent}} agent)
+- **Optional:** You can run other analysis workflows (research, game-brief) before proceeding
+
+Check status anytime with: `workflow-status`
+{{else}}
+**Next Steps:**
+Since no workflow is in progress:
+
+- Refer to the BMM workflow guide if unsure what to do next
+- Or run `workflow-init` to create a workflow path and get guided next steps
+  {{/if}}
+  </output>
   </step>
 
 </workflow>
-```

package/src/modules/bmm/workflows/1-analysis/brainstorm-game/workflow.yaml

@@ -3,10 +3,13 @@ name: "brainstorm-game"
 description: "Facilitate game brainstorming sessions by orchestrating the CIS brainstorming workflow with game-specific context, guidance, and additional game design techniques."
 author: "BMad"
 
-# Critical variables load from config_source
+# 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
@@ -18,5 +21,21 @@ instructions: "{installed_path}/instructions.md"
 game_context: "{installed_path}/game-context.md"
 game_brain_methods: "{installed_path}/game-brain-methods.csv"
 
-# CIS brainstorming workflow to invoke
-cis_brainstorming: "{project-root}/bmad/cis/workflows/brainstorming/workflow.yaml"
+# CORE brainstorming workflow to invoke
+core_brainstorming: "{project-root}/bmad/core/workflows/brainstorming/workflow.yaml"
+
+standalone: true
+
+web_bundle:
+  name: "brainstorm-game"
+  description: "Facilitate game brainstorming sessions by orchestrating the CIS brainstorming workflow with game-specific context, guidance, and additional game design techniques."
+  author: "BMad"
+  instructions: "bmad/bmm/workflows/1-analysis/brainstorm-game/instructions.md"
+  template: false
+  web_bundle_files:
+    - "bmad/bmm/workflows/1-analysis/brainstorm-game/instructions.md"
+    - "bmad/bmm/workflows/1-analysis/brainstorm-game/game-context.md"
+    - "bmad/bmm/workflows/1-analysis/brainstorm-game/game-brain-methods.csv"
+    - "bmad/core/workflows/brainstorming/workflow.yaml"
+  existing_workflows:
+    - core_brainstorming: "bmad/core/workflows/brainstorming/workflow.yaml"

package/src/modules/bmm/workflows/1-analysis/brainstorm-project/README.md

@@ -0,0 +1,29 @@
+---
+last-redoc-date: 2025-10-01
+---
+
+# Project Brainstorming Workflow
+
+This workflow facilitates structured ideation for non-game software projects through systematic exploration of problem spaces, architectures, and implementation strategies. Unlike traditional requirement gathering, it employs creative techniques to uncover non-obvious approaches and identify innovative solutions that address core business needs while considering technical constraints and organizational capabilities.
+
+The workflow operates through a project-specific context framework that captures business objectives, technical environment, stakeholder needs, and organizational constraints. It generates multiple solution vectors through parallel ideation tracks: architectural approaches, user experience paradigms, integration patterns, and value delivery mechanisms. Each track produces concrete proposals that are evaluated against feasibility, impact, and alignment with strategic objectives.
+
+Critical differentiators include its focus on solution innovation rather than requirement enumeration, emphasis on technical-business alignment from inception, and structured approach to surfacing hidden assumptions. The workflow produces actionable outputs that directly feed into Product Brief development, ensuring that creative exploration translates into concrete planning artifacts.
+
+## Usage
+
+```bash
+bmad bmm 1-analysis brainstorm-project
+```
+
+## Inputs
+
+- **Project Context Document**: Business objectives, technical environment, stakeholder landscape, organizational constraints, success criteria, and known pain points
+- **Problem Statement** (optional): Core business challenge or opportunity driving the project
+
+## Outputs
+
+- **Architecture Proposals**: Multiple technical approaches with trade-off analysis and feasibility assessments
+- **Value Delivery Framework**: Prioritized feature concepts aligned with business objectives and user needs
+- **Risk and Opportunity Analysis**: Identified technical dependencies, integration challenges, and innovation opportunities
+- **Strategic Recommendation**: Synthesized direction with rationale and implementation considerations

package/src/modules/bmm/workflows/1-analysis/brainstorm-project/instructions.md

@@ -1,13 +1,36 @@
 # Brainstorm Project - Workflow Instructions
 
 ```xml
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
+<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
+<critical>Communicate all responses in {communication_language}</critical>
 <critical>This is a meta-workflow that orchestrates the CIS brainstorming workflow with project-specific context</critical>
 
 <workflow>
 
-  <step n="1" goal="Load project brainstorming context">
+  <step n="1" goal="Validate workflow readiness">
+    <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
+      <param>mode: validate</param>
+      <param>calling_workflow: brainstorm-project</param>
+    </invoke-workflow>
+
+    <check if="status_exists == false">
+      <output>{{suggestion}}</output>
+      <output>Note: Brainstorming is optional. Continuing without progress tracking.</output>
+      <action>Set standalone_mode = true</action>
+    </check>
+
+    <check if="status_exists == true">
+      <action>Store {{status_file_path}} for later updates</action>
+
+      <check if="warning != ''">
+        <output>{{warning}}</output>
+        <output>Note: Brainstorming can be valuable at any project stage.</output>
+      </check>
+    </check>
+  </step>
+
+  <step n="2" goal="Load project brainstorming context">
     <action>Read the project context document from: {project_context}</action>
     <action>This context provides project-specific guidance including:
       - Focus areas for project ideation
@@ -17,9 +40,9 @@
     </action>
   </step>
 
-  <step n="2" goal="Invoke CIS brainstorming with project context">
+  <step n="3" goal="Invoke core brainstorming with project context">
     <action>Execute the CIS brainstorming workflow with project context</action>
-    <invoke-workflow path="{cis_brainstorming}" data="{project_context}">
+    <invoke-workflow path="{core_brainstorming}" data="{project_context}">
       The CIS brainstorming workflow will:
       - Present interactive brainstorming techniques menu
       - Guide the user through selected ideation methods
@@ -28,10 +51,40 @@
     </invoke-workflow>
   </step>
 
-  <step n="3" goal="Completion">
-    <action>Confirm brainstorming session completed successfully</action>
-    <action>Brainstorming results saved by CIS workflow</action>
-    <action>Report workflow completion</action>
+  <step n="4" goal="Update status and complete">
+    <check if="standalone_mode != true">
+      <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
+        <param>mode: update</param>
+        <param>action: complete_workflow</param>
+        <param>workflow_name: brainstorm-project</param>
+      </invoke-workflow>
+
+      <check if="success == true">
+        <output>Status updated! Next: {{next_workflow}}</output>
+      </check>
+    </check>
+
+    <output>**✅ Brainstorming Session Complete, {user_name}!**
+
+**Session Results:**
+- Brainstorming results saved to: {output_folder}/bmm-brainstorming-session-{{date}}.md
+
+{{#if standalone_mode != true}}
+**Status Updated:**
+- Progress tracking updated
+
+**Next Steps:**
+- **Next required:** {{next_workflow}} ({{next_agent}} agent)
+- **Optional:** You can run other analysis workflows (research, product-brief) before proceeding
+
+Check status anytime with: `workflow-status`
+{{else}}
+**Next Steps:**
+Since no workflow is in progress:
+- Refer to the BMM workflow guide if unsure what to do next
+- Or run `workflow-init` to create a workflow path and get guided next steps
+{{/if}}
+    </output>
   </step>
 
 </workflow>

package/src/modules/bmm/workflows/1-analysis/brainstorm-project/project-context.md

@@ -6,13 +6,13 @@ This context guide provides project-specific considerations for brainstorming se
 
 When brainstorming for projects, consider exploring:
 
-- **User Problems & Pain Points** - What challenges do users face?
-- **Feature Ideas & Capabilities** - What could the product do?
+- **User Problems and Pain Points** - What challenges do users face?
+- **Feature Ideas and Capabilities** - What could the product do?
 - **Technical Approaches** - How might we build it?
 - **User Experience** - How will users interact with it?
-- **Business Model & Value** - How does it create value?
+- **Business Model and Value** - How does it create value?
 - **Market Differentiation** - What makes it unique?
-- **Technical Risks & Challenges** - What could go wrong?
+- **Technical Risks and Challenges** - What could go wrong?
 - **Success Metrics** - How will we measure success?
 
 ## Integration with Project Workflow

package/src/modules/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml

@@ -3,10 +3,13 @@ name: "brainstorm-project"
 description: "Facilitate project brainstorming sessions by orchestrating the CIS brainstorming workflow with project-specific context and guidance."
 author: "BMad"
 
-# Critical variables load from config_source
+# 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
@@ -17,5 +20,20 @@ instructions: "{installed_path}/instructions.md"
 # Context document for project brainstorming
 project_context: "{installed_path}/project-context.md"
 
-# CIS brainstorming workflow to invoke
-cis_brainstorming: "{project-root}/bmad/cis/workflows/brainstorming/workflow.yaml"
+# CORE brainstorming workflow to invoke
+core_brainstorming: "{project-root}/bmad/core/workflows/brainstorming/workflow.yaml"
+
+standalone: true
+
+web_bundle:
+  name: "brainstorm-project"
+  description: "Facilitate project brainstorming sessions by orchestrating the CIS brainstorming workflow with project-specific context and guidance."
+  author: "BMad"
+  instructions: "bmad/bmm/workflows/1-analysis/brainstorm-project/instructions.md"
+  template: false
+  web_bundle_files:
+    - "bmad/bmm/workflows/1-analysis/brainstorm-project/instructions.md"
+    - "bmad/bmm/workflows/1-analysis/brainstorm-project/project-context.md"
+    - "bmad/core/workflows/brainstorming/workflow.yaml"
+  existing_workflows:
+    - core_brainstorming: "bmad/core/workflows/brainstorming/workflow.yaml"

package/src/modules/bmm/workflows/1-analysis/game-brief/README.md

@@ -48,7 +48,7 @@ Work through each section collaboratively:
 4. Scope and Constraints (platforms, timeline, budget, team)
 5. Reference Framework (inspiration, competitors, differentiators)
 6. Content Framework (world, narrative, volume)
-7. Art & Audio Direction (visual and audio style)
+7. Art and Audio Direction (visual and audio style)
 8. Risk Assessment (risks, challenges, mitigation)
 9. Success Criteria (MVP, metrics, launch goals)
 10. Next Steps (immediate actions, research, questions)
@@ -107,9 +107,9 @@ Output is designed to feed directly into:
 ```
 1-analysis/game-brief     (You are here)
     ↓
-2-plan/gdd               (Game Design Document)
+2-plan-workflows/gdd               (Game Design Document)
     ↓
-2-plan/narrative         (Optional: Story-heavy games)
+2-plan-workflows/narrative         (Optional: Story-heavy games)
     ↓
 3-solutioning            (Technical architecture, engine selection)
     ↓
@@ -216,6 +216,6 @@ A: Involve your team! Collaborative briefs catch blind spots and build shared vi
 ## Related Workflows
 
 - **Product Brief** (`1-analysis/product-brief`): For software products, not games
-- **GDD** (`2-plan/gdd`): Next step after game brief
-- **Narrative Design** (`2-plan/narrative`): For story-heavy games after GDD
+- **GDD** (`2-plan-workflows/gdd`): Next step after game brief
+- **Narrative Design** (`2-plan-workflows/narrative`): For story-heavy games after GDD
 - **Solutioning** (`3-solutioning`): Technical architecture after planning

package/src/modules/bmm/workflows/1-analysis/game-brief/checklist.md

@@ -45,13 +45,13 @@ Use this checklist to ensure your game brief is complete and ready for GDD creat
 
 ## Content Framework ✓
 
-- [ ] **World & Setting** is defined
+- [ ] **World and Setting** is defined
 - [ ] **Narrative Approach** matches game type
 - [ ] **Content Volume** is estimated (rough order of magnitude)
 - [ ] Playtime expectations are set
 - [ ] Replayability approach is clear
 
-## Art & Audio Direction ✓
+## Art and Audio Direction ✓
 
 - [ ] **Visual Style** is described with references
 - [ ] 2D vs. 3D is decided