ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc status updates

Browse Source
This commit is contained in:
Brian Madison
2025-10-04 01:29:40 -05:00
parent a747017520
commit 46cabf72cd
315 changed files with 1 additions and 38707 deletions
Download Patch File Download Diff File Expand all files Collapse all files

221
bmad/bmm/workflows/1-analysis/game-brief/README.md
View File

@@ -1,221 +0,0 @@
# 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/gdd (Game Design Document)
↓
2-plan/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/gdd`): Next step after game brief
- **Narrative Design** (`2-plan/narrative`): For story-heavy games after GDD
- **Solutioning** (`3-solutioning`): Technical architecture after planning

128
bmad/bmm/workflows/1-analysis/game-brief/checklist.md
View File

@@ -1,128 +0,0 @@
# 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._

517
bmad/bmm/workflows/1-analysis/game-brief/instructions.md
View File

@@ -1,517 +0,0 @@
# 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>
<workflow>
<step n="0" goal="Initialize game brief session">
<action>Welcome the user to the Game Brief creation process</action>
<action>Explain this is a collaborative process to define their game vision</action>
<ask>What is the working title for your game?</ask>
<template-output>game_name</template-output>
</step>
<step n="1" goal="Gather available inputs and context">
<action>Check what inputs the user has available:</action>
<ask>Do you have any of these documents to help inform the brief?
1. Market research or player data
2. Brainstorming results or game jam prototypes
3. Competitive game analysis
4. Initial game ideas or design notes
5. Reference games list
6. None - let's start fresh
Please share any documents you have or select option 6.</ask>
<action>Load and analyze any provided documents</action>
<action>Extract key insights and themes from input documents</action>
<ask>Based on what you've shared (or if starting fresh), tell me:
- What's the core gameplay experience you want to create?
- What emotion or feeling should players have?
- What sparked this game idea?</ask>
<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'">
<ask>Let's capture your game vision.
**Core Concept** - What is your game in one sentence?
Example: "A roguelike deck-builder where you climb a mysterious spire"
**Elevator Pitch** - Describe your game in 2-3 sentences as if pitching to a publisher or player.
Example: "Slay the Spire fuses card games and roguelikes together. Craft a unique deck, encounter bizarre creatures, discover relics of immense power, and kill the Spire."
**Vision Statement** - What is the aspirational goal for this game? What experience do you want to create?
Example: "Create a deeply replayable tactical card game that rewards strategic thinking while maintaining the excitement of randomness. Every run should feel unique but fair."
Your answers:</ask>
<action>Help refine the core concept to be clear and compelling</action>
<action>Ensure elevator pitch is concise but captures the hook</action>
<action>Guide vision statement to be aspirational but achievable</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'">
<ask>Who will play your game?
**Primary Audience:**
- Age range
- Gaming experience level (casual, core, hardcore)
- Preferred genres
- Platform preferences
- Typical play session length
- Why will THIS game appeal to them?
**Secondary Audience** (if applicable):
- Who else might enjoy this game?
- How might their needs differ?
**Market Context:**
- What's the market opportunity?
- Are there similar successful games?
- What's the competitive landscape?
- Why is now the right time for this game?</ask>
<action>Push for specificity beyond "people who like fun games"</action>
<action>Help identify a realistic and reachable audience</action>
<action>Document market evidence or 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'">
<ask>Let's define your core gameplay.
**Core Gameplay Pillars (2-4 fundamental elements):**
These are the pillars that define your game. Everything should support these.
Examples:
- "Tight controls + challenging combat + rewarding exploration" (Hollow Knight)
- "Emergent stories + survival tension + creative problem solving" (RimWorld)
- "Strategic depth + quick sessions + massive replayability" (Into the Breach)
**Primary Mechanics:**
What does the player actually DO?
- Core actions (jump, shoot, build, manage, etc.)
- Key systems (combat, resource management, progression, etc.)
- Interaction model (real-time, turn-based, etc.)
**Player Experience Goals:**
What emotions and experiences are you designing for?
Examples: tension and relief, mastery and growth, creativity and expression, discovery and surprise
Your game fundamentals:</ask>
<action>Ensure pillars are specific and measurable</action>
<action>Focus on player actions, not implementation details</action>
<action>Connect mechanics to emotional experience</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'">
<ask>Let's establish realistic constraints.
**Target Platforms:**
- PC (Steam, itch.io, Epic)?
- Console (which ones)?
- Mobile (iOS, Android)?
- Web browser?
- Priority order if multiple?
**Development Timeline:**
- Target release date or timeframe?
- Are there fixed deadlines (game jams, funding milestones)?
- Phased release (early access, beta)?
**Budget Considerations:**
- Self-funded, grant-funded, publisher-backed?
- Asset creation budget (art, audio, voice)?
- Marketing budget?
- Tools and software costs?
**Team Resources:**
- Team size and roles?
- Full-time or part-time?
- Skills available vs. skills needed?
- Outsourcing plans?
**Technical Constraints:**
- Engine preference or requirement?
- Performance targets (frame rate, load times)?
- File size limits?
- Accessibility requirements?</ask>
<action>Help user be realistic about scope</action>
<action>Identify potential blockers early</action>
<action>Document assumptions about resources</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'">
<ask>Let's identify your reference games and position.
**Inspiration Games:**
List 3-5 games that inspire this project. For each:
- Game name
- What you're drawing from it (mechanic, feel, art style, etc.)
- What you're NOT taking from it
**Competitive Analysis:**
What games are most similar to yours?
- Direct competitors (very similar games)
- Indirect competitors (solve same player need differently)
- What they do well
- What they do poorly
- What your game will do differently
**Key Differentiators:**
What makes your game unique?
- What's your hook?
- Why will players choose your game over alternatives?
- What can you do that others can't or won't?</ask>
<action>Help identify genuine differentiation vs. "just better"</action>
<action>Look for specific, concrete differences</action>
<action>Validate differentiators are actually valuable to players</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'">
<ask>Let's scope your content needs.
**World and Setting:**
- Where/when does your game take place?
- How much world-building is needed?
- Is narrative important (critical, supporting, minimal)?
- Real-world or fantasy/sci-fi?
**Narrative Approach:**
- Story-driven, story-light, or no story?
- Linear, branching, or emergent narrative?
- Cutscenes, dialogue, environmental storytelling?
- How much writing is needed?
**Content Volume:**
Estimate the scope:
- How long is a typical playthrough?
- How many levels/stages/areas?
- Replayability approach (procedural, unlocks, multiple paths)?
- Asset volume (characters, enemies, items, environments)?</ask>
<action>Help estimate content realistically</action>
<action>Identify if narrative workflow will be needed later</action>
<action>Flag content-heavy areas that need planning</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'">
<ask>What should your game look and sound like?
**Visual Style:**
- Art style (pixel art, low-poly, hand-drawn, realistic, etc.)
- Color palette and mood
- Reference images or games with similar aesthetics
- 2D or 3D?
- Animation requirements
**Audio Style:**
- Music genre and mood
- SFX approach (realistic, stylized, retro)
- Voice acting needs (full, partial, none)?
- Audio importance to gameplay (critical or supporting)
**Production Approach:**
- Creating assets in-house or outsourcing?
- Asset store usage?
- Generative/AI tools?
- Style complexity vs. team capability?</ask>
<action>Ensure art/audio vision aligns with budget and team skills</action>
<action>Identify potential production bottlenecks</action>
<action>Note if style guide will be needed</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'">
<ask>Let's identify potential risks honestly.
**Key Risks:**
- What could prevent this game from being completed?
- What could make it not fun?
- What assumptions are you making that might be wrong?
**Technical Challenges:**
- Any unproven technical elements?
- Performance concerns?
- Platform-specific challenges?
- Middleware or tool dependencies?
**Market Risks:**
- Is the market saturated?
- Are you dependent on a trend or platform?
- Competition concerns?
- Discoverability challenges?
**Mitigation Strategies:**
For each major risk, what's your plan?
- How will you validate assumptions?
- What's the backup plan?
- Can you prototype risky elements early?</ask>
<action>Encourage honest risk assessment</action>
<action>Focus on actionable mitigation, not just worry</action>
<action>Prioritize risks by impact and likelihood</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'">
<ask>What does success look like?
**MVP Definition:**
What's the absolute minimum playable version?
- Core loop must be fun and complete
- Essential content only
- What can be added later?
- When do you know MVP is "done"?
**Success Metrics:**
How will you measure success?
- Players acquired
- Retention rate (daily, weekly)
- Session length
- Completion rate
- Review scores
- Revenue targets (if commercial)
- Community engagement
**Launch Goals:**
What are your concrete targets for launch?
- Sales/downloads in first month?
- Review score target?
- Streamer/press coverage goals?
- Community size goals?</ask>
<action>Push for specific, measurable goals</action>
<action>Distinguish between MVP and full release</action>
<action>Ensure goals 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'">
<ask>What needs to happen next?
**Immediate Actions:**
What should you do right after this brief?
- Prototype a core mechanic?
- Create art style test?
- Validate technical feasibility?
- Build vertical slice?
- Playtest with target audience?
**Research Needs:**
What do you still need to learn?
- Market validation?
- Technical proof of concept?
- Player interest testing?
- Competitive deep-dive?
**Open Questions:**
What are you still uncertain about?
- Design questions to resolve
- Technical unknowns
- Market validation needs
- Resource/budget questions</ask>
<action>Create actionable next steps</action>
<action>Prioritize by importance and dependency</action>
<action>Identify blockers that need resolution</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. 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>
<template-output>final_brief</template-output>
</step>
</workflow>

205
bmad/bmm/workflows/1-analysis/game-brief/template.md
View File

@@ -1,205 +0,0 @@
# 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._

31
bmad/bmm/workflows/1-analysis/game-brief/workflow.yaml
View File

@@ -1,31 +0,0 @@
# 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
config_source: "{project-root}/bmad/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
date: system-generated
# Optional input documents
recommended_inputs:
- market_research: "Market research document (optional)"
- brainstorming_results: "Brainstorming session outputs (optional)"
- competitive_analysis: "Competitive game analysis (optional)"
- initial_ideas: "Initial game ideas or notes (optional)"
- reference_games: "List of inspiration games (optional)"
# Module path and component files
installed_path: "{project-root}/bmad/bmm/workflows/1-analysis/game-brief"
template: "{installed_path}/template.md"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"
# Output configuration
default_output_file: "{output_folder}/game-brief-{{game_name}}-{{date}}.md"
# Workflow settings
autonomous: false # This is an interactive workflow requiring user collaboration
brief_format: "comprehensive" # Options: "comprehensive" (full detail) or "executive" (3-page limit)