Skip to content
Get packs

Team Release Orchestrator

Coordinates a simulated release team to take a game from release candidate to deployment.

Source Download skill
Repository
Donchitos/Claude-Code-Game-Studios
Stars
32,965
Licence
MIT
Files
1 file

What it does

This skill makes the agent run a structured, multi-step game release process. It works out the target version (from the argument or from project milestone files), checks that the project's release readiness gate has passed, and then walks through phases in which it plays or delegates to roles such as release manager, QA lead, DevOps engineer and producer. It asks the user to confirm decisions at each phase transition and can write release artifacts such as go/no-go records and changelogs. The file is only partly visible: the text ends mid-list, so the full phase details are not shown.

Great for

  • Game studios using the Claude Code Game Studios template who want a guided release checklist
  • Solo game developers who want help tracking release steps and decisions
  • Teams that already run /gate-check release and want a consistent release record

Skip it if

  • Projects without the surrounding studio folder structure (docs, hooks and config files it references) since it will not resolve its config or gate state, and the agent may guess at missing steps
  • Anyone expecting unattended, fully automated deployment: the skill asks for confirmation at decision points, and the Phase 6 deploy step is gated by a user question
  • Non-game software releases, since the team roles and checks are written for game projects

Try asking

  • “Release version 1.2.0 of my game using the team-release process”
  • “Run the release pipeline with --review lean for the next version”
  • “Prepare the go/no-go record and changelog for the upcoming build”
Step-by-step guide: how to use Team Release OrchestratorInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 1 original files, the MIT licence and an attribution note.

    team-release.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip team-release.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip team-release.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Pass an explicit version number so the agent does not have to infer it from milestone files
  • Run /gate-check release before this skill; it will stop and ask otherwise, and overriding the stage check is recorded in the release report
  • Review each AskUserQuestion prompt carefully before approving, especially the deploy decision

What's inside

  • SKILL.md

Redistributed unmodified from Donchitos/Claude-Code-Game-Studios under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.