bmad-gds - BMAD Game Development Studio
When to use this skill
- Starting a new game project and need a structured concept → production workflow
- Creating a Game Design Document (GDD), narrative design, or technical architecture
- Managing sprints and dev stories for a game team
- Setting up test frameworks for Unity, Unreal Engine, or Godot projects
- Quick prototyping or rapid feature work without full planning overhead
- Reviewing code or running retrospectives after development epics
Installation
npx skills add https://github.com/supercent-io/skills-template --skill bmad-gds
Supported Engines
Unity · Unreal Engine · Godot · Custom/Other
BMAD-GDS Workflow Commands
Phase 1 — Pre-production
| Command |
Description |
bmad-gds-brainstorm-game |
Facilitate a game brainstorming session with game-specific ideation techniques |
bmad-gds-game-brief |
Create an interactive game brief defining concept and core mechanics |
Phase 2 — Design
| Command |
Description |
bmad-gds-gdd |
Generate a Game Design Document: mechanics, systems, progression, implementation guidance |
bmad-gds-narrative |
Create narrative documentation: story structure, character arcs, world-building |
Phase 3 — Technical
| Command |
Description |
bmad-gds-project-context |
Generate project-context.md for consistent AI agent coordination |
bmad-gds-game-architecture |
Produce scale-adaptive game architecture: engine, systems, networking, technical design |
bmad-gds-test-framework |
Initialize test framework architecture for Unity, Unreal, or Godot |
bmad-gds-test-design |
Create comprehensive test scenarios covering gameplay, progression, and quality |
Phase 4 — Production
| Command |
Description |
bmad-gds-sprint-planning |
Generate or update sprint-status.yaml from epic files |
bmad-gds-sprint-status |
View sprint progress, surface risks, get next action recommendation |
bmad-gds-create-story |
Create a dev-ready implementation story |
bmad-gds-dev-story |
Execute a dev story: implement tasks and tests |
bmad-gds-code-review |
QA code review for stories flagged Ready for Review |
bmad-gds-correct-course |
Navigate major in-sprint course corrections |
bmad-gds-retrospective |
Facilitate retrospective after epic completion |
Game Testing
| Command |
Description |
bmad-gds-test-automate |
Generate automated game tests for gameplay systems |
bmad-gds-e2e-scaffold |
Scaffold end-to-end testing infrastructure |
bmad-gds-playtest-plan |
Create a structured playtesting plan for user testing sessions |
bmad-gds-performance-test |
Design a performance testing strategy for profiling and optimization |
bmad-gds-test-review |
Review test quality and coverage gaps |
Quick / Anytime
| Command |
Description |
bmad-gds-quick-prototype |
Rapid prototyping to validate mechanics without full planning overhead |
bmad-gds-quick-spec |
Quick tech spec for simple, well-defined features or tasks |
bmad-gds-quick-dev |
Flexible rapid implementation for game features |
bmad-gds-document-project |
Analyze and document an existing game project |
Specialized Agents
| Agent |
Role |
game-designer |
Game concept, mechanics, GDD, narrative design, brainstorming |
game-architect |
Technical architecture, system design, project context |
game-dev |
Implementation, dev stories, code review |
game-scrum-master |
Sprint planning, story management, course corrections, retrospectives |
game-qa |
Test framework, test design, automation, E2E, playtest, performance |
game-solo-dev |
Full-scope solo mode: quick prototype, quick spec, quick dev |
Quick Start
Scenario: New Unity3D game — from concept to first sprint
# Step 0: Confirm unity-mcp is running before starting
npx unity-mcp status
Step 1 — bmad-gds-brainstorm-game
→ "mobile endless runner on Unity3D with procedural obstacles"
Step 2 — bmad-gds-game-brief
→ Lock in core loop: run, dodge, score
Step 3 — bmad-gds-gdd
→ Full GDD: mechanics, progression, power-up systems
Step 4 — bmad-gds-game-architecture
→ Unity3D architecture: ScriptableObject data layer, pooling, input
Step 5 — bmad-gds-test-framework
→ Initialize Unity Test Runner + EditMode/PlayMode scaffolding
Step 6 — bmad-gds-sprint-planning
→ Break epics into Unity3D dev stories
Step 7 — bmad-gds-dev-story
→ Implement story: "Player controller with physics-based movement"
Step 8 — bmad-gds-code-review
→ QA gate before merging to main
Typical Workflow
- Run
bmad-gds-brainstorm-game → ideate game concept
- Run
bmad-gds-game-brief → lock in concept and core mechanics
- Run
bmad-gds-gdd → produce full Game Design Document
- Run
bmad-gds-game-architecture → define technical architecture
- Run
bmad-gds-sprint-planning → break work into sprints and stories
- Run
bmad-gds-dev-story per story → implement features
- Run
bmad-gds-code-review → quality gate before merge
- Run
bmad-gds-retrospective → continuous improvement after each epic
Quick Reference
| Action |
Command |
| Brainstorm game concept |
bmad-gds-brainstorm-game |
| Create game brief |
bmad-gds-game-brief |
| Generate GDD |
bmad-gds-gdd |
| Define architecture |
bmad-gds-game-architecture |
| Plan sprint |
bmad-gds-sprint-planning |
| Check sprint status |
bmad-gds-sprint-status |
| Create story |
bmad-gds-create-story |
| Develop story |
bmad-gds-dev-story |
| Quick prototype |
bmad-gds-quick-prototype |
1---2name: bmad-gds-23description: AI-driven Game Development Studio using BMAD methodology. Routes game projects through Pre-production, Design, Architecture, Production, and Game Testing phases with 6 specialized agents. Supports Unity, Unreal Engine, Godot, and custom engines.4---567# bmad-gds - BMAD Game Development Studio89## When to use this skill1011- Starting a new game project and need a structured concept → production workflow12- Creating a Game Design Document (GDD), narrative design, or technical architecture13- Managing sprints and dev stories for a game team14- Setting up test frameworks for Unity, Unreal Engine, or Godot projects15- Quick prototyping or rapid feature work without full planning overhead16- Reviewing code or running retrospectives after development epics1718---1920## Installation2122```bash23npx skills add https://github.com/supercent-io/skills-template --skill bmad-gds24```2526---2728## Supported Engines2930Unity · Unreal Engine · Godot · Custom/Other3132---3334## BMAD-GDS Workflow Commands3536### Phase 1 — Pre-production3738| Command | Description |39|---------|-------------|40| `bmad-gds-brainstorm-game` | Facilitate a game brainstorming session with game-specific ideation techniques |41| `bmad-gds-game-brief` | Create an interactive game brief defining concept and core mechanics |4243### Phase 2 — Design4445| Command | Description |46|---------|-------------|47| `bmad-gds-gdd` | Generate a Game Design Document: mechanics, systems, progression, implementation guidance |48| `bmad-gds-narrative` | Create narrative documentation: story structure, character arcs, world-building |4950### Phase 3 — Technical5152| Command | Description |53|---------|-------------|54| `bmad-gds-project-context` | Generate project-context.md for consistent AI agent coordination |55| `bmad-gds-game-architecture` | Produce scale-adaptive game architecture: engine, systems, networking, technical design |56| `bmad-gds-test-framework` | Initialize test framework architecture for Unity, Unreal, or Godot |57| `bmad-gds-test-design` | Create comprehensive test scenarios covering gameplay, progression, and quality |5859### Phase 4 — Production6061| Command | Description |62|---------|-------------|63| `bmad-gds-sprint-planning` | Generate or update sprint-status.yaml from epic files |64| `bmad-gds-sprint-status` | View sprint progress, surface risks, get next action recommendation |65| `bmad-gds-create-story` | Create a dev-ready implementation story |66| `bmad-gds-dev-story` | Execute a dev story: implement tasks and tests |67| `bmad-gds-code-review` | QA code review for stories flagged Ready for Review |68| `bmad-gds-correct-course` | Navigate major in-sprint course corrections |69| `bmad-gds-retrospective` | Facilitate retrospective after epic completion |7071### Game Testing7273| Command | Description |74|---------|-------------|75| `bmad-gds-test-automate` | Generate automated game tests for gameplay systems |76| `bmad-gds-e2e-scaffold` | Scaffold end-to-end testing infrastructure |77| `bmad-gds-playtest-plan` | Create a structured playtesting plan for user testing sessions |78| `bmad-gds-performance-test` | Design a performance testing strategy for profiling and optimization |79| `bmad-gds-test-review` | Review test quality and coverage gaps |8081### Quick / Anytime8283| Command | Description |84|---------|-------------|85| `bmad-gds-quick-prototype` | Rapid prototyping to validate mechanics without full planning overhead |86| `bmad-gds-quick-spec` | Quick tech spec for simple, well-defined features or tasks |87| `bmad-gds-quick-dev` | Flexible rapid implementation for game features |88| `bmad-gds-document-project` | Analyze and document an existing game project |8990---9192## Specialized Agents9394| Agent | Role |95|-------|------|96| `game-designer` | Game concept, mechanics, GDD, narrative design, brainstorming |97| `game-architect` | Technical architecture, system design, project context |98| `game-dev` | Implementation, dev stories, code review |99| `game-scrum-master` | Sprint planning, story management, course corrections, retrospectives |100| `game-qa` | Test framework, test design, automation, E2E, playtest, performance |101| `game-solo-dev` | Full-scope solo mode: quick prototype, quick spec, quick dev |102103---104105## Quick Start106107**Scenario: New Unity3D game — from concept to first sprint**108109```bash110# Step 0: Confirm unity-mcp is running before starting111npx unity-mcp status112```113114```text115Step 1 — bmad-gds-brainstorm-game116 → "mobile endless runner on Unity3D with procedural obstacles"117118Step 2 — bmad-gds-game-brief119 → Lock in core loop: run, dodge, score120121Step 3 — bmad-gds-gdd122 → Full GDD: mechanics, progression, power-up systems123124Step 4 — bmad-gds-game-architecture125 → Unity3D architecture: ScriptableObject data layer, pooling, input126127Step 5 — bmad-gds-test-framework128 → Initialize Unity Test Runner + EditMode/PlayMode scaffolding129130Step 6 — bmad-gds-sprint-planning131 → Break epics into Unity3D dev stories132133Step 7 — bmad-gds-dev-story134 → Implement story: "Player controller with physics-based movement"135136Step 8 — bmad-gds-code-review137 → QA gate before merging to main138```139140---141142## Typical Workflow1431441. Run `bmad-gds-brainstorm-game` → ideate game concept1452. Run `bmad-gds-game-brief` → lock in concept and core mechanics1463. Run `bmad-gds-gdd` → produce full Game Design Document1474. Run `bmad-gds-game-architecture` → define technical architecture1485. Run `bmad-gds-sprint-planning` → break work into sprints and stories1496. Run `bmad-gds-dev-story` per story → implement features1507. Run `bmad-gds-code-review` → quality gate before merge1518. Run `bmad-gds-retrospective` → continuous improvement after each epic152153---154155## Quick Reference156157| Action | Command |158|--------|---------|159| Brainstorm game concept | `bmad-gds-brainstorm-game` |160| Create game brief | `bmad-gds-game-brief` |161| Generate GDD | `bmad-gds-gdd` |162| Define architecture | `bmad-gds-game-architecture` |163| Plan sprint | `bmad-gds-sprint-planning` |164| Check sprint status | `bmad-gds-sprint-status` |165| Create story | `bmad-gds-create-story` |166| Develop story | `bmad-gds-dev-story` |167| Quick prototype | `bmad-gds-quick-prototype` |
akillness