feat: security overhaul (proxy ssrf fix, streaming sanitization, docker optimization)

2026-10-24 07:28:05 +02:00 · 2026-01-07 08:43:33 +01:00
1 parent 6d87ada2b8
commit 8df9a37baa
@@ -0,0 +1,26 @@
+category,technique_name,description,facilitation_prompts,best_for,energy_level,typical_duration
+game_design,MDA Framework Exploration,Explore game concepts through Mechanics-Dynamics-Aesthetics lens to ensure cohesive design from implementation to player experience,What mechanics create the core loop?|What dynamics emerge from these mechanics?|What aesthetic experience results?|How do they align?,holistic-design,moderate,20-30
+game_design,Core Loop Brainstorming,Design the fundamental moment-to-moment gameplay loop that players repeat - the heartbeat of your game,What does the player do?|What's the immediate reward?|Why do it again?|How does it evolve?,gameplay-foundation,high,15-25
+game_design,Player Fantasy Mining,Identify and amplify the core fantasy that players want to embody - what makes them feel powerful and engaged,What fantasy does the player live?|What makes them feel awesome?|What power do they wield?|What identity do they assume?,player-motivation,high,15-20
+game_design,Genre Mashup,Combine unexpected game genres to create innovative hybrid experiences that offer fresh gameplay,Take two unrelated genres|How do they merge?|What unique gameplay emerges?|What's the hook?,innovation,high,15-20
+game_design,Verbs Before Nouns,Focus on what players DO before what things ARE - prioritize actions over objects for engaging gameplay,What verbs define your game?|What actions feel good?|Build mechanics from verbs|Nouns support actions,mechanics-first,moderate,20-25
+game_design,Failure State Design,Work backwards from interesting failure conditions to create tension and meaningful choices,How can players fail interestingly?|What makes failure feel fair?|How does failure teach?|Recovery mechanics?,challenge-design,moderate,15-20
+game_design,Progression Curve Sculpting,Map the player's emotional and skill journey from tutorial to mastery - pace challenge and revelation,How does difficulty evolve?|When do we introduce concepts?|What's the skill ceiling?|How do we maintain flow?,pacing-balance,moderate,25-30
+game_design,Emergence Engineering,Design simple rule interactions that create complex unexpected player-driven outcomes,What simple rules combine?|What emerges from interactions?|How do players surprise you?|Systemic possibilities?,depth-complexity,moderate,20-25
+game_design,Accessibility Layers,Brainstorm how different skill levels and abilities can access your core experience meaningfully,Who might struggle with what?|What alternate inputs exist?|How do we preserve challenge?|Inclusive design options?,inclusive-design,moderate,20-25
+game_design,Reward Schedule Architecture,Design the timing and type of rewards to maintain player motivation and engagement,What rewards when?|Variable or fixed schedule?|Intrinsic vs extrinsic rewards?|Progression satisfaction?,engagement-retention,moderate,20-30
+narrative_game,Ludonarrative Harmony,Align story and gameplay so mechanics reinforce narrative themes - make meaning through play,What does gameplay express?|How do mechanics tell story?|Where do they conflict?|How to unify theme?,storytelling,moderate,20-25
+narrative_game,Environmental Storytelling,Use world design and ambient details to convey narrative without explicit exposition,What does the space communicate?|What happened here before?|Visual narrative clues?|Show don't tell?,world-building,moderate,15-20
+narrative_game,Player Agency Moments,Identify key decision points where player choice shapes narrative in meaningful ways,What choices matter?|How do consequences manifest?|Branch vs flavor choices?|Meaningful agency where?,player-choice,moderate,20-25
+narrative_game,Emotion Targeting,Design specific moments intended to evoke targeted emotional responses through integrated design,What emotion when?|How do all elements combine?|Music + mechanics + narrative?|Orchestrated feelings?,emotional-design,high,20-30
+systems_game,Economy Balancing Thought Experiments,Explore resource generation/consumption balance to prevent game-breaking exploits,What resources exist?|Generation vs consumption rates?|What loops emerge?|Where's the exploit?,economy-design,moderate,25-30
+systems_game,Meta-Game Layer Design,Brainstorm progression systems that persist beyond individual play sessions,What carries over between sessions?|Long-term goals?|How does meta feed core loop?|Retention hooks?,retention-systems,moderate,20-25
+multiplayer_game,Social Dynamics Mapping,Anticipate how players will interact and design mechanics that support desired social behaviors,How will players cooperate?|Competitive dynamics?|Toxic behavior prevention?|Positive interaction rewards?,social-design,moderate,20-30
+multiplayer_game,Spectator Experience Design,Consider how watching others play can be entertaining - esports and streaming potential,What's fun to watch?|Readable visual clarity?|Highlight moments?|Narrative for observers?,spectator-value,moderate,15-20
+creative_game,Constraint-Based Creativity,Embrace a specific limitation as your core design constraint and build everything around it,Pick a severe constraint|What if this was your ONLY mechanic?|Build a full game from limitation|Constraint as creativity catalyst,innovation,moderate,15-25
+creative_game,Game Feel Playground,Focus purely on how controls and feedback FEEL before worrying about context or goals,What feels juicy to do?|Controller response?|Visual/audio feedback?|Satisfying micro-interactions?,game-feel,high,20-30
+creative_game,One Button Game Challenge,Design interesting gameplay using only a single input - forces elegant simplicity,Only one button - what can it do?|Context changes meaning?|Timing variations?|Depth from simplicity?,minimalist-design,moderate,15-20
+wild_game,Remix an Existing Game,Take a well-known game and twist one core element - what new experience emerges?,Pick a famous game|Change ONE fundamental rule|What ripples from that change?|New game from mutation?,rapid-prototyping,high,10-15
+wild_game,Anti-Game Design,Design a game that deliberately breaks common conventions - subvert player expectations,What if we broke this rule?|Expectation subversion?|Anti-patterns as features?|Avant-garde possibilities?,experimental,moderate,15-20
+wild_game,Physics Playground,Start with an interesting physics interaction and build a game around that sensation,What physics are fun to play with?|Build game from physics toy|Emergent physics gameplay?|Sensation first?,prototype-first,high,15-25
+wild_game,Toy Before Game,Create a playful interactive toy with no goals first - then discover the game within it,What's fun to mess with?|No goals yet - just play|What game emerges organically?|Toy to game evolution?,discovery-design,high,20-30
@@ -0,0 +1,115 @@
+# Game Brainstorming Context
+
+This context guide provides game-specific considerations for brainstorming sessions focused on game design and development.
+
+## Session Focus Areas
+
+When brainstorming for games, consider exploring:
+
+- **Core Gameplay Loop** - What players do moment-to-moment
+- **Player Fantasy** - What identity/power fantasy does the game fulfill?
+- **Game Mechanics** - Rules and interactions that define play
+- **Game Dynamics** - Emergent behaviors from mechanic interactions
+- **Aesthetic Experience** - Emotional responses and feelings evoked
+- **Progression Systems** - How players grow and unlock content
+- **Challenge and Difficulty** - How to create engaging difficulty curves
+- **Social/Multiplayer Features** - How players interact with each other
+- **Narrative and World** - Story, setting, and environmental storytelling
+- **Art Direction and Feel** - Visual style and game feel
+- **Monetization** - Business model and revenue approach (if applicable)
+
+## Game Design Frameworks
+
+### MDA Framework
+
+- **Mechanics** - Rules and systems (what's in the code)
+- **Dynamics** - Runtime behavior (how mechanics interact)
+- **Aesthetics** - Emotional responses (what players feel)
+
+### Player Motivation (Bartle's Taxonomy)
+
+- **Achievers** - Goal completion and progression
+- **Explorers** - Discovery and understanding systems
+- **Socializers** - Interaction and relationships
+- **Killers** - Competition and dominance
+
+### Core Experience Questions
+
+- What does the player DO? (Verbs first, nouns second)
+- What makes them feel powerful/competent/awesome?
+- What's the central tension or challenge?
+- What's the "one more turn" factor?
+
+## Recommended Brainstorming Techniques
+
+### Game Design Specific Techniques
+
+(These are available as additional techniques in game brainstorming sessions)
+
+- **MDA Framework Exploration** - Design through mechanics-dynamics-aesthetics
+- **Core Loop Brainstorming** - Define the heartbeat of gameplay
+- **Player Fantasy Mining** - Identify and amplify player power fantasies
+- **Genre Mashup** - Combine unexpected genres for innovation
+- **Verbs Before Nouns** - Focus on actions before objects
+- **Failure State Design** - Work backwards from interesting failures
+- **Ludonarrative Harmony** - Align story and gameplay
+- **Game Feel Playground** - Focus purely on how controls feel
+
+### Standard Techniques Well-Suited for Games
+
+- **SCAMPER Method** - Innovate on existing game mechanics
+- **What If Scenarios** - Explore radical gameplay possibilities
+- **First Principles Thinking** - Rebuild game concepts from scratch
+- **Role Playing** - Generate ideas from player perspectives
+- **Analogical Thinking** - Find inspiration from other games/media
+- **Constraint-Based Creativity** - Design around limitations
+- **Morphological Analysis** - Explore mechanic combinations
+
+## Output Guidance
+
+Effective game brainstorming sessions should capture:
+
+1. **Core Concept** - High-level game vision and hook
+2. **Key Mechanics** - Primary gameplay verbs and interactions
+3. **Player Experience** - What it feels like to play
+4. **Unique Elements** - What makes this game special/different
+5. **Design Challenges** - Obstacles to solve during development
+6. **Prototype Ideas** - What to test first
+7. **Reference Games** - Existing games that inspire or inform
+8. **Open Questions** - What needs further exploration
+
+## Integration with Game Development Workflow
+
+Game brainstorming sessions typically feed into:
+
+- **Game Briefs** - High-level vision and core pillars
+- **Game Design Documents (GDD)** - Comprehensive design specifications
+- **Technical Design Docs** - Architecture for game systems
+- **Prototype Plans** - What to build to validate concepts
+- **Art Direction Documents** - Visual style and feel guides
+
+## Special Considerations for Game Design
+
+### Start With The Feel
+
+- How should controls feel? Responsive? Weighty? Floaty?
+- What's the "game feel" - the juice and feedback?
+- Can we prototype the core interaction quickly?
+
+### Think in Systems
+
+- How do mechanics interact?
+- What emergent behaviors arise?
+- Are there dominant strategies or exploits?
+
+### Design for Failure
+
+- How do players fail?
+- Is failure interesting and instructive?
+- What's the cost of failure?
+
+### Player Agency vs. Authored Experience
+
+- Where do players have meaningful choices?
+- Where is the experience authored/scripted?
+- How do we balance freedom and guidance?
@@ -0,0 +1,130 @@
+<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>
+<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
+<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>
+
+<workflow>
+
+  <step n="1" goal="Validate workflow readiness" tag="workflow-status">
+    <action>Check if {output_folder}/bmgd-workflow-status.yaml exists</action>
+
+    <check if="status file not found">
+      <output>No workflow status file found. Game brainstorming is optional - you can continue without status tracking.</output>
+      <action>Set standalone_mode = true</action>
+    </check>
+
+    <check if="status file found">
+      <action>Load the FULL file: {output_folder}/bmgd-workflow-status.yaml</action>
+      <action>Parse workflow_status section</action>
+      <action>Check status of "brainstorm-game" workflow</action>
+      <action>Get project_level from YAML metadata</action>
+      <action>Find first non-completed workflow (next expected workflow)</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="brainstorm-game status is file path (already completed)">
+        <output>⚠️ Game brainstorming session already completed: {{brainstorm-game status}}</output>
+        <ask>Re-running will create a new session. Continue? (y/n)</ask>
+        <check if="n">
+          <output>Exiting. Use workflow-status to see your next step.</output>
+          <action>Exit workflow</action>
+        </check>
+      </check>
+
+      <check if="brainstorm-game is not the next expected workflow (latter items are completed already in the list)">
+        <output>⚠️ Next expected workflow: {{next_workflow}}. Game brainstorming is out of sequence.</output>
+        <ask>Continue with game brainstorming anyway? (y/n)</ask>
+        <check if="n">
+          <output>Exiting. Run {{next_workflow}} instead.</output>
+          <action>Exit workflow</action>
+        </check>
+      </check>
+
+      <action>Set standalone_mode = false</action>
+    </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.)
+      - Key considerations for game design
+      - Recommended techniques for game brainstorming
+      - Output structure guidance
+    </action>
+    <action>Load game-specific brain techniques from: {game_brain_methods}</action>
+    <action>These additional techniques supplement the standard CIS brainstorming methods with game design-focused approaches like:
+      - MDA Framework exploration
+      - Core loop brainstorming
+      - Player fantasy mining
+      - Genre mashup
+      - And other game-specific ideation methods
+    </action>
+  </step>
+
+  <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="{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
+      - Guide the user through selected ideation methods
+      - Generate and capture brainstorming session results
+      - Save output to: {output_folder}/brainstorming-session-results-{{date}}.md
+    </invoke-workflow>
+  </step>
+
+  <step n="4" goal="Update status and complete" tag="workflow-status">
+    <check if="standalone_mode != true">
+      <action>Load the FULL file: {output_folder}/bmgd-workflow-status.yaml</action>
+      <action>Find workflow_status key "brainstorm-game"</action>
+      <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
+      <action>Update workflow_status["brainstorm-game"] = "{output_folder}/bmm-brainstorming-session-{{date}}.md"</action>
+      <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
+
+      <action>Find first non-completed workflow in workflow_status (next workflow to do)</action>
+      <action>Determine next agent from path file based on next workflow</action>
+    </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: brainstorm-game marked complete
+- Next workflow: {{next_workflow}}
+  {{else}}
+  **Note:** Running in standalone mode (no progress tracking)
+  {{/if}}
+
+**Next Steps:**
+
+{{#if standalone_mode != true}}
+
+- **Next workflow:** {{next_workflow}} ({{next_agent}} agent)
+- **Optional:** You can run other analysis workflows (research, game-brief) before proceeding
+
+Check status anytime with: `workflow-status`
+{{else}}
+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>
@@ -0,0 +1,165 @@
+---
+name: 'step-01-init'
+description: 'Initialize the game brainstorming workflow and validate readiness'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/brainstorm-game'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01-init.md'
+nextStepFile: '{workflow_path}/steps/step-02-context.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/brainstorming-session-{date}.md'
+
+# Context Files
+gameContext: '{workflow_path}/game-context.md'
+gameBrainMethods: '{workflow_path}/game-brain-methods.csv'
+---
+
+# Step 1: Initialize Brainstorming
+
+**Progress: Step 1 of 4** - Next: Load Context
+
+## STEP GOAL:
+
+Validate workflow readiness, check for workflow status tracking, and prepare for the game brainstorming session.
+
+## 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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- You are a creative game design facilitator
+- Focus on drawing out user's ideas
+- Game brainstorming is optional but valuable
+
+### Step-Specific Rules:
+
+- Check for workflow status file
+- Initialize session document with proper frontmatter
+- Prepare user for brainstorming mindset
+
+## EXECUTION PROTOCOLS:
+
+- Show your analysis before taking any action
+- Wait for user confirmation before proceeding
+- Update frontmatter `stepsCompleted: [1]` before loading next step
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Check Workflow Status
+
+**Search for workflow status file:**
+
+Check if `{output_folder}/bmgd-workflow-status.yaml` exists.
+
+**If status file NOT found:**
+
+"No workflow status file found. Game brainstorming is optional and can run standalone.
+
+Would you like to:
+
+1. Continue in standalone mode (no progress tracking)
+2. Run `workflow-init` first to set up tracking
+
+Your choice:"
+
+**If user continues:** Set `standalone_mode = true`
+
+**If status file found:**
+
+Load the file and check:
+
+- Is this a game project? (`project_type == 'game'`)
+- Has brainstorm-game already been completed?
+- Is this the next expected workflow?
+
+Handle each scenario appropriately with user prompts.
+
+### 2. Set Brainstorming Mindset
+
+"**Welcome to Game Brainstorming!**
+
+{{user_name}}, let's explore game ideas together.
+
+**Brainstorming Rules:**
+
+- There are no bad ideas in brainstorming
+- Quantity over quality initially
+- Build on ideas rather than criticize
+- Wild ideas are welcome
+- Defer judgment until later
+
+**What we'll do:**
+
+1. Load game-specific brainstorming techniques
+2. Explore your game concepts using various methods
+3. Capture and organize all ideas
+4. Save results for future refinement
+
+Ready to start brainstorming? [Y/N]"
+
+### 3. Initialize Output Document
+
+**If user confirms, create the session document:**
+
+Create `{outputFile}` with frontmatter:
+
+```markdown
+---
+title: 'Game Brainstorming Session'
+date: '{{date}}'
+author: '{{user_name}}'
+version: '1.0'
+stepsCompleted: [1]
+status: 'in-progress'
+---
+
+# Game Brainstorming Session
+
+## Session Info
+
+- **Date:** {{date}}
+- **Facilitator:** Game Designer Agent
+- **Participant:** {{user_name}}
+
+---
+
+_Ideas will be captured as we progress through the session._
+```
+
+### 4. Proceed to Context Step
+
+After initialization:
+
+- Update frontmatter: `stepsCompleted: [1]`
+- Load `{nextStepFile}`
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- Workflow status checked appropriately
+- User confirmed ready to brainstorm
+- Output document initialized
+- Brainstorming mindset established
+- Frontmatter updated with stepsCompleted: [1]
+
+### SYSTEM FAILURE:
+
+- Starting without user confirmation
+- Not checking workflow status
+- Missing document initialization
+- Not setting brainstorming tone
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
@@ -0,0 +1,211 @@
+---
+name: 'step-02-context'
+description: 'Load game-specific brainstorming context and techniques'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/brainstorm-game'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-02-context.md'
+nextStepFile: '{workflow_path}/steps/step-03-ideation.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/brainstorming-session-{date}.md'
+
+# Context Files
+gameContext: '{workflow_path}/game-context.md'
+gameBrainMethods: '{workflow_path}/game-brain-methods.csv'
+coreBrainstorming: '{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml'
+---
+
+# Step 2: Load Context
+
+**Progress: Step 2 of 4** - Next: Ideation Session
+
+## STEP GOAL:
+
+Load game-specific brainstorming context and techniques to guide the ideation session. Merge game techniques with core brainstorming methods.
+
+## 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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- You are a creative game design facilitator
+- Game-specific techniques enhance standard brainstorming
+- Understand various ideation methods deeply
+
+### Step-Specific Rules:
+
+- Load all context files completely
+- Present technique options to user
+- Let user select preferred approach
+
+## EXECUTION PROTOCOLS:
+
+- Show your analysis before taking any action
+- Present A/P/C menu after context loaded
+- ONLY proceed when user chooses C (Continue)
+- Update frontmatter `stepsCompleted: [1, 2]` before loading next step
+
+## COLLABORATION MENUS (A/P/C):
+
+- **A (Advanced Elicitation)**: Explore technique combinations
+- **P (Party Mode)**: Get perspectives on approaches
+- **C (Continue)**: Confirm context and proceed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Load Game Context
+
+**Load the game context document:**
+
+Read `{gameContext}` to understand:
+
+- Focus areas for game ideation
+- Key considerations for game design
+- Recommended techniques
+- Output structure guidance
+
+### 2. Load Game Brain Methods
+
+**Load game-specific techniques:**
+
+Read `{gameBrainMethods}` CSV to load:
+
+- MDA Framework exploration
+- Core loop brainstorming
+- Player fantasy mining
+- Genre mashup
+- And other game-specific methods
+
+### 3. Present Available Techniques
+
+"**Game Brainstorming Techniques Loaded!**
+
+I've loaded game-specific brainstorming methods:
+
+**Conceptual Techniques:**
+
+- **MDA Framework** - Mechanics, Dynamics, Aesthetics exploration
+- **Player Fantasy Mining** - What fantasy does the player fulfill?
+- **Core Loop Design** - Define the central gameplay loop
+- **Genre Mashup** - Combine unexpected genres
+
+**Experience Techniques:**
+
+- **Emotion Mapping** - Target emotions throughout gameplay
+- **Moment Design** - Plan memorable peak moments
+- **Flow Analysis** - Balance challenge and skill
+
+**Practical Techniques:**
+
+- **Constraint Box** - Creative limits spark innovation
+- **Reference Blending** - Combine inspiration sources
+- **What If Scenarios** - Explore radical possibilities
+
+**How would you like to brainstorm?**
+
+1. **Guided** - I'll walk you through techniques one by one
+2. **Selective** - Choose specific techniques to use
+3. **Freeform** - Open exploration with techniques as needed
+4. **YOLO** - Let me drive the session with all techniques
+
+Your preference:"
+
+### 4. Capture User Preference
+
+**Based on selection:**
+
+- **Guided**: Prepare structured technique sequence
+- **Selective**: Present technique menu for selection
+- **Freeform**: Prepare all techniques for on-demand use
+- **YOLO**: Plan comprehensive technique coverage
+
+### 5. Generate Context Section
+
+Based on the conversation, prepare the content:
+
+```markdown
+## Brainstorming Approach
+
+**Selected Mode:** {{selected_mode}}
+
+**Techniques Available:**
+{{technique_list}}
+
+**Focus Areas:**
+{{focus_areas_from_context}}
+```
+
+### 6. Present Content and Menu
+
+Show the loaded context and present:
+
+"I've prepared the brainstorming context.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 5]
+
+**Ready to start ideation?**
+
+**Select an Option:**
+[A] Advanced Elicitation - Explore technique combinations
+[P] Party Mode - Get perspectives on approaches
+[C] Continue - Save this and move to Ideation Session (Step 3 of 4)"
+
+### 7. Handle Menu Selection
+
+#### IF A (Advanced Elicitation):
+
+- Explore technique combinations and synergies
+- Ask user: "Accept these changes? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF P (Party Mode):
+
+- Get multiple perspectives on brainstorming approaches
+- Ask user: "Accept these changes? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF C (Continue):
+
+- Append the context section to `{outputFile}`
+- Update frontmatter: `stepsCompleted: [1, 2]`
+- Load `{nextStepFile}`
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [context saved with frontmatter updated], will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- Game context loaded completely
+- Game brain methods loaded from CSV
+- Techniques presented clearly
+- User selected brainstorming approach
+- A/P/C menu presented and handled correctly
+- Frontmatter updated with stepsCompleted: [1, 2]
+
+### SYSTEM FAILURE:
+
+- Not loading context files
+- Proceeding without user technique selection
+- Not presenting A/P/C menu after context
+- Proceeding without user selecting 'C'
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
@@ -0,0 +1,290 @@
+---
+name: 'step-03-ideation'
+description: 'Execute the brainstorming session with game-specific techniques'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/brainstorm-game'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-03-ideation.md'
+nextStepFile: '{workflow_path}/steps/step-04-complete.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/brainstorming-session-{date}.md'
+
+# Core Brainstorming Reference
+coreBrainstorming: '{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 3: Ideation Session
+
+**Progress: Step 3 of 4** - Next: Complete Session
+
+## STEP GOAL:
+
+Facilitate the actual brainstorming session using selected techniques. Capture all ideas, concepts, and insights generated during the session.
+
+## 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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- You are a creative game design facilitator
+- Draw out user's ideas - don't generate for them
+- Use techniques to unlock creativity
+- ALL ideas are valid during brainstorming
+
+### Step-Specific Rules:
+
+- Apply selected techniques from Step 2
+- Capture EVERY idea, no matter how wild
+- Build on ideas rather than criticize
+- User drives the ideation; you facilitate
+
+## EXECUTION PROTOCOLS:
+
+- Show your analysis before taking any action
+- Present A/P/C menu after ideation session
+- ONLY proceed when user chooses C (Continue)
+- Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
+
+## COLLABORATION MENUS (A/P/C):
+
+- **A (Advanced Elicitation)**: Dig deeper into promising ideas
+- **P (Party Mode)**: Get multiple perspectives on concepts
+- **C (Continue)**: Save ideas and complete session
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Begin Ideation Session
+
+**Start the brainstorming:**
+
+"**Let's Start Brainstorming!**
+
+Based on your selected approach ({{selected_mode}}), let's explore game ideas.
+
+**First Question:**
+What kind of game experience are you drawn to?
+
+Think about:
+
+- A feeling you want players to have
+- A mechanic you find compelling
+- A theme or setting that excites you
+- A problem you want to solve through games
+
+Share whatever comes to mind:"
+
+### 2. Apply Selected Techniques
+
+**Based on mode selected in Step 2:**
+
+**For Guided Mode:**
+Walk through each technique sequentially:
+
+1. **Player Fantasy Mining**
+   "What fantasy does your player want to fulfill? Being a hero? Building an empire? Surviving? Exploring? Describe the core fantasy."
+
+2. **Core Loop Brainstorming**
+   "What's the central action players repeat? Think: [Action] → [Reward/Feedback] → [Motivation to continue]"
+
+3. **MDA Framework**
+   "Let's explore: What Aesthetics (emotions)? What Dynamics (behaviors)? What Mechanics enable them?"
+
+4. **Genre Mashup**
+   "What two unexpected genres could combine? Example: 'Puzzle + Horror' = tension through problem-solving"
+
+**For Selective Mode:**
+Present technique menu, execute chosen techniques.
+
+**For Freeform Mode:**
+Follow user's exploration, introduce techniques when relevant.
+
+**For YOLO Mode:**
+Drive comprehensive exploration using all techniques.
+
+### 3. Capture Ideas Throughout
+
+**For EACH idea generated:**
+
+Add to running list:
+
+```markdown
+### Idea: {{idea_title}}
+
+**Source Technique:** {{technique_used}}
+**Description:** {{idea_description}}
+**Potential:** {{quick_assessment}}
+**Build-on ideas:** {{related_concepts}}
+```
+
+### 4. Probe for Depth
+
+**Throughout the session:**
+
+Use probing questions:
+
+- "What makes that exciting to you?"
+- "How would that feel moment-to-moment?"
+- "What's the twist that makes it unique?"
+- "What game does this remind you of, and how is it different?"
+- "What would the 'aha' moment be?"
+
+### 5. Build Idea Connections
+
+**As ideas accumulate:**
+
+"I'm noticing some connections:
+
+- {{idea_1}} and {{idea_2}} share {{common_element}}
+- {{idea_3}} could be the 'twist' for {{idea_4}}
+
+Should we explore these combinations?"
+
+### 6. Session Checkpoint
+
+**After sufficient ideation:**
+
+"**Brainstorming Progress**
+
+We've generated {{idea_count}} ideas so far:
+
+**Top Concepts:**
+{{summary_of_strongest_ideas}}
+
+**Themes Emerging:**
+{{recurring_themes}}
+
+**Would you like to:**
+
+1. Continue exploring (more techniques)
+2. Deep dive into a specific concept
+3. Wrap up and save what we have
+
+Your choice:"
+
+### 7. Generate Ideation Section
+
+Based on all ideas captured, prepare the content:
+
+```markdown
+## Ideas Generated
+
+### Concept 1: {{concept_name}}
+
+{{full_concept_description}}
+
+**Core Elements:**
+
+- {{element_1}}
+- {{element_2}}
+
+**Questions to Explore:**
+
+- {{question_1}}
+- {{question_2}}
+
+---
+
+### Concept 2: {{concept_name}}
+
+{{repeat_structure}}
+
+---
+
+## Themes and Patterns
+
+{{observed_themes}}
+
+## Promising Combinations
+
+{{combination_ideas}}
+
+## Raw Ideas List
+
+{{all_ideas_bullet_points}}
+```
+
+### 8. Present Content and Menu
+
+Show the generated content to the user and present:
+
+"**Ideation Session Summary**
+
+Here's everything we captured:
+
+[Show the complete markdown content from step 7]
+
+**Session Stats:**
+
+- Ideas generated: {{count}}
+- Concepts developed: {{count}}
+- Themes identified: {{count}}
+
+**Select an Option:**
+[A] Advanced Elicitation - Dig deeper into promising ideas
+[P] Party Mode - Get multiple perspectives on concepts
+[C] Continue - Save ideas and complete session (Step 4 of 4)"
+
+### 9. Handle Menu Selection
+
+#### IF A (Advanced Elicitation):
+
+- Deep dive into selected concepts
+- Ask user: "Accept these additions? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF P (Party Mode):
+
+- Get diverse perspectives on concepts
+- Ask user: "Accept these perspectives? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF C (Continue):
+
+- Append the ideation section to `{outputFile}`
+- Update frontmatter: `stepsCompleted: [1, 2, 3]`
+- Load `{nextStepFile}`
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [ideation content saved with frontmatter updated], will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- User drove the ideation
+- Multiple techniques applied
+- All ideas captured without judgment
+- Connections and themes identified
+- Ideas organized and summarized
+- A/P/C menu presented and handled correctly
+- Frontmatter updated with stepsCompleted: [1, 2, 3]
+
+### SYSTEM FAILURE:
+
+- Generating ideas FOR the user instead of WITH them
+- Dismissing or criticizing ideas during session
+- Not capturing all ideas
+- Rushing through techniques
+- Not presenting A/P/C menu after ideation
+- Proceeding without user selecting 'C'
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
@@ -0,0 +1,276 @@
+---
+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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### 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}/bmgd-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.
@@ -0,0 +1,50 @@
+# 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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
@@ -0,0 +1,42 @@
+# Brainstorm Game Workflow Configuration
+name: "brainstorm-game"
+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"
+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"
+game_dev_experience: "{config_source}:game_dev_experience"
+date: system-generated
+
+# Workflow components - Step-file architecture
+installed_path: "{project-root}/_bmad/bmgd/workflows/1-preproduction/brainstorm-game"
+instructions: "{installed_path}/workflow.md"
+template: false
+
+# 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 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
@@ -0,0 +1,128 @@
+# Game Brief Validation Checklist
+
+Use this checklist to ensure your game brief is complete and ready for GDD creation.
+
+## Game Vision ✓
+
+- [ ] **Core Concept** is clear and concise (one sentence)
+- [ ] **Elevator Pitch** hooks the reader in 2-3 sentences
+- [ ] **Vision Statement** is aspirational but achievable
+- [ ] Vision captures the emotional experience you want to create
+
+## Target Market ✓
+
+- [ ] **Primary Audience** is specific (not just "gamers")
+- [ ] Age range and experience level are defined
+- [ ] Play session expectations are realistic
+- [ ] **Market Context** demonstrates opportunity
+- [ ] Competitive landscape is understood
+- [ ] You know why this audience will care
+
+## Game Fundamentals ✓
+
+- [ ] **Core Gameplay Pillars** (2-4) are clearly defined
+- [ ] Each pillar is specific and measurable
+- [ ] **Primary Mechanics** describe what players actually DO
+- [ ] **Player Experience Goals** connect mechanics to emotions
+- [ ] Core loop is clear and compelling
+
+## Scope and Constraints ✓
+
+- [ ] **Target Platforms** are prioritized
+- [ ] **Development Timeline** is realistic
+- [ ] **Budget** aligns with scope
+- [ ] **Team Resources** (size, skills) are documented
+- [ ] **Technical Constraints** are identified
+- [ ] Scope matches team capability
+
+## Reference Framework ✓
+
+- [ ] **Inspiration Games** (3-5) are listed with specifics
+- [ ] You know what you're taking vs. NOT taking from each
+- [ ] **Competitive Analysis** covers direct and indirect competitors
+- [ ] **Key Differentiators** are genuine and valuable
+- [ ] Differentiators are specific (not "just better")
+
+## Content Framework ✓
+
+- [ ] **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 and Audio Direction ✓
+
+- [ ] **Visual Style** is described with references
+- [ ] 2D vs. 3D is decided
+- [ ] **Audio Style** matches game mood
+- [ ] **Production Approach** is realistic for team/budget
+- [ ] Style complexity matches capabilities
+
+## Risk Assessment ✓
+
+- [ ] **Key Risks** are honestly identified
+- [ ] **Technical Challenges** are documented
+- [ ] **Market Risks** are considered
+- [ ] **Mitigation Strategies** are actionable
+- [ ] Assumptions to validate are listed
+
+## Success Criteria ✓
+
+- [ ] **MVP Definition** is truly minimal
+- [ ] MVP can validate core gameplay hypothesis
+- [ ] **Success Metrics** are specific and measurable
+- [ ] **Launch Goals** are realistic
+- [ ] You know what "done" looks like for MVP
+
+## Next Steps ✓
+
+- [ ] **Immediate Actions** are prioritized
+- [ ] **Research Needs** are identified
+- [ ] **Open Questions** are documented
+- [ ] Critical path is clear
+- [ ] Blockers are identified
+
+## Overall Quality ✓
+
+- [ ] Brief is clear and concise (3-5 pages)
+- [ ] Sections are internally consistent
+- [ ] Scope is realistic for team/timeline/budget
+- [ ] Vision is compelling and achievable
+- [ ] You're excited to build this game
+- [ ] Team/stakeholders can understand the vision
+
+## Red Flags 🚩
+
+Watch for these warning signs:
+
+- [ ] ❌ Scope too large for team/timeline
+- [ ] ❌ Unclear core loop or pillars
+- [ ] ❌ Target audience is "everyone"
+- [ ] ❌ Differentiators are vague or weak
+- [ ] ❌ No prototype plan for risky mechanics
+- [ ] ❌ Budget/timeline is wishful thinking
+- [ ] ❌ Market is saturated with no clear positioning
+- [ ] ❌ MVP is not actually minimal
+
+## Ready for Next Steps?
+
+If you've checked most boxes and have no major red flags:
+
+✅ **Ready to proceed to:**
+
+- Prototype core mechanic
+- GDD workflow
+- Team/stakeholder review
+- Market validation
+
+⚠️ **Need more work if:**
+
+- Multiple sections incomplete
+- Red flags present
+- Team/stakeholders don't align
+- Core concept unclear
+
+---
+
+_This checklist is a guide, not a gate. Use your judgment based on project needs._
@@ -0,0 +1,373 @@
+# Game Brief - Interactive Workflow Instructions
+
+<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>
+<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
+
+<critical>DOCUMENT OUTPUT: Concise, professional, game-design focused. Use tables/lists over prose. User skill level ({user_skill_level}) affects conversation style ONLY, not document content.</critical>
+<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>
+
+<workflow>
+
+<step n="0" goal="Validate workflow readiness" tag="workflow-status">
+<action>Check if {output_folder}/bmgd-workflow-status.yaml exists</action>
+
+<check if="status file not found">
+  <output>No workflow status file found. Game brief is optional - you can continue without status tracking.</output>
+  <action>Set standalone_mode = true</action>
+</check>
+
+<check if="status file found">
+  <action>Load the FULL file: {output_folder}/bmgd-workflow-status.yaml</action>
+  <action>Parse workflow_status section</action>
+  <action>Check status of "game-brief" workflow</action>
+  <action>Get project_level from YAML metadata</action>
+  <action>Find first non-completed workflow (next expected workflow)</action>
+
+  <check if="project_type != 'game'">
+    <output>Note: This is a {{project_type}} project. Game brief is designed for game projects.</output>
+    <ask>Continue with game brief anyway? (y/n)</ask>
+    <check if="n">
+      <action>Exit workflow</action>
+    </check>
+  </check>
+
+  <check if="game-brief status is file path (already completed)">
+    <output>⚠️ Game Brief already completed: {{game-brief status}}</output>
+    <ask>Re-running will overwrite the existing brief. Continue? (y/n)</ask>
+    <check if="n">
+      <output>Exiting. Use workflow-status to see your next step.</output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
+
+  <check if="game-brief is not the next expected workflow (latter items are completed already in the list)">
+    <output>⚠️ Next expected workflow: {{next_workflow}}. Game Brief is out of sequence.</output>
+    <ask>Continue with Game Brief anyway? (y/n)</ask>
+    <check if="n">
+      <output>Exiting. Run {{next_workflow}} instead.</output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
+
+<action>Set standalone_mode = false</action>
+</check>
+</step>
+
+<step n="1" goal="Initialize game brief session">
+<action>Welcome the user in {communication_language} to the Game Brief creation process</action>
+<action>Explain this is a collaborative process to define their game vision, capturing the essence of what they want to create</action>
+<action>Ask for the working title of their game</action>
+<template-output>game_name</template-output>
+</step>
+
+<step n="1" goal="Gather available inputs and context">
+<action>Explore what existing materials the user has available to inform the brief</action>
+<action>Offer options for input sources: market research, brainstorming results, competitive analysis, design notes, reference games, or starting fresh</action>
+<action>If documents are provided, load and analyze them to extract key insights, themes, and patterns</action>
+<action>Engage the user about their core vision: what gameplay experience they want to create, what emotions players should feel, and what sparked this game idea</action>
+<action>Build initial understanding through conversational exploration rather than rigid questioning</action>
+
+<template-output>initial_context</template-output>
+</step>
+
+<step n="2" goal="Choose collaboration mode">
+<ask>How would you like to work through the brief?
+
+**1. Interactive Mode** - We'll work through each section together, discussing and refining as we go
+**2. YOLO Mode** - I'll generate a complete draft based on our conversation so far, then we'll refine it together
+
+Which approach works best for you?</ask>
+
+<action>Store the user's preference for mode</action>
+<template-output>collaboration_mode</template-output>
+</step>
+
+<step n="3" goal="Define game vision" if="collaboration_mode == 'interactive'">
+<action>Guide user to articulate their game vision across three levels of depth</action>
+<action>Help them craft a one-sentence core concept that captures the essence (reference successful games like "A roguelike deck-builder where you climb a mysterious spire" as examples)</action>
+<action>Develop an elevator pitch (2-3 sentences) that would compel a publisher or player - refine until it's concise but hooks attention</action>
+<action>Explore their aspirational vision statement: the experience they want to create and what makes it meaningful - ensure it's ambitious yet achievable</action>
+<action>Refine through conversation, challenging vague language and elevating compelling ideas</action>
+
+<template-output>core_concept</template-output>
+<template-output>elevator_pitch</template-output>
+<template-output>vision_statement</template-output>
+</step>
+
+<step n="4" goal="Identify target market" if="collaboration_mode == 'interactive'">
+<action>Guide user to define their primary target audience with specific demographics, gaming preferences, and behavioral characteristics</action>
+<action>Push for specificity beyond generic descriptions like "people who like fun games" - challenge vague answers</action>
+<action>Explore secondary audiences if applicable and how their needs might differ</action>
+<action>Investigate the market context: opportunity size, competitive landscape, similar successful games, and why now is the right time</action>
+<action>Help identify a realistic and reachable audience segment based on evidence or well-reasoned assumptions</action>
+
+<template-output>primary_audience</template-output>
+<template-output>secondary_audience</template-output>
+<template-output>market_context</template-output>
+</step>
+
+<step n="5" goal="Define game fundamentals" if="collaboration_mode == 'interactive'">
+<action>Help user identify 2-4 core gameplay pillars that fundamentally define their game - everything should support these pillars</action>
+<action>Provide examples from successful games for inspiration (Hollow Knight's "tight controls + challenging combat + rewarding exploration")</action>
+<action>Explore what the player actually DOES - core actions, key systems, and interaction models</action>
+<action>Define the emotional experience goals: what feelings are you designing for (tension/relief, mastery/growth, creativity/expression, discovery/surprise)</action>
+<action>Ensure pillars are specific and measurable, focusing on player actions rather than implementation details</action>
+<action>Connect mechanics directly to emotional experiences through guided discussion</action>
+
+<template-output>core_gameplay_pillars</template-output>
+<template-output>primary_mechanics</template-output>
+<template-output>player_experience_goals</template-output>
+</step>
+
+<step n="6" goal="Define scope and constraints" if="collaboration_mode == 'interactive'">
+<action>Help user establish realistic project constraints across all key dimensions</action>
+<action>Explore target platforms and prioritization (PC, console, mobile, web)</action>
+<action>Discuss development timeline: release targets, fixed deadlines, phased release strategies</action>
+<action>Investigate budget reality: funding source, asset creation costs, marketing, tools and software</action>
+<action>Assess team resources: size, roles, availability, skills gaps, outsourcing needs</action>
+<action>Define technical constraints: engine choice, performance targets, file size limits, accessibility requirements</action>
+<action>Push for realism about scope - identify potential blockers early and document resource assumptions</action>
+
+<template-output>target_platforms</template-output>
+<template-output>development_timeline</template-output>
+<template-output>budget_considerations</template-output>
+<template-output>team_resources</template-output>
+<template-output>technical_constraints</template-output>
+</step>
+
+<step n="7" goal="Establish reference framework" if="collaboration_mode == 'interactive'">
+<action>Guide user to identify 3-5 inspiration games and articulate what they're drawing from each (mechanics, feel, art style) and explicitly what they're NOT taking</action>
+<action>Conduct competitive analysis: identify direct and indirect competitors, analyze what they do well and poorly, and define how this game will differ</action>
+<action>Explore key differentiators and unique value proposition - what's the hook that makes players choose this game over alternatives</action>
+<action>Challenge "just better" thinking - push for genuine, specific differentiation that's actually valuable to players</action>
+<action>Validate that differentiators are concrete, achievable, and compelling</action>
+
+<template-output>inspiration_games</template-output>
+<template-output>competitive_analysis</template-output>
+<template-output>key_differentiators</template-output>
+</step>
+
+<step n="8" goal="Define content framework" if="collaboration_mode == 'interactive'">
+<action>Explore the game's world and setting: location, time period, world-building depth, narrative importance, and genre context</action>
+<action>Define narrative approach: story-driven/light/absent, linear/branching/emergent, delivery methods (cutscenes, dialogue, environmental), writing scope</action>
+<action>Estimate content volume realistically: playthrough length, level/stage count, replayability strategy, total asset volume</action>
+<action>Identify if a dedicated narrative workflow will be needed later based on story complexity</action>
+<action>Flag content-heavy areas that require detailed planning and resource allocation</action>
+
+<template-output>world_setting</template-output>
+<template-output>narrative_approach</template-output>
+<template-output>content_volume</template-output>
+</step>
+
+<step n="9" goal="Define art and audio direction" if="collaboration_mode == 'interactive'">
+<action>Explore visual style direction: art style preference, color palette and mood, reference games/images, 2D vs 3D, animation requirements</action>
+<action>Define audio style: music genre and mood, SFX approach, voice acting scope, audio's importance to gameplay</action>
+<action>Discuss production approach: in-house creation vs outsourcing, asset store usage, AI/generative tools, style complexity vs team capability</action>
+<action>Ensure art and audio vision aligns realistically with budget and team skills - identify potential production bottlenecks early</action>
+<action>Note if a comprehensive style guide will be needed for consistent production</action>
+
+<template-output>visual_style</template-output>
+<template-output>audio_style</template-output>
+<template-output>production_approach</template-output>
+</step>
+
+<step n="10" goal="Assess risks" if="collaboration_mode == 'interactive'">
+<action>Facilitate honest risk assessment across all dimensions - what could prevent completion, what could make it unfun, what assumptions might be wrong</action>
+<action>Identify technical challenges: unproven elements, performance concerns, platform-specific issues, tool dependencies</action>
+<action>Explore market risks: saturation, trend dependency, competition intensity, discoverability challenges</action>
+<action>For each major risk, develop actionable mitigation strategies - how to validate assumptions, backup plans, early prototyping opportunities</action>
+<action>Prioritize risks by impact and likelihood, focusing on proactive mitigation rather than passive worry</action>
+
+<template-output>key_risks</template-output>
+<template-output>technical_challenges</template-output>
+<template-output>market_risks</template-output>
+<template-output>mitigation_strategies</template-output>
+</step>
+
+<step n="11" goal="Define success criteria" if="collaboration_mode == 'interactive'">
+<action>Define the MVP (Minimum Playable Version) - what's the absolute minimum where the core loop is fun and complete, with essential content only</action>
+<action>Establish specific, measurable success metrics: player acquisition, retention rates, session length, completion rate, review scores, revenue targets, community engagement</action>
+<action>Set concrete launch goals: first-month sales/downloads, review score targets, streamer/press coverage, community size</action>
+<action>Push for specificity and measurability - challenge vague aspirations with "how will you measure that?"</action>
+<action>Clearly distinguish between MVP milestones and full release goals, ensuring all targets are realistic given resources</action>
+
+<template-output>mvp_definition</template-output>
+<template-output>success_metrics</template-output>
+<template-output>launch_goals</template-output>
+</step>
+
+<step n="12" goal="Identify immediate next steps" if="collaboration_mode == 'interactive'">
+<action>Identify immediate actions to take right after this brief: prototype core mechanics, create art style tests, validate technical feasibility, build vertical slice, playtest with target audience</action>
+<action>Determine research needs: market validation, technical proof of concept, player interest testing, competitive deep-dive</action>
+<action>Document open questions and uncertainties: unresolved design questions, technical unknowns, market validation needs, resource/budget questions</action>
+<action>Create actionable, specific next steps - prioritize by importance and dependency</action>
+<action>Identify blockers that must be resolved before moving forward</action>
+
+<template-output>immediate_actions</template-output>
+<template-output>research_needs</template-output>
+<template-output>open_questions</template-output>
+</step>
+
+<!-- YOLO Mode - Generate everything then refine -->
+<step n="3" goal="Generate complete brief draft" if="collaboration_mode == 'yolo'">
+<action>Based on initial context and any provided documents, generate a complete game brief covering all sections</action>
+<action>Make reasonable assumptions where information is missing</action>
+<action>Flag areas that need user validation with [NEEDS CONFIRMATION] tags</action>
+
+<template-output>core_concept</template-output>
+<template-output>elevator_pitch</template-output>
+<template-output>vision_statement</template-output>
+<template-output>primary_audience</template-output>
+<template-output>secondary_audience</template-output>
+<template-output>market_context</template-output>
+<template-output>core_gameplay_pillars</template-output>
+<template-output>primary_mechanics</template-output>
+<template-output>player_experience_goals</template-output>
+<template-output>target_platforms</template-output>
+<template-output>development_timeline</template-output>
+<template-output>budget_considerations</template-output>
+<template-output>team_resources</template-output>
+<template-output>technical_constraints</template-output>
+<template-output>inspiration_games</template-output>
+<template-output>competitive_analysis</template-output>
+<template-output>key_differentiators</template-output>
+<template-output>world_setting</template-output>
+<template-output>narrative_approach</template-output>
+<template-output>content_volume</template-output>
+<template-output>visual_style</template-output>
+<template-output>audio_style</template-output>
+<template-output>production_approach</template-output>
+<template-output>key_risks</template-output>
+<template-output>technical_challenges</template-output>
+<template-output>market_risks</template-output>
+<template-output>mitigation_strategies</template-output>
+<template-output>mvp_definition</template-output>
+<template-output>success_metrics</template-output>
+<template-output>launch_goals</template-output>
+<template-output>immediate_actions</template-output>
+<template-output>research_needs</template-output>
+<template-output>open_questions</template-output>
+
+<action>Present the complete draft to the user</action>
+<ask>Here's the complete game brief draft. What would you like to adjust or refine?</ask>
+</step>
+
+<step n="4" goal="Refine brief sections" repeat="until-approved" if="collaboration_mode == 'yolo'">
+<ask>Which section would you like to refine?
+
+1. Game Vision
+2. Target Market
+3. Game Fundamentals
+4. Scope and Constraints
+5. Reference Framework
+6. Content Framework
+7. Art and Audio Direction
+8. Risk Assessment
+9. Success Criteria
+10. Next Steps
+11. Save and continue</ask>
+
+<action>Work with user to refine selected section</action>
+<action>Update relevant template outputs</action>
+</step>
+
+<!-- Final steps for both modes -->
+<step n="13" goal="Create executive summary">
+<action>Synthesize all sections into a compelling executive summary</action>
+<action>Include:
+- Game concept in 1-2 sentences
+- Target audience and market
+- Core gameplay pillars
+- Key differentiators
+- Success vision</action>
+
+<template-output>executive_summary</template-output>
+</step>
+
+<step n="14" goal="Compile supporting materials">
+<action>If research documents were provided, create a summary of key findings</action>
+<action>Document any stakeholder input received during the process</action>
+<action>Compile list of reference games and resources</action>
+
+<template-output>research_summary</template-output>
+<template-output>stakeholder_input</template-output>
+<template-output>references</template-output>
+</step>
+
+<step n="15" goal="Final review and handoff">
+<action>Generate the complete game brief document</action>
+<action>Review all sections for completeness and consistency</action>
+<action>Flag any areas that need design attention with [DESIGN-TODO] tags</action>
+
+<ask>The game brief is complete! Would you like to:
+
+1. Review the entire document
+2. Make final adjustments
+3. Generate an executive summary version (3-page limit)
+4. Save and prepare for GDD creation
+
+This brief will serve as the primary input for creating the Game Design Document (GDD).
+
+**Recommended next steps:**
+
+- Create prototype of core mechanic
+- Proceed to GDD workflow: `workflow gdd`
+- Validate assumptions with target players</ask>
+
+<check if="user chooses option 3 (executive summary)">
+  <action>Create condensed 3-page executive brief focusing on: core concept, target market, gameplay pillars, key differentiators, and success criteria</action>
+  <action>Save as: {output_folder}/game-brief-executive-{{game_name}}-{{date}}.md</action>
+</check>
+
+<template-output>final_brief</template-output>
+<template-output>executive_brief</template-output>
+</step>
+
+<step n="16" goal="Update status and complete" tag="workflow-status">
+<check if="standalone_mode != true">
+  <action>Load the FULL file: {output_folder}/bmgd-workflow-status.yaml</action>
+  <action>Find workflow_status key "game-brief"</action>
+  <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
+  <action>Update workflow_status["game-brief"] = "{output_folder}/bmm-game-brief-{{game_name}}-{{date}}.md"</action>
+  <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
+
+<action>Find first non-completed workflow in workflow_status (next workflow to do)</action>
+<action>Determine next agent from path file based on next workflow</action>
+</check>
+
+<output>**✅ Game Brief Complete, {user_name}!**
+
+**Brief Document:**
+
+- Game brief saved to {output_folder}/bmm-game-brief-{{game_name}}-{{date}}.md
+
+{{#if standalone_mode != true}}
+**Status Updated:**
+
+- Progress tracking updated: game-brief marked complete
+- Next workflow: {{next_workflow}}
+  {{else}}
+  **Note:** Running in standalone mode (no progress tracking)
+  {{/if}}
+
+**Next Steps:**
+
+{{#if standalone_mode != true}}
+
+- **Next workflow:** {{next_workflow}} ({{next_agent}} agent)
+- **Optional:** Consider creating a prototype of core mechanic or validating assumptions with target players before proceeding
+
+Check status anytime with: `workflow-status`
+{{else}}
+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>
@@ -0,0 +1,224 @@
+---
+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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### 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.
@@ -0,0 +1,152 @@
+---
+name: 'step-01b-continue'
+description: 'Resume an interrupted Game Brief workflow from the last completed step'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/game-brief.md'
+---
+
+# Step 1B: Workflow Continuation
+
+## STEP GOAL:
+
+Resume the Game Brief workflow from where it was left off, ensuring smooth continuation with full context restoration.
+
+## 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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- You are a veteran game designer facilitator collaborating with a creative peer
+- We engage in collaborative dialogue, not command-response
+- Resume workflow from exact point where it was interrupted
+
+### Step-Specific Rules:
+
+- FOCUS on understanding where we left off and continuing appropriately
+- FORBIDDEN to modify content completed in previous steps
+- Only reload documents that were already tracked in `inputDocuments`
+
+## EXECUTION PROTOCOLS:
+
+- Show your analysis of current state before taking action
+- Keep existing frontmatter `stepsCompleted` values
+- Only load documents that were already tracked in `inputDocuments`
+- FORBIDDEN to discover new input documents during continuation
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Analyze Current State
+
+**State Assessment:**
+Review the frontmatter to understand:
+
+- `stepsCompleted`: Which steps are already done
+- `lastStep`: The most recently completed step number
+- `inputDocuments`: What context was already loaded
+- `documentCounts`: brainstorming, research, notes counts
+- `game_name`: The game name (if set)
+- All other frontmatter variables
+
+### 2. Restore Context Documents
+
+**Context Reloading:**
+
+- For each document in `inputDocuments`, load the complete file
+- This ensures you have full context for continuation
+- Don't discover new documents - only reload what was previously processed
+
+### 3. Present Current Progress
+
+**Progress Report to User:**
+"Welcome back {{user_name}}! I'm resuming our Game Brief collaboration for {{game_name or project_name}}.
+
+**Current Progress:**
+
+- Steps completed: {stepsCompleted}
+- Last worked on: Step {lastStep}
+- Context documents available: {len(inputDocuments)} files
+
+**Document Status:**
+
+- Current Game Brief is ready with all completed sections
+- Ready to continue from where we left off
+
+Does this look right, or do you want to make any adjustments before we proceed?"
+
+### 4. Determine Continuation Path
+
+**Next Step Logic:**
+Based on `lastStep` value, determine which step to load next:
+
+- If `lastStep = 1` -> Load `./step-02-vision.md`
+- If `lastStep = 2` -> Load `./step-03-market.md`
+- If `lastStep = 3` -> Load `./step-04-fundamentals.md`
+- If `lastStep = 4` -> Load `./step-05-scope.md`
+- If `lastStep = 5` -> Load `./step-06-references.md`
+- If `lastStep = 6` -> Load `./step-07-content.md`
+- If `lastStep = 7` -> Load `./step-08-complete.md`
+- If `lastStep = 8` -> Workflow already complete
+
+### 5. Handle Workflow Completion
+
+**If workflow already complete (`lastStep = 8`):**
+"Great news! It looks like we've already completed the Game Brief workflow for {{game_name}}.
+
+The final document is ready at `{outputFile}` with all sections completed.
+
+Would you like me to:
+
+- Review the completed brief with you
+- Suggest next workflow steps (like GDD creation)
+- Start a new brief revision
+
+What would be most helpful?"
+
+### 6. Present MENU OPTIONS
+
+**If workflow not complete:**
+Display: "Ready to continue with Step {nextStepNumber}?
+
+**Select an Option:** [C] Continue to next step"
+
+#### Menu Handling Logic:
+
+- IF C: Load, read entire file, then execute the appropriate next step file based on `lastStep`
+- IF Any other comments or queries: respond and redisplay menu
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [current state confirmed], will you then load and read fully the appropriate next step file to resume the workflow.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- All previous input documents successfully reloaded
+- Current workflow state accurately analyzed and presented
+- User confirms understanding of progress before continuation
+- Correct next step identified and prepared for loading
+
+### SYSTEM FAILURE:
+
+- Discovering new input documents instead of reloading existing ones
+- Modifying content from already completed steps
+- Loading wrong next step based on `lastStep` value
+- Proceeding without user confirmation of current state
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
@@ -0,0 +1,219 @@
+---
+name: 'step-02-vision'
+description: 'Define the core game vision including name, concept, pitch, and vision statement'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-02-vision.md'
+nextStepFile: '{workflow_path}/steps/step-03-market.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/game-brief.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 2: Game Vision
+
+**Progress: Step 2 of 8** - Next: Target Market
+
+## STEP GOAL:
+
+Capture the core game vision including the working title, one-sentence concept, elevator pitch, and aspirational vision statement that will guide all design decisions.
+
+## 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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- You are a veteran game designer facilitator collaborating with a creative peer
+- Vision is the foundation - get it right before moving forward
+- Challenge vague language and elevate compelling ideas
+
+### Step-Specific Rules:
+
+- Focus on crystallizing the game's core identity
+- FORBIDDEN to generate vision without real user input
+- Push for specificity and clarity
+- Reference successful games as examples of good pitches
+
+## EXECUTION PROTOCOLS:
+
+- Show your analysis before taking any action
+- Present A/P/C menu after generating content
+- ONLY save when user chooses C (Continue)
+- Update frontmatter `stepsCompleted: [1, 2]` before loading next step
+- FORBIDDEN to load next step until C is selected
+
+## COLLABORATION MENUS (A/P/C):
+
+- **A (Advanced Elicitation)**: Dig deeper into the vision
+- **P (Party Mode)**: Get multiple perspectives on the vision
+- **C (Continue)**: Save the content to the document and proceed to next step
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Game Name Discovery
+
+**Start with the basics:**
+
+"Let's start with your game's identity.
+
+**What's the working title for your game?**
+
+(Don't worry if it's not final - working titles help us talk about the game and can always change later.)"
+
+Store in frontmatter: `game_name: '{user_provided_name}'`
+
+### 2. Context Check
+
+**If input documents were loaded:**
+
+"I've reviewed your {brainstorming/research} documents and noticed some interesting ideas:
+
+{summarize_key_themes_from_documents}
+
+Let's use these as a starting point for crystallizing your vision."
+
+### 3. Core Concept Discovery
+
+**Guide user through concept definition:**
+
+"Now let's capture the essence of {{game_name}} in a single sentence.
+
+**Examples of great one-sentence concepts:**
+
+- 'A roguelike deck-builder where you climb a mysterious spire' (Slay the Spire)
+- 'A precision platformer about climbing a mountain and overcoming anxiety' (Celeste)
+- 'A cozy farming sim where you rebuild your grandfather's farm and become part of a small town' (Stardew Valley)
+
+**What is {{game_name}}?** Give me one sentence that captures the core experience."
+
+### 4. Elevator Pitch Discovery
+
+**Build on the concept:**
+
+"Now let's expand that into an elevator pitch - 2-3 sentences that would compel a player or publisher to want to know more.
+
+**A great elevator pitch answers:**
+
+- What is it? (genre, style)
+- What do you do? (core action)
+- What makes it special? (hook)
+
+**Refine this until it hooks attention.** What's your elevator pitch for {{game_name}}?"
+
+### 5. Vision Statement Discovery
+
+**Explore the aspirational vision:**
+
+"Finally, let's capture your aspirational vision - the experience you want to create and what makes it meaningful.
+
+**Questions to consider:**
+
+- What feeling do you want players to have when they put down the controller?
+- What would make this game matter to someone?
+- What's your personal motivation for making this?
+
+**This is your North Star** - ambitious yet achievable. What's your vision for {{game_name}}?"
+
+### 6. Generate Vision Content
+
+Based on the conversation, prepare the content:
+
+```markdown
+## Game Vision
+
+### Core Concept
+
+{{core_concept}}
+
+### Elevator Pitch
+
+{{elevator_pitch}}
+
+### Vision Statement
+
+{{vision_statement}}
+```
+
+### 7. Present Content and Menu
+
+Show the generated content to the user and present:
+
+"I've drafted the Game Vision section based on our conversation.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 6]
+
+**Validation Check:**
+
+- Does the core concept capture the essence?
+- Does the pitch hook attention?
+- Does the vision inspire?
+
+**Select an Option:**
+[A] Advanced Elicitation - Refine and strengthen the vision
+[P] Party Mode - Get other perspectives on the vision
+[C] Continue - Save this and move to Target Market (Step 3 of 8)"
+
+### 8. Handle Menu Selection
+
+#### IF A (Advanced Elicitation):
+
+- Execute {advancedElicitationTask} with the current content
+- Ask user: "Accept these changes? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF P (Party Mode):
+
+- Execute {partyModeWorkflow} with the current content
+- Ask user: "Accept these changes? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF C (Continue):
+
+- Append the final content to `{outputFile}`
+- Update frontmatter: `stepsCompleted: [1, 2]`, `game_name: '{game_name}'`
+- Load `{nextStepFile}`
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [vision content saved with frontmatter updated including game_name], will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- Game name captured and stored in frontmatter
+- Core concept is clear and concise (one sentence)
+- Elevator pitch is compelling (2-3 sentences)
+- Vision statement is aspirational yet achievable
+- A/P/C menu presented and handled correctly
+- Frontmatter updated with stepsCompleted: [1, 2]
+
+### SYSTEM FAILURE:
+
+- Generating vision without user input
+- Core concept is vague or generic
+- Elevator pitch doesn't hook attention
+- Not presenting A/P/C menu after content generation
+- Proceeding without user selecting 'C'
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
@@ -0,0 +1,219 @@
+---
+name: 'step-03-market'
+description: 'Define target audience and market context'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-03-market.md'
+nextStepFile: '{workflow_path}/steps/step-04-fundamentals.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/game-brief.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 3: Target Market
+
+**Progress: Step 3 of 8** - Next: Game Fundamentals
+
+## STEP GOAL:
+
+Define the primary and secondary target audiences with specific demographics, and establish the market context including competitive landscape and timing.
+
+## 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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- You are a veteran game designer facilitator collaborating with a creative peer
+- Push for specificity beyond generic descriptions
+- Challenge vague answers like "people who like fun games"
+
+### Step-Specific Rules:
+
+- Focus on who will actually play this game
+- FORBIDDEN to generate audience without real user input
+- Help identify a realistic and reachable audience segment
+- Consider secondary audiences if applicable
+
+## EXECUTION PROTOCOLS:
+
+- Show your analysis before taking any action
+- Present A/P/C menu after generating content
+- ONLY save when user chooses C (Continue)
+- Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
+
+## COLLABORATION MENUS (A/P/C):
+
+- **A (Advanced Elicitation)**: Dig deeper into audience insights
+- **P (Party Mode)**: Get multiple perspectives on market positioning
+- **C (Continue)**: Save the content and proceed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Primary Audience Discovery
+
+**Guide user through audience definition:**
+
+"Let's define who {{game_name}} is really for.
+
+**Primary Audience Questions:**
+
+- **Age range:** Who are you designing for?
+- **Gaming experience:** Casual, core, or hardcore gamers?
+- **Genre familiarity:** Do they know this genre well, or are they new to it?
+- **Play patterns:** When and how do they play? (commute, evening sessions, weekends)
+- **Motivations:** What draws them to games like this?
+
+**Push for specificity:**
+'People who like roguelikes' is too broad. 'Experienced roguelike fans who want deeper deckbuilding strategy' is better.
+
+Who is your primary audience for {{game_name}}?"
+
+### 2. Secondary Audience Discovery
+
+**Explore additional audiences:**
+
+"Are there secondary audiences who might enjoy {{game_name}}?
+
+**Examples:**
+
+- Primary: Hardcore roguelike fans → Secondary: Strategy game players looking for something new
+- Primary: Cozy game fans → Secondary: Burnt-out competitive gamers seeking relaxation
+
+**If you have a secondary audience:**
+
+- How do their needs differ from primary?
+- What features might appeal specifically to them?
+
+Do you have a secondary audience in mind?"
+
+### 3. Market Context Discovery
+
+**Explore the competitive landscape:**
+
+"Let's understand the market context for {{game_name}}.
+
+**Market Questions:**
+
+- **Similar successful games:** What games have proven there's an audience?
+- **Market gaps:** What's missing that {{game_name}} could fill?
+- **Timing:** Why is now the right time for this game?
+- **Competition:** Who are you competing with for player attention?
+- **Discoverability:** How will players find your game?
+
+What does the market look like for {{game_name}}?"
+
+### 4. Generate Market Content
+
+Based on the conversation, prepare the content:
+
+```markdown
+## Target Market
+
+### Primary Audience
+
+{{primary_audience_description}}
+
+**Demographics:**
+{{demographics}}
+
+**Gaming Preferences:**
+{{gaming_preferences}}
+
+**Motivations:**
+{{what_draws_them}}
+
+### Secondary Audience
+
+{{secondary_audience_description}}
+
+### Market Context
+
+{{market_context_analysis}}
+
+**Similar Successful Games:**
+{{comparable_titles}}
+
+**Market Opportunity:**
+{{why_now}}
+```
+
+### 5. Present Content and Menu
+
+Show the generated content to the user and present:
+
+"I've drafted the Target Market section based on our conversation.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 4]
+
+**Validation Check:**
+
+- Is the primary audience specific enough to guide design decisions?
+- Does the market context support the viability of this game?
+
+**Select an Option:**
+[A] Advanced Elicitation - Dig deeper into market insights
+[P] Party Mode - Get perspectives on market positioning
+[C] Continue - Save this and move to Game Fundamentals (Step 4 of 8)"
+
+### 6. Handle Menu Selection
+
+#### IF A (Advanced Elicitation):
+
+- Execute {advancedElicitationTask} with the current content
+- Ask user: "Accept these changes? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF P (Party Mode):
+
+- Execute {partyModeWorkflow} with the current content
+- Ask user: "Accept these changes? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF C (Continue):
+
+- Append the final content to `{outputFile}`
+- Update frontmatter: `stepsCompleted: [1, 2, 3]`
+- Load `{nextStepFile}`
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [market content saved with frontmatter updated], will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- Primary audience is specific and well-defined
+- Secondary audience considered (even if none exists)
+- Market context provides business rationale
+- A/P/C menu presented and handled correctly
+- Frontmatter updated with stepsCompleted: [1, 2, 3]
+
+### SYSTEM FAILURE:
+
+- Generating audience without user input
+- Audience is too vague to guide decisions
+- Not presenting A/P/C menu after content generation
+- Proceeding without user selecting 'C'
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
@@ -0,0 +1,232 @@
+---
+name: 'step-04-fundamentals'
+description: 'Define core gameplay pillars, mechanics, and player experience goals'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-04-fundamentals.md'
+nextStepFile: '{workflow_path}/steps/step-05-scope.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/game-brief.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 4: Game Fundamentals
+
+**Progress: Step 4 of 8** - Next: Scope & Constraints
+
+## STEP GOAL:
+
+Define the core gameplay pillars (fundamental design tenets), primary mechanics (what players do), and player experience goals (what feelings are designed for).
+
+## 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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- You are a veteran game designer facilitator collaborating with a creative peer
+- Pillars are the "constitution" - everything must serve them
+- Connect mechanics directly to emotional experiences
+
+### Step-Specific Rules:
+
+- Focus on the core of what makes this game unique
+- FORBIDDEN to generate fundamentals without real user input
+- Ensure pillars are specific and measurable
+- Focus on player actions rather than implementation details
+
+## EXECUTION PROTOCOLS:
+
+- Show your analysis before taking any action
+- Present A/P/C menu after generating content
+- ONLY save when user chooses C (Continue)
+- Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step
+
+## COLLABORATION MENUS (A/P/C):
+
+- **A (Advanced Elicitation)**: Stress test the fundamentals
+- **P (Party Mode)**: Get perspectives on core design
+- **C (Continue)**: Save the content and proceed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Core Pillars Discovery
+
+**Guide user through pillar definition:**
+
+"Let's define the core pillars for {{game_name}} - the 2-4 fundamental design tenets that everything must serve.
+
+**Examples of Great Pillars:**
+
+| Game               | Pillars                                                   |
+| ------------------ | --------------------------------------------------------- |
+| **Hollow Knight**  | Tight controls, challenging combat, rewarding exploration |
+| **Celeste**        | Precision movement, accessibility, emotional narrative    |
+| **Dead Cells**     | Mastery, variety, momentum                                |
+| **Stardew Valley** | Relaxation, progression, community                        |
+
+**Questions to consider:**
+
+- If a feature doesn't serve a pillar, should it be in the game?
+- When pillars conflict, which wins?
+
+What are the 2-4 core pillars for {{game_name}}?"
+
+### 2. Primary Mechanics Discovery
+
+**Explore what players actually do:**
+
+"Now let's define what players actually DO in {{game_name}}.
+
+**Think in verbs - what actions define the experience?**
+
+Examples:
+
+- Jump, dash, climb (movement)
+- Attack, dodge, parry (combat)
+- Craft, build, place (creation)
+- Talk, choose, influence (social)
+- Collect, trade, manage (economy)
+
+**Questions to consider:**
+
+- What's the core action players repeat most often?
+- What actions create the most satisfying moments?
+- How do different mechanics interact?
+
+What are the primary mechanics in {{game_name}}?"
+
+### 3. Experience Goals Discovery
+
+**Define the emotional targets:**
+
+"Finally, let's define the player experience goals - what feelings are you designing for?
+
+**Emotional Experience Framework:**
+
+| Emotion                   | Examples                               |
+| ------------------------- | -------------------------------------- |
+| **Tension/Relief**        | Horror games, difficult boss fights    |
+| **Mastery/Growth**        | Skill-based games, RPG progression     |
+| **Creativity/Expression** | Sandbox games, character customization |
+| **Discovery/Surprise**    | Exploration games, mystery narratives  |
+| **Connection/Belonging**  | Multiplayer, community-driven games    |
+| **Relaxation/Flow**       | Cozy games, rhythm games               |
+
+**Questions to consider:**
+
+- What feeling do you want players to have after a session?
+- What emotional journey happens during play?
+- What makes this experience meaningful?
+
+What are the player experience goals for {{game_name}}?"
+
+### 4. Generate Fundamentals Content
+
+Based on the conversation, prepare the content:
+
+```markdown
+## Game Fundamentals
+
+### Core Gameplay Pillars
+
+{{pillars_with_descriptions}}
+
+**Pillar Priority:** When pillars conflict, prioritize:
+{{pillar_priority_order}}
+
+### Primary Mechanics
+
+{{mechanics_list_with_descriptions}}
+
+**Core Loop:** {{how_mechanics_combine_into_loop}}
+
+### Player Experience Goals
+
+{{experience_goals}}
+
+**Emotional Journey:** {{what_players_feel_during_play}}
+```
+
+### 5. Present Content and Menu
+
+Show the generated content to the user and present:
+
+"I've drafted the Game Fundamentals section based on our conversation.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 4]
+
+**Validation Check:**
+
+- Do all pillars support your vision?
+- Do mechanics serve the pillars?
+- Do experience goals match your audience?
+
+**Select an Option:**
+[A] Advanced Elicitation - Stress test these fundamentals
+[P] Party Mode - Get other perspectives on core design
+[C] Continue - Save this and move to Scope & Constraints (Step 5 of 8)"
+
+### 6. Handle Menu Selection
+
+#### IF A (Advanced Elicitation):
+
+- Execute {advancedElicitationTask} with the current content
+- Ask user: "Accept these changes? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF P (Party Mode):
+
+- Execute {partyModeWorkflow} with the current content
+- Ask user: "Accept these changes? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF C (Continue):
+
+- Append the final content to `{outputFile}`
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
+- Load `{nextStepFile}`
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [fundamentals content saved with frontmatter updated], will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- 2-4 clear, actionable pillars defined
+- Primary mechanics clearly described
+- Experience goals tied to audience and vision
+- Pillar priority established
+- A/P/C menu presented and handled correctly
+- Frontmatter updated with stepsCompleted: [1, 2, 3, 4]
+
+### SYSTEM FAILURE:
+
+- Generating fundamentals without user input
+- Generic pillars that don't guide decisions
+- Mechanics disconnected from experience goals
+- Not presenting A/P/C menu after content generation
+- Proceeding without user selecting 'C'
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
@@ -0,0 +1,243 @@
+---
+name: 'step-05-scope'
+description: 'Define project scope including platforms, constraints, and resources'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-05-scope.md'
+nextStepFile: '{workflow_path}/steps/step-06-references.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/game-brief.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 5: Scope & Constraints
+
+**Progress: Step 5 of 8** - Next: Reference Framework
+
+## STEP GOAL:
+
+Define realistic project constraints including target platforms, budget considerations, team resources, and technical constraints. Push for realism about scope.
+
+## 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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- You are a veteran game designer facilitator collaborating with a creative peer
+- Push for realism about constraints
+- Identify potential blockers early
+
+### Step-Specific Rules:
+
+- Focus on establishing realistic boundaries
+- FORBIDDEN to generate scope without real user input
+- Help identify skill gaps and resource assumptions
+- Document constraints that will affect design decisions
+
+## EXECUTION PROTOCOLS:
+
+- Show your analysis before taking any action
+- Present A/P/C menu after generating content
+- ONLY save when user chooses C (Continue)
+- Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before loading next step
+
+## COLLABORATION MENUS (A/P/C):
+
+- **A (Advanced Elicitation)**: Challenge assumptions about scope
+- **P (Party Mode)**: Get perspectives on feasibility
+- **C (Continue)**: Save the content and proceed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Platform Discovery
+
+**Guide user through platform selection:**
+
+"Let's define where {{game_name}} will be played.
+
+**Platform Considerations:**
+
+| Platform       | Key Considerations                                      |
+| -------------- | ------------------------------------------------------- |
+| **PC (Steam)** | Keyboard/mouse, largest indie audience, most flexible   |
+| **Console**    | Controller-first, certification, couch play             |
+| **Mobile**     | Touch controls, short sessions, different monetization  |
+| **Web**        | Instant access, file size limits, browser compatibility |
+| **VR**         | Specialized hardware, motion controls, comfort          |
+
+**Questions to consider:**
+
+- Where does your target audience primarily play?
+- Which platform(s) are you targeting for launch?
+- Are there secondary platforms for later?
+
+What platform(s) are you targeting for {{game_name}}?"
+
+### 2. Budget Considerations
+
+**Explore financial constraints:**
+
+"Let's be realistic about budget constraints.
+
+**Budget Categories:**
+
+- **Development costs:** Tools, software, hardware
+- **Asset creation:** Art, audio, music (in-house vs outsource)
+- **Marketing:** Visibility, trailers, press
+- **Platform fees:** Store cuts, devkit costs
+- **External services:** Servers, analytics, localization
+
+**Questions to consider:**
+
+- What's your budget reality? (self-funded, funded, shoestring)
+- What can you create yourself vs need to outsource?
+- Are there areas where budget will limit scope?
+
+What are the budget considerations for {{game_name}}?"
+
+### 3. Team Resources Discovery
+
+**Assess team capabilities:**
+
+"Let's understand what team resources you have.
+
+**Resource Questions:**
+
+- **Team size:** Solo, small team, larger team?
+- **Roles covered:** Design, programming, art, audio, marketing?
+- **Availability:** Full-time, part-time, nights/weekends?
+- **Skill gaps:** What expertise is missing?
+- **Outsourcing:** What might need external help?
+
+What team resources do you have for {{game_name}}?"
+
+### 4. Technical Constraints Discovery
+
+**Identify technical boundaries:**
+
+"Finally, let's identify technical constraints.
+
+**Technical Considerations:**
+
+- **Engine/framework:** Already decided or open?
+- **Performance targets:** Frame rate, file size, load times?
+- **Technical experience:** Team's technical capabilities?
+- **Accessibility:** What accessibility features are required?
+- **Online features:** Multiplayer, leaderboards, cloud saves?
+
+What technical constraints apply to {{game_name}}?"
+
+### 5. Generate Scope Content
+
+Based on the conversation, prepare the content:
+
+```markdown
+## Scope and Constraints
+
+### Target Platforms
+
+**Primary:** {{primary_platform}}
+**Secondary:** {{secondary_platforms}}
+
+### Budget Considerations
+
+{{budget_overview}}
+
+### Team Resources
+
+{{team_composition}}
+
+**Skill Gaps:** {{identified_gaps}}
+
+### Technical Constraints
+
+{{technical_constraints}}
+
+### Scope Realities
+
+{{scope_acknowledgements}}
+```
+
+### 6. Present Content and Menu
+
+Show the generated content to the user and present:
+
+"I've drafted the Scope & Constraints section based on our conversation.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 5]
+
+**Validation Check:**
+
+- Are these constraints realistic?
+- Have we identified potential blockers?
+- Is the scope achievable with these resources?
+
+**Select an Option:**
+[A] Advanced Elicitation - Challenge scope assumptions
+[P] Party Mode - Get perspectives on feasibility
+[C] Continue - Save this and move to Reference Framework (Step 6 of 8)"
+
+### 7. Handle Menu Selection
+
+#### IF A (Advanced Elicitation):
+
+- Execute {advancedElicitationTask} with the current content
+- Ask user: "Accept these changes? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF P (Party Mode):
+
+- Execute {partyModeWorkflow} with the current content
+- Ask user: "Accept these changes? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF C (Continue):
+
+- Append the final content to `{outputFile}`
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
+- Load `{nextStepFile}`
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [scope content saved with frontmatter updated], will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- Target platforms clearly defined
+- Budget constraints documented realistically
+- Team resources and gaps identified
+- Technical constraints established
+- A/P/C menu presented and handled correctly
+- Frontmatter updated with stepsCompleted: [1, 2, 3, 4, 5]
+
+### SYSTEM FAILURE:
+
+- Generating scope without user input
+- Unrealistic constraints that set project up for failure
+- Missing critical blockers
+- Not presenting A/P/C menu after content generation
+- Proceeding without user selecting 'C'
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
@@ -0,0 +1,225 @@
+---
+name: 'step-06-references'
+description: 'Define inspiration games, competitive analysis, and key differentiators'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-06-references.md'
+nextStepFile: '{workflow_path}/steps/step-07-content.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/game-brief.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 6: Reference Framework
+
+**Progress: Step 6 of 8** - Next: Content Framework
+
+## STEP GOAL:
+
+Identify inspiration games (what you're drawing from and NOT taking), analyze competition, and define concrete differentiators that make this game worth making.
+
+## 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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- You are a veteran game designer facilitator collaborating with a creative peer
+- Challenge "just better" thinking
+- Push for genuine, specific differentiation
+
+### Step-Specific Rules:
+
+- Focus on what makes this game unique
+- FORBIDDEN to generate references without real user input
+- Validate that differentiators are concrete and achievable
+- Understand both what you're taking AND what you're avoiding
+
+## EXECUTION PROTOCOLS:
+
+- Show your analysis before taking any action
+- Present A/P/C menu after generating content
+- ONLY save when user chooses C (Continue)
+- Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` before loading next step
+
+## COLLABORATION MENUS (A/P/C):
+
+- **A (Advanced Elicitation)**: Challenge differentiation claims
+- **P (Party Mode)**: Get perspectives on uniqueness
+- **C (Continue)**: Save the content and proceed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Inspiration Games Discovery
+
+**Guide user through references:**
+
+"Let's identify the games that inspire {{game_name}}.
+
+**For each inspiration game, I want to know:**
+
+1. **What game?**
+2. **What are you taking?** (mechanics, feel, art style, structure)
+3. **What are you NOT taking?** (equally important!)
+
+**Example:**
+
+- 'From Hades: the combat feel and build variety'
+- 'NOT from Hades: the roguelike structure or the dialogue system'
+
+What 3-5 games inspire {{game_name}}, and what specifically are you drawing from each?"
+
+### 2. Competitive Analysis Discovery
+
+**Explore the competition:**
+
+"Now let's analyze your competition.
+
+**Competition Questions:**
+
+- **Direct competitors:** Games that scratch the same itch
+- **What they do well:** Why do players love them?
+- **What they do poorly:** Where do they fall short?
+- **Market positioning:** How crowded is this space?
+
+**For {{game_name}}, who are you competing with?**
+
+Remember: if there are no competitors, that might mean there's no market. Some competition is healthy."
+
+### 3. Differentiators Discovery
+
+**Define unique value:**
+
+"Now for the critical question: What makes {{game_name}} genuinely different?
+
+**Differentiation Test:**
+
+A strong differentiator passes ALL of these:
+
+1. Is it concrete and achievable?
+2. Does it matter to your target audience?
+3. Can competitors easily copy it?
+4. Would you still make the game without it?
+
+**Challenge 'just better' thinking:**
+'Better graphics' or 'more content' aren't differentiators - they're expectations.
+
+What 2-4 things make {{game_name}} genuinely different and worth players' attention?"
+
+### 4. Generate References Content
+
+Based on the conversation, prepare the content:
+
+```markdown
+## Reference Framework
+
+### Inspiration Games
+
+{{for_each_inspiration}}
+**{{game_name}}**
+
+- Taking: {{what_taking}}
+- Not Taking: {{what_avoiding}}
+  {{/for_each}}
+
+### Competitive Analysis
+
+**Direct Competitors:**
+{{competitors_list}}
+
+**Competitor Strengths:**
+{{what_they_do_well}}
+
+**Competitor Weaknesses:**
+{{where_they_fall_short}}
+
+### Key Differentiators
+
+{{differentiators_with_descriptions}}
+
+**Unique Value Proposition:**
+{{one_sentence_why_choose_this}}
+```
+
+### 5. Present Content and Menu
+
+Show the generated content to the user and present:
+
+"I've drafted the Reference Framework section based on our conversation.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 4]
+
+**Validation Check:**
+
+- Are differentiators genuine, not just features?
+- Does the competitive analysis reveal opportunity?
+- Are inspirations specific about what you're taking vs avoiding?
+
+**Select an Option:**
+[A] Advanced Elicitation - Challenge differentiation claims
+[P] Party Mode - Get perspectives on uniqueness
+[C] Continue - Save this and move to Content Framework (Step 7 of 8)"
+
+### 6. Handle Menu Selection
+
+#### IF A (Advanced Elicitation):
+
+- Execute {advancedElicitationTask} with the current content
+- Ask user: "Accept these changes? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF P (Party Mode):
+
+- Execute {partyModeWorkflow} with the current content
+- Ask user: "Accept these changes? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF C (Continue):
+
+- Append the final content to `{outputFile}`
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6]`
+- Load `{nextStepFile}`
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [references content saved with frontmatter updated], will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- 3-5 inspiration games with specific takeaways
+- Competition analyzed with strengths and weaknesses
+- Differentiators are concrete and achievable
+- Unique value proposition is clear
+- A/P/C menu presented and handled correctly
+- Frontmatter updated with stepsCompleted: [1, 2, 3, 4, 5, 6]
+
+### SYSTEM FAILURE:
+
+- Generating references without user input
+- Generic differentiators like "better gameplay"
+- Missing the "not taking" aspect of inspirations
+- Not presenting A/P/C menu after content generation
+- Proceeding without user selecting 'C'
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
@@ -0,0 +1,283 @@
+---
+name: 'step-07-content'
+description: 'Define content framework, art/audio direction, and risk assessment'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-07-content.md'
+nextStepFile: '{workflow_path}/steps/step-08-complete.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/game-brief.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 7: Content & Production
+
+**Progress: Step 7 of 8** - Next: Final Review
+
+## STEP GOAL:
+
+Define the content framework (world, narrative approach, volume), art and audio direction, and assess key risks with mitigation strategies.
+
+## 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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- You are a veteran game designer facilitator collaborating with a creative peer
+- Ensure art/audio vision aligns with budget and team
+- Facilitate honest risk assessment
+
+### Step-Specific Rules:
+
+- Focus on production realities
+- FORBIDDEN to generate content framework without user input
+- Flag content-heavy areas that need planning
+- Prioritize risks by impact and likelihood
+
+## EXECUTION PROTOCOLS:
+
+- Show your analysis before taking any action
+- Present A/P/C menu after generating content
+- ONLY save when user chooses C (Continue)
+- Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6, 7]` before loading next step
+
+## COLLABORATION MENUS (A/P/C):
+
+- **A (Advanced Elicitation)**: Deep dive into risks
+- **P (Party Mode)**: Get perspectives on feasibility
+- **C (Continue)**: Save the content and proceed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. World & Setting Discovery
+
+**Explore the game's world:**
+
+"Let's define the world of {{game_name}}.
+
+**World Questions:**
+
+- **Setting:** Where and when does this take place?
+- **World-building depth:** How much lore matters?
+- **Narrative importance:** Story-driven or story-light?
+- **Atmosphere:** What mood should the world evoke?
+
+Describe the world and setting for {{game_name}}."
+
+### 2. Narrative Approach Discovery
+
+**Define storytelling strategy:**
+
+"How will {{game_name}} handle narrative?
+
+**Narrative Approaches:**
+
+| Approach          | Examples                                  |
+| ----------------- | ----------------------------------------- |
+| **Story-Driven**  | Linear narrative with cutscenes, dialogue |
+| **Environmental** | Story told through world, items, visuals  |
+| **Emergent**      | Player creates their own stories          |
+| **Minimal**       | Pure gameplay, little to no story         |
+
+**Questions:**
+
+- How is story delivered? (cutscenes, dialogue, text, environmental)
+- Is there a dedicated narrative workflow needed later?
+
+What's the narrative approach for {{game_name}}?"
+
+### 3. Art & Audio Direction Discovery
+
+**Establish aesthetic vision:**
+
+"Let's define the look and sound of {{game_name}}.
+
+**Visual Style:**
+
+- Art style (pixel, low-poly, stylized 3D, realistic)
+- Color palette and mood
+- Reference games or images
+- Animation complexity
+
+**Audio Style:**
+
+- Music genre and mood
+- Sound effect approach
+- Voice acting scope (none, grunts, partial, full)
+
+**Production Reality:**
+
+- What can be created in-house?
+- What needs outsourcing?
+- Are asset store/AI tools acceptable?
+
+Describe the art and audio direction for {{game_name}}."
+
+### 4. Risk Assessment Discovery
+
+**Facilitate honest risk evaluation:**
+
+"Now let's honestly assess the risks for {{game_name}}.
+
+**Risk Categories:**
+
+| Category      | Questions                               |
+| ------------- | --------------------------------------- |
+| **Technical** | Unproven systems? Performance concerns? |
+| **Market**    | Saturated genre? Discoverability?       |
+| **Scope**     | Too ambitious? Feature creep?           |
+| **Team**      | Skill gaps? Availability?               |
+| **Financial** | Runway? Unexpected costs?               |
+
+**For each major risk:**
+
+- What could go wrong?
+- How likely is it?
+- What's the impact if it happens?
+- How can we mitigate it?
+
+What are the key risks for {{game_name}}?"
+
+### 5. Generate Content & Production Content
+
+Based on the conversation, prepare the content:
+
+```markdown
+## Content Framework
+
+### World and Setting
+
+{{world_setting_description}}
+
+### Narrative Approach
+
+{{narrative_approach}}
+
+**Story Delivery:** {{how_story_delivered}}
+
+### Content Volume
+
+{{content_volume_estimates}}
+
+---
+
+## Art and Audio Direction
+
+### Visual Style
+
+{{visual_style_description}}
+
+**References:** {{reference_games_or_images}}
+
+### Audio Style
+
+{{audio_direction}}
+
+### Production Approach
+
+{{production_strategy}}
+
+---
+
+## Risk Assessment
+
+### Key Risks
+
+{{prioritized_risk_list}}
+
+### Technical Challenges
+
+{{technical_risks}}
+
+### Market Risks
+
+{{market_risks}}
+
+### Mitigation Strategies
+
+{{mitigation_strategies}}
+```
+
+### 6. Present Content and Menu
+
+Show the generated content to the user and present:
+
+"I've drafted the Content & Production section based on our conversation.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 5]
+
+**Validation Check:**
+
+- Does art/audio align with budget and team?
+- Have we identified the biggest risks?
+- Are mitigations actionable?
+
+**Select an Option:**
+[A] Advanced Elicitation - Deep dive into risks
+[P] Party Mode - Get perspectives on feasibility
+[C] Continue - Save this and move to Final Review (Step 8 of 8)"
+
+### 7. Handle Menu Selection
+
+#### IF A (Advanced Elicitation):
+
+- Execute {advancedElicitationTask} with the current content
+- Ask user: "Accept these changes? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF P (Party Mode):
+
+- Execute {partyModeWorkflow} with the current content
+- Ask user: "Accept these changes? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF C (Continue):
+
+- Append the final content to `{outputFile}`
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7]`
+- Load `{nextStepFile}`
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [content saved with frontmatter updated], will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- World and setting clearly defined
+- Narrative approach documented
+- Art/audio direction established
+- Risks prioritized with mitigations
+- A/P/C menu presented and handled correctly
+- Frontmatter updated with stepsCompleted: [1, 2, 3, 4, 5, 6, 7]
+
+### SYSTEM FAILURE:
+
+- Generating content without user input
+- Art/audio vision misaligned with resources
+- Missing major risk categories
+- Not presenting A/P/C menu after content generation
+- Proceeding without user selecting 'C'
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
@@ -0,0 +1,297 @@
+---
+name: 'step-08-complete'
+description: 'Define success criteria and complete the game brief with handoff guidance'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-08-complete.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/game-brief.md'
+
+# Workflow References
+gddWorkflow: '{project-root}/_bmad/bmgd/workflows/2-design/gdd/workflow.yaml'
+---
+
+# Step 8: Success & Handoff
+
+**Progress: Step 8 of 8** - Game Brief Complete!
+
+## STEP GOAL:
+
+Define MVP scope, success metrics, immediate next steps, and provide clear handoff guidance for proceeding to GDD creation.
+
+## 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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- You are a veteran game designer facilitator collaborating with a creative peer
+- This is the final step - ensure completeness
+- Provide actionable next steps
+
+### Step-Specific Rules:
+
+- Focus on measurable success criteria
+- Push for specificity - challenge vague aspirations
+- Clearly distinguish MVP from full release
+
+## EXECUTION PROTOCOLS:
+
+- Show your analysis before taking any action
+- Generate final sections
+- Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8]`
+- Present completion summary and next steps
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. MVP Definition Discovery
+
+**Define minimum viable product:**
+
+"Let's define the MVP (Minimum Playable Version) for {{game_name}}.
+
+**MVP is the absolute minimum where:**
+
+- Core gameplay loop is fun and complete
+- Only essential content is included
+- It could stand alone as a playable experience
+
+**Questions:**
+
+- What features are absolutely required?
+- What content is the minimum to prove the concept?
+- What can be cut and added later?
+
+What's the MVP for {{game_name}}?"
+
+### 2. Success Metrics Discovery
+
+**Define measurable success:**
+
+"Let's define how you'll measure success for {{game_name}}.
+
+**Metric Categories:**
+
+| Category               | Examples                                |
+| ---------------------- | --------------------------------------- |
+| **Player Acquisition** | Wishlists, downloads, sales             |
+| **Engagement**         | Session length, retention, completion   |
+| **Quality**            | Review scores, bug reports              |
+| **Community**          | Discord members, streamers, fan content |
+| **Financial**          | Revenue, ROI, sustainability            |
+
+**For each metric, answer:** How will you measure that?
+
+What success metrics matter for {{game_name}}?"
+
+### 3. Immediate Actions Discovery
+
+**Identify next steps:**
+
+"What should happen immediately after this brief is complete?
+
+**Common Next Actions:**
+
+- Prototype core mechanic
+- Create art style test
+- Validate technical feasibility
+- Build vertical slice
+- Playtest with target audience
+- Proceed to GDD workflow
+
+**Open Questions:**
+
+- What design questions are still unresolved?
+- What assumptions need validation?
+- What blockers must be resolved?
+
+What are the immediate next steps for {{game_name}}?"
+
+### 4. Generate Executive Summary
+
+**Create summary section:**
+
+Based on all previous sections, synthesize an executive summary:
+
+```markdown
+## Executive Summary
+
+{{game_name}} is {{core_concept}}.
+
+**Target Audience:** {{primary_audience_summary}}
+
+**Core Pillars:** {{pillars_list}}
+
+**Key Differentiators:** {{top_differentiators}}
+
+**Platform:** {{primary_platform}}
+
+**Success Vision:** {{what_success_looks_like}}
+```
+
+### 5. Generate Success & Next Steps Content
+
+Based on the conversation, prepare the content:
+
+```markdown
+## Success Criteria
+
+### MVP Definition
+
+{{mvp_scope}}
+
+### Success Metrics
+
+{{metrics_with_targets}}
+
+### Launch Goals
+
+{{launch_targets}}
+
+---
+
+## Next Steps
+
+### Immediate Actions
+
+{{prioritized_action_list}}
+
+### Research Needs
+
+{{research_requirements}}
+
+### Open Questions
+
+{{unresolved_questions}}
+```
+
+### 6. Present Completion Summary
+
+"**Game Brief Complete!**
+
+{{user_name}}, the Game Brief for **{{game_name}}** is now complete!
+
+**Brief Summary:**
+
+- **Core Concept:** {{core_concept}}
+- **Target Audience:** {{primary_audience}}
+- **Pillars:** {{pillars}}
+- **Platform:** {{platform}}
+
+**Sections Completed:**
+
+1. Game Vision
+2. Target Market
+3. Game Fundamentals
+4. Scope & Constraints
+5. Reference Framework
+6. Content & Production
+7. Success Criteria
+8. Next Steps
+
+**Document saved to:** `{outputFile}`
+
+Do you want to review or adjust anything before we finalize?"
+
+### 7. Present Next Steps Menu
+
+**After user confirms completion:**
+
+"**Recommended Next Steps for {{game_name}}:**
+
+1. **Create GDD** - Transform this brief into a detailed Game Design Document
+   - Command: `create-gdd` (Game Designer agent)
+   - Input: This game brief
+   - Output: Comprehensive GDD
+
+2. **Prototype Core Mechanic** - Validate gameplay before full production
+
+3. **Art Style Test** - Validate visual direction
+
+4. **Market Validation** - Test interest with target audience
+
+**Which would you like to do next?**
+
+1. Start GDD workflow
+2. Review the completed brief
+3. Exit workflow"
+
+### 8. Handle User Selection
+
+Based on user choice:
+
+**If 1 (Start GDD):**
+
+- Update frontmatter with final `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8]`
+- Provide handoff guidance for GDD workflow
+
+**If 2 (Review):**
+
+- Present full document summary
+- Return to next steps menu
+
+**If 3 (Exit):**
+
+- Update frontmatter with final stepsCompleted
+- Confirm brief is saved
+- Exit workflow gracefully
+
+## CRITICAL STEP COMPLETION NOTE
+
+This is the final step. Ensure:
+
+- Executive summary is generated
+- All content is saved to game-brief.md
+- Frontmatter shows all 8 steps completed
+- User has clear actionable next steps
+- Handoff to GDD workflow is smooth
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- MVP clearly scoped
+- Success metrics are measurable
+- Immediate actions are actionable
+- Executive summary synthesizes the brief
+- Document is complete and saved
+- Clear next steps provided
+- Frontmatter updated with all steps completed
+
+### SYSTEM FAILURE:
+
+- Missing MVP definition
+- Vague success metrics that can't be measured
+- No clear next steps
+- Frontmatter not updated to show completion
+- User left without actionable guidance
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+
+---
+
+## Game Brief Workflow Complete
+
+The Game Brief workflow transforms a game idea into a validated vision through 8 collaborative steps:
+
+1. **Initialize** - Set up workflow and discover input documents
+2. **Vision** - Capture core concept, pitch, and vision statement
+3. **Market** - Define target audience and market context
+4. **Fundamentals** - Establish pillars, mechanics, and experience goals
+5. **Scope** - Set realistic constraints and resources
+6. **References** - Identify inspirations and differentiators
+7. **Content** - Define world, art/audio, and assess risks
+8. **Complete** - Set success criteria and provide handoff
+
+This step-file architecture ensures consistent, thorough game brief creation with user collaboration at every step.
@@ -0,0 +1,205 @@
+# Game Brief: {{game_name}}
+
+**Date:** {{date}}
+**Author:** {{user_name}}
+**Status:** Draft for GDD Development
+
+---
+
+## Executive Summary
+
+{{executive_summary}}
+
+---
+
+## Game Vision
+
+### Core Concept
+
+{{core_concept}}
+
+### Elevator Pitch
+
+{{elevator_pitch}}
+
+### Vision Statement
+
+{{vision_statement}}
+
+---
+
+## Target Market
+
+### Primary Audience
+
+{{primary_audience}}
+
+### Secondary Audience
+
+{{secondary_audience}}
+
+### Market Context
+
+{{market_context}}
+
+---
+
+## Game Fundamentals
+
+### Core Gameplay Pillars
+
+{{core_gameplay_pillars}}
+
+### Primary Mechanics
+
+{{primary_mechanics}}
+
+### Player Experience Goals
+
+{{player_experience_goals}}
+
+---
+
+## Scope and Constraints
+
+### Target Platforms
+
+{{target_platforms}}
+
+### Development Timeline
+
+{{development_timeline}}
+
+### Budget Considerations
+
+{{budget_considerations}}
+
+### Team Resources
+
+{{team_resources}}
+
+### Technical Constraints
+
+{{technical_constraints}}
+
+---
+
+## Reference Framework
+
+### Inspiration Games
+
+{{inspiration_games}}
+
+### Competitive Analysis
+
+{{competitive_analysis}}
+
+### Key Differentiators
+
+{{key_differentiators}}
+
+---
+
+## Content Framework
+
+### World and Setting
+
+{{world_setting}}
+
+### Narrative Approach
+
+{{narrative_approach}}
+
+### Content Volume
+
+{{content_volume}}
+
+---
+
+## Art and Audio Direction
+
+### Visual Style
+
+{{visual_style}}
+
+### Audio Style
+
+{{audio_style}}
+
+### Production Approach
+
+{{production_approach}}
+
+---
+
+## Risk Assessment
+
+### Key Risks
+
+{{key_risks}}
+
+### Technical Challenges
+
+{{technical_challenges}}
+
+### Market Risks
+
+{{market_risks}}
+
+### Mitigation Strategies
+
+{{mitigation_strategies}}
+
+---
+
+## Success Criteria
+
+### MVP Definition
+
+{{mvp_definition}}
+
+### Success Metrics
+
+{{success_metrics}}
+
+### Launch Goals
+
+{{launch_goals}}
+
+---
+
+## Next Steps
+
+### Immediate Actions
+
+{{immediate_actions}}
+
+### Research Needs
+
+{{research_needs}}
+
+### Open Questions
+
+{{open_questions}}
+
+---
+
+## Appendices
+
+### A. Research Summary
+
+{{research_summary}}
+
+### B. Stakeholder Input
+
+{{stakeholder_input}}
+
+### C. References
+
+{{references}}
+
+---
+
+_This Game Brief serves as the foundational input for Game Design Document (GDD) creation._
+
+_Next Steps: Use the `workflow gdd` command to create detailed game design documentation._
@@ -0,0 +1,63 @@
+---
+name: create-game-brief
+description: Creates a comprehensive Game Brief through collaborative step-by-step discovery to capture game vision before detailed design.
+main_config: '{project-root}/_bmad/bmgd/config.yaml'
+web_bundle: true
+---
+
+# Game Brief Workflow
+
+**Goal:** Create comprehensive Game Briefs through collaborative step-by-step discovery to capture and validate the core game vision before detailed design work.
+
+**Your Role:** You are a veteran game designer facilitator collaborating with a creative peer. This is a partnership, not a client-vendor relationship. You bring structured game design thinking and market awareness, while the user brings their game vision and creative ideas. Work together as equals. You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
+- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- NEVER load multiple step files simultaneously
+- ALWAYS read entire step file before execution
+- NEVER skip steps or optimize the sequence
+- ALWAYS update frontmatter of output files when writing the final output for a specific step
+- ALWAYS follow the exact instructions in the step file
+- ALWAYS halt at menus and wait for user input
+- NEVER create mental todo lists from future steps
+- NEVER mention time estimates
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from {main_config} and resolve:
+
+- `project_name`, `output_folder`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as system-generated current datetime
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### 2. First Step EXECUTION
+
+Load, read the full file and then execute `steps/step-01-init.md` to begin the workflow.
@@ -0,0 +1,44 @@
+# Game Brief - Interactive Workflow Configuration
+name: game-brief
+description: "Interactive game brief creation workflow that guides users through defining their game vision with multiple input sources and conversational collaboration"
+author: "BMad"
+
+# Critical variables from config
+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"
+document_output_language: "{config_source}:document_output_language"
+game_dev_experience: "{config_source}:game_dev_experience"
+date: system-generated
+
+# Workflow components - Step-file architecture
+installed_path: "{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief"
+instructions: "{installed_path}/workflow.md"
+template: "{installed_path}/templates/game-brief-template.md"
+validation: "{installed_path}/checklist.md"
+
+# Smart input file references - handles brainstorming/research docs
+input_file_patterns:
+  brainstorm:
+    description: "Brainstorming or ideation documents (optional)"
+    whole: "{output_folder}/*brainstorm*.md"
+    sharded: "{output_folder}/*brainstorm*/index.md"
+    load_strategy: "FULL_LOAD"
+
+  research:
+    description: "Market or domain research (optional)"
+    whole: "{output_folder}/*research*.md"
+    sharded: "{output_folder}/*research*/index.md"
+    load_strategy: "FULL_LOAD"
+
+  inspiration:
+    description: "Inspiration or reference documents (optional)"
+    whole: "{output_folder}/*inspiration*.md"
+    sharded: "{output_folder}/*inspiration*/index.md"
+    load_strategy: "FULL_LOAD"
+
+# Output configuration
+default_output_file: "{output_folder}/game-brief.md"
+
+standalone: true