mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-29 16:14:59 +00:00
129 lines
3.9 KiB
Markdown
129 lines
3.9 KiB
Markdown
|
|
# 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._
|