bmad-method 5.1.3 → 6.0.0-alpha.1

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

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

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

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

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

@@ -0,0 +1,41 @@
+# Brainstorm Game Workflow Configuration
+name: "brainstorm-game"
+description: "Facilitate game brainstorming sessions by orchestrating the CIS brainstorming workflow with game-specific context, guidance, and additional game design techniques."
+author: "BMad"
+
+# Critical variables from config
+config_source: "{project-root}/bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+user_skill_level: "{config_source}:user_skill_level"
+date: system-generated
+
+# Module path and component files
+installed_path: "{project-root}/bmad/bmm/workflows/1-analysis/brainstorm-game"
+template: false
+instructions: "{installed_path}/instructions.md"
+
+# Context and techniques for game brainstorming
+game_context: "{installed_path}/game-context.md"
+game_brain_methods: "{installed_path}/game-brain-methods.csv"
+
+# CORE brainstorming workflow to invoke
+core_brainstorming: "{project-root}/bmad/core/workflows/brainstorming/workflow.yaml"
+
+standalone: true
+
+web_bundle:
+  name: "brainstorm-game"
+  description: "Facilitate game brainstorming sessions by orchestrating the CIS brainstorming workflow with game-specific context, guidance, and additional game design techniques."
+  author: "BMad"
+  instructions: "bmad/bmm/workflows/1-analysis/brainstorm-game/instructions.md"
+  template: false
+  web_bundle_files:
+    - "bmad/bmm/workflows/1-analysis/brainstorm-game/instructions.md"
+    - "bmad/bmm/workflows/1-analysis/brainstorm-game/game-context.md"
+    - "bmad/bmm/workflows/1-analysis/brainstorm-game/game-brain-methods.csv"
+    - "bmad/core/workflows/brainstorming/workflow.yaml"
+  existing_workflows:
+    - core_brainstorming: "bmad/core/workflows/brainstorming/workflow.yaml"

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

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

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

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

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

@@ -0,0 +1,25 @@
+# Project Brainstorming Context
+
+This context guide provides project-specific considerations for brainstorming sessions focused on software and product development.
+
+## Session Focus Areas
+
+When brainstorming for projects, consider exploring:
+
+- **User Problems and Pain Points** - What challenges do users face?
+- **Feature Ideas and Capabilities** - What could the product do?
+- **Technical Approaches** - How might we build it?
+- **User Experience** - How will users interact with it?
+- **Business Model and Value** - How does it create value?
+- **Market Differentiation** - What makes it unique?
+- **Technical Risks and Challenges** - What could go wrong?
+- **Success Metrics** - How will we measure success?
+
+## Integration with Project Workflow
+
+Brainstorming sessions typically feed into:
+
+- **Product Briefs** - Initial product vision and strategy
+- **PRDs** - Detailed requirements documents
+- **Technical Specifications** - Architecture and implementation plans
+- **Research Activities** - Areas requiring further investigation

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

@@ -0,0 +1,39 @@
+# Brainstorm Project Workflow Configuration
+name: "brainstorm-project"
+description: "Facilitate project brainstorming sessions by orchestrating the CIS brainstorming workflow with project-specific context and guidance."
+author: "BMad"
+
+# Critical variables from config
+config_source: "{project-root}/bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+user_skill_level: "{config_source}:user_skill_level"
+date: system-generated
+
+# Module path and component files
+installed_path: "{project-root}/bmad/bmm/workflows/1-analysis/brainstorm-project"
+template: false
+instructions: "{installed_path}/instructions.md"
+
+# Context document for project brainstorming
+project_context: "{installed_path}/project-context.md"
+
+# CORE brainstorming workflow to invoke
+core_brainstorming: "{project-root}/bmad/core/workflows/brainstorming/workflow.yaml"
+
+standalone: true
+
+web_bundle:
+  name: "brainstorm-project"
+  description: "Facilitate project brainstorming sessions by orchestrating the CIS brainstorming workflow with project-specific context and guidance."
+  author: "BMad"
+  instructions: "bmad/bmm/workflows/1-analysis/brainstorm-project/instructions.md"
+  template: false
+  web_bundle_files:
+    - "bmad/bmm/workflows/1-analysis/brainstorm-project/instructions.md"
+    - "bmad/bmm/workflows/1-analysis/brainstorm-project/project-context.md"
+    - "bmad/core/workflows/brainstorming/workflow.yaml"
+  existing_workflows:
+    - core_brainstorming: "bmad/core/workflows/brainstorming/workflow.yaml"

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

