bmad-game-dev-studio

Plugin bmad-game-dev-studio from marketplace bmad-game-dev-studio in bmad-code-org/bmad-module-game-dev-studio. Commands read from the repo's manifest — 1 month ago.

Skills (33)

• gds-agent-game-architect

  Game systems architect for technical architecture, engine design, and infrastructure. Use when the user asks to talk to Cloud Dragonborn or requests the Game Architect.

• gds-agent-game-designer

  Game designer for creative vision, GDD creation, and narrative design. Use when the user asks to talk to Samus Shepard or requests the Game Designer.

• gds-agent-game-dev

  Consolidated game developer for story execution, code implementation, code review, QA/test authorship, and sprint orchestration. Use when the user asks to talk to Link Freeman, the Game Developer, the Game QA, or the Game Scrum Master.

• gds-agent-game-solo-dev

  Elite indie game developer for rapid prototyping and solo quick-flow development. Use when the user asks to talk to Indie or requests the Game Solo Dev.

• gds-agent-tech-writer

  Technical documentation specialist and knowledge curator for game projects. Use when the user asks to talk to Paige or requests the Technical Writer.

• gds-brainstorm-game

  Facilitate game brainstorming sessions with game-specific techniques. Use when the user says "brainstorm game" or "game ideas"

• gds-create-game-brief

  Create, update, or validate a game brief. Use when the user wants help producing, editing, or validating a game brief before detailed design.

• gds-domain-research

  Conduct game domain and industry research. Use when the user says "lets create a research report on [game domain or industry]"

• gds-create-narrative

  Create comprehensive narrative documentation with story structure and world-building. Use when the user says "narrative design" or "create narrative"

• gds-gdd

  Create, update, or validate a game's Game Design Document. Use when the user wants help producing, editing, or validating a GDD — the primary design artifact covering pillars, mechanics, progression, levels, art, audio, and development epics.

• gds-prd

  Create, update, validate, or analyze a game project's PRD. Use when the user wants help producing, editing, validating, or analyzing a PRD — often derived from a GDD or prepared for external-tool integration.

• gds-ux

  Plan game UX, UI, and HUD design specifications. Use when the user says "lets create game UX", "design the HUD", "create UI specifications", or "help me plan the game UX

• gds-check-implementation-readiness

  Verify GDD, UX, Architecture, and Epics alignment before production. Use when the user says "check readiness" or "implementation readiness"

• gds-create-epics-and-stories

  Create Epics and Stories from GDD requirements for development. Use when the user says "create epics" or "create stories"

• gds-game-architecture

  Design scale-adaptive game architecture with engine systems and networking. Use when the user says "game architecture" or "design architecture"

• gds-generate-project-context

  Create optimized project-context.md for AI agent consistency. Use when the user says "project context" or "generate context"

• gds-code-review

  Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"

• gds-correct-course

  Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"

• gds-create-story

  Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"

• gds-dev-story

  Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"

• gds-investigate

  Forensic case investigation with evidence-graded findings, calibrated to the input. Use when the user asks to investigate a bug, trace what caused an incident, walk through unfamiliar code, or build a mental model of a code area before working on it.

• gds-retrospective

  Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"

• gds-sprint-planning

  Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"

• gds-sprint-status

  Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"

• gds-e2e-scaffold

  Scaffold end-to-end testing infrastructure. Use when the user says "e2e scaffold" or "set up e2e testing"

• gds-performance-test

  Design game performance testing strategy. Use when the user says "performance test" or "benchmark"

• gds-playtest-plan

  Create structured playtesting plans for user feedback. Use when the user says "playtest plan" or "playtesting"

• gds-test-automate

  Generate automated game tests for gameplay systems. Use when the user says "automate tests" or "generate tests"

• gds-test-design

  Create comprehensive game test scenarios. Use when the user says "test design" or "design tests"

• gds-test-framework

  Initialize game test framework for Unity, Unreal, or Godot. Use when the user says "test framework" or "set up testing"

• gds-test-review

  Review test quality and coverage. Use when the user says "test review" or "review tests"

• gds-document-project

  Analyze existing game projects to produce useful documentation. Use when the user says "document project" or "generate docs"

• gds-quick-dev

  Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project''s existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.