BMAD Game Development Studio

Use this skill as the game producer / orchestration layer for the repository's game-development cluster.

The job is not to do every game task directly. The job is to:

1. normalize a messy game-production packet,
2. decide which phase or risk matters most now,
3. produce the next coordination artifact,
4. route specialist work to the right downstream skill.

Read references/operating-modes.md for the main entry modes and references/scope-boundaries.md before choosing between this skill and the narrower game skills.

When to use this skill

• A game idea, prototype, or existing project needs to be turned into a milestone brief or production plan
• A small team needs help converting a GDD or design brief into epics, stories, and review checkpoints
• Playtest notes, bug lists, and milestone pressure need one cross-functional reprioritization pass
• A public beat such as a demo, festival, playtest, or launch target is forcing design, QA, and production decisions to reconnect
• The user needs one coordinating artifact first, then wants the skill to point toward the correct specialist follow-up