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

package/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-04-complete.md

@@ -0,0 +1,275 @@
+---
+name: 'step-04-complete'
+description: 'Complete the brainstorming session with summary and next steps'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/brainstorm-game'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-04-complete.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/brainstorming-session-{date}.md'
+
+# Handoff References
+gameBriefWorkflow: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief/workflow.yaml'
+gddWorkflow: '{project-root}/_bmad/bmgd/workflows/2-design/gdd/workflow.yaml'
+---
+
+# Step 4: Complete Session
+
+**Progress: Step 4 of 4** - Brainstorming Complete!
+
+## STEP GOAL:
+
+Finalize the brainstorming session, generate actionable next steps, update workflow status, and provide clear handoff guidance.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- NEVER generate content without user input
+- CRITICAL: Read the complete step file before taking any action
+- YOU ARE A FACILITATOR, not a content generator
+- NEVER mention time estimates
+
+### Role Reinforcement:
+
+- You are a creative game design facilitator
+- Help user identify most promising concepts
+- Provide clear path forward
+
+### Step-Specific Rules:
+
+- Highlight top 1-3 concepts for further development
+- Generate actionable next steps
+- Update workflow status if tracking enabled
+
+## EXECUTION PROTOCOLS:
+
+- Show your analysis before taking any action
+- Generate final summary
+- Update frontmatter `stepsCompleted: [1, 2, 3, 4]`
+- Present completion summary and next steps
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Generate Session Summary
+
+**Create executive summary:**
+
+Based on all ideation, synthesize a summary:
+
+```markdown
+## Session Summary
+
+### Most Promising Concepts
+
+**Top Pick: {{top_concept}}**
+{{why_most_promising}}
+
+**Runner-up: {{second_concept}}**
+{{why_promising}}
+
+**Honorable Mention: {{third_concept}}**
+{{why_worth_exploring}}
+
+### Key Insights
+
+{{insights_from_session}}
+
+### Recommended Next Steps
+
+1. {{next_step_1}}
+2. {{next_step_2}}
+3. {{next_step_3}}
+```
+
+### 2. Present Final Summary
+
+"**Brainstorming Session Complete!**
+
+{{user_name}}, here's what we accomplished:
+
+**Session Stats:**
+
+- Ideas generated: {{idea_count}}
+- Concepts developed: {{concept_count}}
+- Techniques used: {{technique_list}}
+
+**Most Promising Concept:**
+**{{top_concept_name}}** - {{brief_description}}
+
+**Why This Stands Out:**
+{{reasons}}
+
+**Document saved to:** `{outputFile}`
+
+Would you like to review or adjust the summary before we finalize?"
+
+### 3. Handle Review Requests
+
+**If user wants to review:**
+
+"Which would you like to review?
+
+1. Most Promising Concepts
+2. All Ideas Generated
+3. Session Insights
+4. Full Document
+
+Or type 'all' to see the complete document."
+
+### 4. Update Workflow Status
+
+**If not in standalone mode:**
+
+Load `{output_folder}/bmm-workflow-status.yaml` and:
+
+- Update `brainstorm-game` status to the output file path
+- Preserve all comments and structure
+- Determine next workflow in sequence
+
+### 5. Generate Completion Section
+
+Prepare the final content:
+
+```markdown
+---
+
+## Session Complete
+
+**Date:** {{date}}
+**Duration:** Brainstorming session
+**Participant:** {{user_name}}
+
+### Output
+
+This brainstorming session generated:
+
+- {{idea_count}} raw ideas
+- {{concept_count}} developed concepts
+- {{theme_count}} emerging themes
+
+### Document Status
+
+Status: Complete
+Steps Completed: [1, 2, 3, 4]
+```
+
+### 6. Present Next Steps Menu
+
+"**Recommended Next Steps:**
+
+1. **Create Game Brief** - Transform your top concept into a formal game brief
+   - Workflow: `create-brief`
+   - Input: This brainstorming session
+   - Output: Structured game vision document
+
+2. **Research Market** - Validate your concept against the market
+   - Look at similar games
+   - Identify your unique angle
+   - Understand competition
+
+3. **Prototype Core Mechanic** - Test your core idea immediately
+   - Quick paper prototype
+   - Simple digital prototype
+   - Get hands-on feel for the concept
+
+4. **Another Brainstorm Session** - Explore more concepts
+   - Try different techniques
+   - Explore alternative directions
+
+**Which would you like to do next?**
+
+1. Start Game Brief workflow
+2. Review the brainstorming results
+3. Run another brainstorm session
+4. Exit workflow"
+
+### 7. Handle User Selection
+
+Based on user choice:
+
+**If 1 (Game Brief):**
+
+- Confirm document is saved
+- Provide handoff guidance for game brief workflow
+- Note that brainstorming results will be input
+
+**If 2 (Review):**
+
+- Present document summary
+- Return to next steps menu
+
+**If 3 (Another Session):**
+
+- Note that a new session file will be created
+- Route back to step 1 for fresh start
+
+**If 4 (Exit):**
+
+- Confirm document is saved and complete
+- Exit workflow gracefully
+
+### 8. Final Completion Message
+
+"**Brainstorming Session Complete!**
+
+**Deliverables:**
+
+- Brainstorming results saved to: `{outputFile}`
+- {{idea_count}} ideas captured
+- Top concepts identified and summarized
+
+{{#if standalone_mode != true}}
+**Status Updated:**
+
+- Progress tracking updated: brainstorm-game marked complete
+- Next recommended: Game Brief workflow
+  {{/if}}
+
+**Your Ideas Are Ready For:**
+
+- Game Brief creation
+- Concept validation
+- Prototyping
+- Team discussion
+
+Great brainstorming session, {{user_name}}! Your creativity is the foundation for an exciting game."
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- Top concepts identified and highlighted
+- Session summary generated
+- Actionable next steps provided
+- Workflow status updated (if tracking)
+- Document saved and complete
+- Clear handoff guidance provided
+- Frontmatter shows all 4 steps completed
+
+### SYSTEM FAILURE:
+
+- No clear top concepts identified
+- Missing session summary
+- No actionable next steps
+- Status not updated when tracking enabled
+- User left without guidance
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+
+---
+
+## Brainstorm Game Workflow Complete
+
+The Brainstorm Game workflow facilitates creative game ideation through 4 collaborative steps:
+
+1. **Initialize** - Set brainstorming mindset and prepare session
+2. **Context** - Load game-specific techniques and select approach
+3. **Ideation** - Execute brainstorming with user driving ideas
+4. **Complete** - Summarize results and provide next steps
+
+This step-file architecture ensures consistent, creative brainstorming with user collaboration throughout.

package/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/workflow.md

@@ -0,0 +1,49 @@
+# Brainstorm Game Workflow
+
+**Facilitate game brainstorming sessions with game-specific context and techniques**
+
+## Overview
+
+This workflow orchestrates creative brainstorming for game ideas by combining the core CIS brainstorming workflow with game-specific context, guidance, and specialized game design techniques.
+
+## Workflow Structure
+
+The workflow uses a step-file architecture for modular, stateful execution:
+
+1. **Step 1: Initialize** - Validate workflow readiness and discover context
+2. **Step 2: Context** - Load game-specific brainstorming context and techniques
+3. **Step 3: Ideation** - Execute brainstorming with game techniques
+4. **Step 4: Complete** - Save results and update workflow status
+
+## State Tracking
+
+Progress is tracked in the brainstorming output document frontmatter:
+
+```yaml
+stepsCompleted: [1, 2, 3, ...] # Array of completed step numbers
+```
+
+## Starting the Workflow
+
+To begin, load and execute step-01-init.md:
+
+```
+{workflow_path}/steps/step-01-init.md
+```
+
+## Critical Rules
+
+- This is a meta-workflow that orchestrates CIS brainstorming
+- Use game-specific techniques from game-brain-methods.csv
+- Apply game-context.md guidance throughout
+- **NEVER** mention time estimates
+- **ALWAYS** wait for user input between steps
+
+## Agent Role
+
+You are a creative facilitator specializing in game ideation:
+
+- Draw out user's game concepts and ideas
+- Apply game-specific brainstorming techniques
+- Help users explore mechanics, themes, and experiences
+- Capture and organize ideas for later refinement

package/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml

@@ -1,10 +1,10 @@
 # Brainstorm Game Workflow Configuration
 name: "brainstorm-game"
-description: "Facilitate game brainstorming sessions by orchestrating the CIS brainstorming workflow with game-specific context, guidance, and additional game design techniques."
+description: "Facilitate game brainstorming sessions with game-specific context, guidance, and game design techniques."
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/.bmad/bmgd/config.yaml"
+config_source: "{project-root}/_bmad/bmgd/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,30 +12,51 @@ document_output_language: "{config_source}:document_output_language"
 game_dev_experience: "{config_source}:game_dev_experience"
 date: system-generated
 
-# Module path and component files
-installed_path: "{project-root}/.bmad/bmgd/workflows/1-preproduction/brainstorm-game"
+# Workflow components - Step-file architecture
+installed_path: "{project-root}/_bmad/bmgd/workflows/1-preproduction/brainstorm-game"
+instructions: "{installed_path}/workflow.md"
 template: false
-instructions: "{installed_path}/instructions.md"
 
 # Context and techniques for game brainstorming
 game_context: "{installed_path}/game-context.md"
 game_brain_methods: "{installed_path}/game-brain-methods.csv"
 
-# CORE brainstorming workflow to invoke
-core_brainstorming: "{project-root}/.bmad/core/workflows/brainstorming/workflow.yaml"
+# CORE brainstorming workflow reference (for technique merging)
+core_brainstorming: "{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml"
+
+# Output configuration
+default_output_file: "{output_folder}/brainstorming-session-{date}.md"
+
+# Workflow metadata
+version: "2.0.0"
+paradigm: "step-file-architecture"
+features:
+  - "Step-file architecture for modular execution"
+  - "Game-specific brainstorming techniques"
+  - "MDA Framework exploration"
+  - "Core loop brainstorming"
+  - "Player fantasy mining"
+  - "Genre mashup ideation"
+  - "State tracking via frontmatter"
 
 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."
+  description: "Facilitate game brainstorming sessions with game-specific context and techniques"
   author: "BMad"
-  instructions: ".bmad/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md"
+  instructions: "_bmad/bmgd/workflows/1-preproduction/brainstorm-game/workflow.md"
   template: false
   web_bundle_files:
-    - ".bmad/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md"
-    - ".bmad/bmgd/workflows/1-preproduction/brainstorm-game/game-context.md"
-    - ".bmad/bmgd/workflows/1-preproduction/brainstorm-game/game-brain-methods.csv"
-    - ".bmad/core/workflows/brainstorming/workflow.yaml"
+    # Main workflow file
+    - "_bmad/bmgd/workflows/1-preproduction/brainstorm-game/workflow.md"
+    # Step files
+    - "_bmad/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-01-init.md"
+    - "_bmad/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-02-context.md"
+    - "_bmad/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-03-ideation.md"
+    - "_bmad/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-04-complete.md"
+    # Context files
+    - "_bmad/bmgd/workflows/1-preproduction/brainstorm-game/game-context.md"
+    - "_bmad/bmgd/workflows/1-preproduction/brainstorm-game/game-brain-methods.csv"
   existing_workflows:
-    - core_brainstorming: ".bmad/core/workflows/brainstorming/workflow.yaml"
+    - core_brainstorming: "_bmad/core/workflows/brainstorming/workflow.yaml"

package/src/modules/bmgd/workflows/1-preproduction/game-brief/instructions.md

@@ -1,6 +1,6 @@
 # Game Brief - Interactive Workflow 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: {installed_path}/workflow.yaml</critical>
 <critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
 <critical>Generate all documents in {document_output_language}</critical>

package/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-01-init.md

@@ -0,0 +1,223 @@
+---
+name: 'step-01-init'
+description: 'Initialize the Game Brief workflow by detecting continuation state and setting up the document'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01-init.md'
+nextStepFile: '{workflow_path}/steps/step-02-vision.md'
+continueStepFile: '{workflow_path}/steps/step-01b-continue.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/game-brief.md'
+
+# Template References
+briefTemplate: '{workflow_path}/templates/game-brief-template.md'
+---
+
+# Step 1: Workflow Initialization
+
+**Progress: Step 1 of 8** - Next: Game Vision
+
+## STEP GOAL:
+
+Initialize the Game Brief workflow by detecting continuation state, discovering any input documents (brainstorming, research), and setting up the document structure.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- NEVER generate content without user input
+- CRITICAL: Read the complete step file before taking any action
+- CRITICAL: When loading next step with 'C', ensure entire file is read
+- YOU ARE A FACILITATOR, not a content generator
+- NEVER mention time estimates
+
+### Role Reinforcement:
+
+- You are a veteran game designer facilitator collaborating with a creative peer
+- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
+- We engage in collaborative dialogue, not command-response
+- You bring structured game design thinking and facilitation skills
+
+### Step-Specific Rules:
+
+- Focus only on initialization and setup - no content generation yet
+- FORBIDDEN to look ahead to future steps or assume knowledge from them
+- Approach: Systematic setup with clear reporting to user
+- Detect existing workflow state and handle continuation properly
+
+## EXECUTION PROTOCOLS:
+
+- Show your analysis of current state before taking any action
+- Initialize document structure and update frontmatter appropriately
+- Set up frontmatter `stepsCompleted: [1]` before loading next step
+- FORBIDDEN to load next step until user selects 'C' (Continue)
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Variables from workflow.md are available in memory
+- Focus: Workflow initialization and document setup only
+- Limits: Don't assume knowledge from other steps or create content yet
+- Dependencies: Configuration loaded from workflow.md initialization
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Check for Existing Workflow State
+
+First, check if the output document already exists:
+
+**Workflow State Detection:**
+
+- Look for file at `{outputFile}`
+- If exists, read the complete file including frontmatter
+- If not exists, this is a fresh workflow
+
+### 2. Handle Continuation (If Document Exists)
+
+If the document exists and has frontmatter with `stepsCompleted`:
+
+**Continuation Protocol:**
+
+- **STOP immediately** and load `{continueStepFile}`
+- Do not proceed with any initialization tasks
+- Let step-01b handle all continuation logic
+- This is an auto-proceed situation - no user choice needed
+
+### 3. Fresh Workflow Setup (If No Document)
+
+If no document exists or no `stepsCompleted` in frontmatter:
+
+#### A. Input Document Discovery
+
+Discover and load context documents using smart discovery.
+
+**IMPORTANT: Track document counts as you discover files.**
+
+Initialize counters:
+
+```
+brainstormingCount = 0
+researchCount = 0
+notesCount = 0
+```
+
+**Brainstorming Documents:**
+
+1. Check: `{output_folder}/*brainstorm*.md`
+2. Check: `{output_folder}/analysis/*brainstorm*.md`
+3. Load completely and extract key ideas
+4. **Update brainstormingCount with number of files found**
+
+**Research Documents:**
+
+1. Check: `{output_folder}/*research*.md`
+2. Check: `{output_folder}/analysis/*research*.md`
+3. Load useful research files completely
+4. **Update researchCount with number of files found**
+
+**Design Notes:**
+
+1. Check: `{output_folder}/*notes*.md` or `{output_folder}/*design*.md`
+2. Load any relevant design notes
+3. **Update notesCount with number of files found**
+
+**Loading Rules:**
+
+- Load ALL discovered files completely (no offset/limit)
+- Track all successfully loaded files in frontmatter `inputDocuments` array
+
+#### B. Create Initial Document
+
+**Document Setup:**
+
+- Copy the template from `{briefTemplate}` to `{outputFile}`
+- Initialize frontmatter with proper structure:
+
+```yaml
+---
+stepsCompleted: []
+inputDocuments: []
+documentCounts:
+  brainstorming: { { brainstormingCount } }
+  research: { { researchCount } }
+  notes: { { notesCount } }
+workflowType: 'game-brief'
+lastStep: 0
+project_name: '{{project_name}}'
+user_name: '{{user_name}}'
+date: '{{date}}'
+game_name: ''
+---
+```
+
+#### C. Present Initialization Results
+
+**Setup Report to User:**
+
+"Welcome {{user_name}}! I've set up your Game Brief workspace.
+
+**Document Setup:**
+
+- Created: `{outputFile}` from template
+- Initialized frontmatter with workflow state
+
+**Input Documents Discovered:**
+
+- Brainstorming: {{brainstormingCount}} files {if brainstormingCount > 0}loaded{else}(none found){/if}
+- Research: {{researchCount}} files {if researchCount > 0}loaded{else}(none found){/if}
+- Design notes: {{notesCount}} files {if notesCount > 0}loaded{else}(none found){/if}
+
+{if any_documents_found}
+I'll use these documents to give us a head start on your game brief.
+{else}
+We'll start fresh and build your game vision together through conversation.
+{/if}
+
+Do you have any other documents you'd like me to include, or shall we continue?"
+
+### 4. Present MENU OPTIONS
+
+Display menu after setup report:
+
+"[C] Continue - Save this and move to Game Vision (Step 2 of 8)"
+
+#### Menu Handling Logic:
+
+- IF C: Update frontmatter with `stepsCompleted: [1]`, then load, read entire file, then execute {nextStepFile}
+- IF user provides additional files: Load them, update inputDocuments and documentCounts, redisplay report
+- IF user asks questions: Answer and redisplay menu
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [frontmatter properly updated with stepsCompleted: [1] and documentCounts], will you then load and read fully `{nextStepFile}` to execute and begin game vision discovery.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- Existing workflow detected and properly handed off to step-01b
+- Fresh workflow initialized with template and proper frontmatter
+- Input documents discovered and loaded
+- All discovered files tracked in frontmatter `inputDocuments`
+- **Document counts stored in frontmatter `documentCounts`**
+- Menu presented and user input handled correctly
+- Frontmatter updated with `stepsCompleted: [1]` before proceeding
+
+### SYSTEM FAILURE:
+
+- Proceeding with fresh initialization when existing workflow exists
+- Not updating frontmatter with discovered input documents
+- **Not storing document counts in frontmatter**
+- Creating document without proper template structure
+- Proceeding without user selecting 'C' (Continue)
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.