team-release

Orchestrates a multi-agent release pipeline from candidate build to production deployment.

13|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/frabcd/codex-ai-game-studio --skill team-release-frabcd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-release
Source: https://github.com/frabcd/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/team-release
Command: npx skills add https://github.com/frabcd/codex-ai-game-studio --skill team-release-frabcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating a game release across QA, DevOps, security, analytics, and community roles is error-prone when done ad hoc; this Skill runs the entire release as a structured, gated pipeline with explicit sign-offs and a go/no-go decision. ## Core Features & Use Cases - Phased Release Pipeline: Runs seven phases from release planning and candidate branching through quality gates, go/no-go, deployment, and post-release monitoring. - Role-Based Subagent Delegation: Spawns release-manager, qa-lead, devops-engineer, security-engineer, analytics-engineer, community-manager, and producer subagents, in parallel where the pipeline allows. - Review Modes and Recovery: Supports full, lean, and solo review modes, plus an error recovery protocol that surfaces blocked agents and always produces a partial report. - Use Case: Before shipping v1.2.0 of a multiplayer game, invoke this Skill to cut the release branch, run regression and security audits in parallel, collect sign-offs, get the producer's go/no-go, and deploy with patch notes ready. ## Quick Start Use the team-release skill to release version v1.2.0 and coordinate the full release team through deployment.

Frequently Asked Questions about team-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate a game release with multiple team roles?

Invoke the team-release skill with a version number to run a seven-phase pipeline. It delegates work to release-manager, qa-lead, devops-engineer, and producer subagents, requiring your approval at each phase transition before proceeding.

What happens if I don't provide a version number for a release?

The skill reads production/session-state/active.md and recent milestone files to infer the target version, then asks you to confirm. If no version is discoverable, it prompts you directly rather than defaulting to a hardcoded value.

What are the full, lean, and solo review modes?

Full mode spawns all director and lead gates, lean mode keeps only PHASE-GATE type director gates, and solo mode skips all agent gates. Set the mode with a --review argument or a production/review-mode.txt file; otherwise it defaults to lean.

What happens when the producer declares a no-go on a release?

The pipeline halts before deployment and skips Phase 6 entirely. You can fix the blocker and re-run the affected phase, defer the release, or override with written justification that gets embedded in the release record.

Does the release pipeline handle multiplayer or online games differently?

Yes. If the game has online features, multiplayer, or player data, the pipeline additionally spawns a security-engineer for a pre-release audit and a network-programmer to sign off on netcode stability during the quality gate phase.

What happens if a release subagent fails or gets blocked?

The error recovery protocol surfaces the blocked agent immediately, checks whether later phases depend on its output, and offers options to skip with a noted gap, retry with narrower scope, or stop. A partial report is always produced.