bmad-gds — Claude Code skill: what it does, how to install
Acts as an AI game producer that plans development phases, turns GDDs into backlogs, and aligns team priorities across Unity, Unreal Engine, or Godot.
npx skills add akillness/jeo-skills --skill bmad-gds -a claude-codeWhat bmad-gds does
This skill serves as the production coordinator across pre-production, design, architecture, build execution, and playtesting. Instead of writing engine-level logic or debugging logs directly, it takes raw development notes and extracts the single most urgent decision.
The workflow handles five distinct situations: scoping early ideas into milestone briefs, slicing design docs into backlog items, realigning tasks after playtest feedback, routing build blockers, and gearing up for public demos. Every run generates a structured producer brief highlighting immediate actions, assignees, and downstream delegations.
Detailed frame profiler investigations and raw compilation crashes fall outside its scope, as the skill immediately routes those technical jobs to dedicated agents like game-build-log-triage.
What it helps with
- Break down a game design document into actionable epics and sprint stories
- Coordinate build priorities and store readiness ahead of a public Steam demo
- Reprioritize the backlog when playtest bug reports conflict with milestone deadlines
- Assess whether an engine build failure threatens the target release window
Example prompts for the agent
- Take our game design document and break it into epics and acceptance criteria for the upcoming sprint.
- We have a Steam demo in three weeks and mixed playtest notes. Build a coordination brief to reprioritize tasks.
- Review our Godot prototype notes and define the scope guardrails for the first milestone.
How to install bmad-gds
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill bmad-gds -a claude-code2Manually: put the files in place
~/.claude/skills/bmad-gds/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/bmad-gds/
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill bmad-gds -a codex2Manually: put the files in place
.agents/skills/bmad-gds/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill bmad-gds -a cursor2Manually: put the files in place
.cursor/skills/bmad-gds/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install akillness/jeo-skills bmad-gds2Manually: put the files in place
.github/skills/bmad-gds/SKILL.md1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill bmad-gds -a gemini-cli2Platform CLI
gemini skills install https://github.com/akillness/jeo-skills --path .agent-skills/bmad-gdsManually: put the files in place
.devin/skills/bmad-gds/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill bmad-gds -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about bmad-gds
How do I install bmad-gds in Claude Code?
Run npx skills add akillness/jeo-skills --skill bmad-gds -a claude-code. The file will be placed in ~/.claude/skills/bmad-gds/SKILL.md.
What engines does bmad-gds work with?
It supports projects built in Unity, Unreal Engine, Godot, as well as custom proprietary game engines.
When should you avoid using bmad-gds?
Skip it if you only need raw build log debugging or CPU profiling without milestone planning; those belong in tools like game-build-log-triage or game-performance-profiler.