OpenCode Game Studios

Turn a single OpenCode session into a full game development studio.
48 agents. 37 skills. Native OpenCode commands, plugins, and workflows.

---

Why This Exists

Building a game solo with AI is powerful, but an unstructured coding session still invites rushed decisions, undocumented systems, missing QA, and inconsistent architecture. OpenCode Game Studios gives your repo a studio-shaped operating model: specialized agents, reusable skills, native slash commands, OpenCode permissions, and plugins that reinforce process without taking control away from you.

The result is still user-driven development. You make the calls. The repo provides structured collaboration, documentation standards, and specialist workflows from concept through launch.

---

What's Included

Category	Count	Description
Agents	48	Native OpenCode subagents across design, programming, art, audio, narrative, QA, and production
Skills	37	Reusable SKILL.md workflows for brainstorming, reviews, planning, release, and team orchestration
Commands	37	Native OpenCode slash commands in .opencode/commands/ that load the matching skills
Plugins	4	OpenCode-native automation for guardrails, session context, compaction, and asset validation
Path Rules	11	Ported rule files under .opencode/instructions/path-rules/ for lazy loading by agents
Templates	29	Project templates in docs/project/templates/ for GDDs, ADRs, sprint plans, reports, and more

Native OpenCode Layout

AGENTS.md                        # Root project instructions for OpenCode
opencode.json                    # Native OpenCode config, permissions, and instructions
.opencode/
  agents/                        # 48 native subagents
  skills/                        # 37 reusable skills
  commands/                      # Slash command wrappers for the skills
  plugins/                       # OpenCode plugins replacing Claude hooks
  instructions/                  # Path-rule docs and workflow conventions

docs/project/                    # Project reference docs and templates

Getting Started

Prerequisites

• OpenCode installed and working
• Git
• Optional: Python 3 for validation helpers used by some workflows

Setup

1. Clone the repository:

   git clone <repo-url> my-game
   cd my-game

2. Start OpenCode:

   opencode

3. Run the onboarding command:

   /start
   

4. Follow with whichever native workflow fits your stage:
   • /brainstorm
   • /setup-engine godot 4.6
   • /project-stage-detect
   • /sprint-plan new

OpenCode Mapping

Need	OpenCode-native location
Project rules	AGENTS.md
Project config	opencode.json
Custom agents	.opencode/agents/
Skills	.opencode/skills/
Slash commands	.opencode/commands/
Plugins/hooks replacement	.opencode/plugins/
Shared docs/templates	docs/project/

Core Workflows

Reviews & Analysis /design-review /code-review /balance-check /asset-audit /scope-check /perf-profile /tech-debt

Production /sprint-plan /milestone-review /estimate /retrospective /bug-report

Project Management /start /project-stage-detect /reverse-document /gate-check /map-systems /design-system

Release /release-checklist /launch-checklist /changelog /patch-notes /hotfix

Creative /brainstorm /playtest-report /prototype /onboard /localize

Team Orchestration /team-combat /team-narrative /team-ui /team-release /team-polish /team-audio /team-level

Documentation

• docs/WORKFLOW-GUIDE.md for the end-to-end project flow
• docs/COLLABORATIVE-DESIGN-PRINCIPLE.md for the user-driven collaboration model
• docs/project/quick-start.md for the native reference set
• docs/project/agent-roster.md for the full agent table
• docs/project/skills-reference.md for all skills/commands

License

MIT License. See LICENSE for details.