@@ -0,0 +1,221 @@
+# Game Brief Workflow
+
+## Overview
+
+The Game Brief workflow is the starting point for game projects in the BMad Method. It's a lightweight, interactive brainstorming and planning session that captures your game vision before diving into detailed Game Design Documents (GDD).
+
+## Purpose
+
+**Game Brief answers:**
+
+- What game are you making?
+- Who is it for?
+- What makes it unique?
+- Is it feasible?
+
+**This is NOT:**
+
+- A full Game Design Document
+- A technical specification
+- A production plan
+- A detailed content outline
+
+## When to Use This Workflow
+
+Use the game-brief workflow when:
+
+- Starting a new game project from scratch
+- Exploring a game idea before committing
+- Pitching a concept to team/stakeholders
+- Validating market fit and feasibility
+- Preparing input for the GDD workflow
+
+Skip if:
+
+- You already have a complete GDD
+- Continuing an existing project
+- Prototyping without planning needs
+
+## Workflow Structure
+
+### Interactive Mode (Recommended)
+
+Work through each section collaboratively:
+
+1. Game Vision (concept, pitch, vision statement)
+2. Target Market (audience, competition, positioning)
+3. Game Fundamentals (pillars, mechanics, experience goals)
+4. Scope and Constraints (platforms, timeline, budget, team)
+5. Reference Framework (inspiration, competitors, differentiators)
+6. Content Framework (world, narrative, volume)
+7. Art and Audio Direction (visual and audio style)
+8. Risk Assessment (risks, challenges, mitigation)
+9. Success Criteria (MVP, metrics, launch goals)
+10. Next Steps (immediate actions, research, questions)
+
+### YOLO Mode
+
+AI generates complete draft, then you refine sections iteratively.
+
+## Key Features
+
+### Optional Inputs
+
+The workflow can incorporate:
+
+- Market research
+- Brainstorming results
+- Competitive analysis
+- Design notes
+- Reference game lists
+
+### Realistic Scoping
+
+The workflow actively helps you:
+
+- Identify scope vs. resource mismatches
+- Assess technical feasibility
+- Recognize market risks
+- Plan mitigation strategies
+
+### Clear Handoff
+
+Output is designed to feed directly into:
+
+- GDD workflow (2-plan phase)
+- Prototyping decisions
+- Team discussions
+- Stakeholder presentations
+
+## Output
+
+**game-brief-{game_name}-{date}.md** containing:
+
+- Executive summary
+- Complete game vision
+- Target market analysis
+- Core gameplay definition
+- Scope and constraints
+- Reference framework
+- Art/audio direction
+- Risk assessment
+- Success criteria
+- Next steps
+
+## Integration with BMad Method
+
+```
+1-analysis/game-brief     (You are here)
+    ↓
+2-plan-workflows/gdd               (Game Design Document)
+    ↓
+2-plan-workflows/narrative         (Optional: Story-heavy games)
+    ↓
+3-solutioning            (Technical architecture, engine selection)
+    ↓
+4-dev-stories            (Implementation stories)
+```
+
+## Comparison: Game Brief vs. GDD
+
+| Aspect              | Game Brief                  | GDD                       |
+| ------------------- | --------------------------- | ------------------------- |
+| **Purpose**         | Validate concept            | Design for implementation |
+| **Detail Level**    | High-level vision           | Detailed specifications   |
+| **Time Investment** | 1-2 hours                   | 4-10 hours                |
+| **Audience**        | Self, team, stakeholders    | Development team          |
+| **Scope**           | Concept validation          | Implementation roadmap    |
+| **Format**          | Conversational, exploratory | Structured, comprehensive |
+| **Output**          | 3-5 pages                   | 10-30+ pages              |
+
+## Comparison: Game Brief vs. Product Brief
+
+| Aspect            | Game Brief                   | Product Brief                     |
+| ----------------- | ---------------------------- | --------------------------------- |
+| **Focus**         | Player experience, fun, feel | User problems, features, value    |
+| **Metrics**       | Engagement, retention, fun   | Revenue, conversion, satisfaction |
+| **Core Elements** | Gameplay pillars, mechanics  | Problem/solution, user segments   |
+| **References**    | Other games                  | Competitors, market               |
+| **Vision**        | Emotional experience         | Business outcomes                 |
+
+## Example Use Case
+
+### Scenario: Indie Roguelike Card Game
+
+**Starting Point:**
+"I want to make a roguelike card game with a twist"
+
+**After Game Brief:**
+
+- **Core Concept:** "A roguelike card battler where you play as emotions battling inner demons"
+- **Target Audience:** Core gamers who love Slay the Spire, interested in mental health themes
+- **Differentiator:** Emotional narrative system where deck composition affects story
+- **MVP Scope:** 3 characters, 80 cards, 30 enemy types, 3 bosses, 6-hour first run
+- **Platform:** PC (Steam) first, mobile later
+- **Timeline:** 12 months with 2-person team
+- **Key Risk:** Emotional theme might alienate hardcore roguelike fans
+- **Mitigation:** Prototype early, test with target audience, offer "mechanical-only" mode
+
+**Next Steps:**
+
+1. Build card combat prototype (2 weeks)
+2. Test emotional resonance with players
+3. Proceed to GDD workflow if prototype validates
+
+## Tips for Success
+
+### Be Honest About Scope
+
+The most common game dev failure is scope mismatch. Use this workflow to reality-check:
+
+- Can your team actually build this?
+- Is the timeline realistic?
+- Do you have budget for assets?
+
+### Focus on Player Experience
+
+Don't think about code or implementation. Think about:
+
+- What will players DO?
+- How will they FEEL?
+- Why will they CARE?
+
+### Validate Early
+
+The brief identifies assumptions and risks. Don't skip to GDD without:
+
+- Prototyping risky mechanics
+- Testing with target audience
+- Validating market interest
+
+### Use References Wisely
+
+"Like X but with Y" is a starting point, not a differentiator. Push beyond:
+
+- What specifically from reference games?
+- What are you explicitly NOT doing?
+- What's genuinely new?
+
+## FAQ
+
+**Q: Is this required before GDD?**
+A: No, but highly recommended for new projects. You can start directly with GDD if you have a clear vision.
+
+**Q: Can I use this for game jams?**
+A: Yes, but use YOLO mode for speed. Focus on vision, mechanics, and MVP scope.
+
+**Q: What if my game concept changes?**
+A: Revisit and update the brief. It's a living document during early development.
+
+**Q: How detailed should content volume estimates be?**
+A: Rough orders of magnitude are fine. "~50 enemies" not "47 enemies with 3 variants each."
+
+**Q: Should I complete this alone or with my team?**
+A: Involve your team! Collaborative briefs catch blind spots and build shared vision.
+
+## Related Workflows
+
+- **Product Brief** (`1-analysis/product-brief`): For software products, not games
+- **GDD** (`2-plan-workflows/gdd`): Next step after game brief
+- **Narrative Design** (`2-plan-workflows/narrative`): For story-heavy games after GDD
+- **Solutioning** (`3-solutioning`): Technical architecture after planning