Update to Design Game Studio

{
  "description": "Coordinate real specialist agents for a complex game project while maintaining single-agent fallback and independent verification.",
  "included_files": [],
  "name": "orchestrate-game-agents",
  "skill_md_contents": "---\nname: orchestrate-game-agents\ndescription: Coordinate real specialist agents for a complex game project while maintaining single-agent fallback and independent verification.\n---\n\n# Orchestrate Game Agents\n\n\n1. Read `../../references/orchestration.md`. A role description is not an independent agent; check whether real subagent tools or an authorized backend are available.\n2. Lead Game Director owns project scope, game-design brief, engine choice, task graph, user approvals and integration.\n3. Delegate independent subproblems only when helpful: Game Designer, Engine Architect, Art Director, Gameplay Developer, Level Designer, Audio, QA/Playtester and Release. Use few agents for small games.\n4. Freeze interfaces and shared asset naming before parallel implementation. Give separate non-overlapping files/branches/worktrees and concrete acceptance checks.\n5. Keep security and QA review read-only and independent of implementers. Reconcile cross-agent decisions centrally; never claim '8 agents completed' based on simulated personas.\n6. Limit token/time/cost budgets and external side effects. Report actual subagent tasks, commands, artifacts and failures, with sequential fallback identified when used.\n\n## Execution truth and safeguards\n- A skill is an instruction workflow, not a remotely running game engine or a separately running AI agent. Inspect tools and repo state before claiming execution.\n- Preserve existing projects, names, dependencies, save formats, and user work unless a change is explicitly requested. Obtain approval for deployment, payments, destructive edits, publication, and major third-party connections.\n- Avoid reproducing protected commercial characters, levels, dialogue, soundtracks, logos, or copyrighted assets unless authorized. For assets, record origin and license. Read `../../references/security-and-rights.md`.\n- Report what was implemented, what was actually run, what failed, and what remains unverified; never describe proposed tests as passed.\n"
}