team-release

Orchestrates a multi-agent release pipeline from release candidate through deployment and post-release monitoring.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating a game release requires sign-offs from QA, DevOps, security, analytics, and production roles, and doing this manually leads to missed gates, untested builds, and chaotic go/no-go decisions. ## Core Features & Use Cases - Phased Release Pipeline: Runs seven structured 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 with full context, running independent gates in parallel. - Configurable Review Modes: Supports full, lean, and solo review modes to scale director gate involvement based on release risk. - Use Case: A studio preparing v1.2.0 invokes the skill, which infers the version from milestone data, cuts a release branch, runs regression and security audits in parallel, collects sign-offs, and deploys only after a producer go decision. ## Quick Start Ask the assistant to run the team-release skill for version v1.2.0 and confirm each phase gate as the release pipeline progresses.

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, and it delegates work to release-manager, qa-lead, devops-engineer, and producer subagents across seven phases. Each phase transition requires your approval before proceeding.

What happens if the release gets a no-go decision?

On a producer NO-GO, the skill skips deployment entirely and offers options to fix the blocker, defer the release, or override with written justification. It produces a partial report covering completed phases and marks the verdict BLOCKED.

Can I run the release pipeline without all director gates?

Yes, the skill supports three review modes: full spawns all director gates, lean keeps only phase-gate directors, and solo skips all agent gates. Set the mode via a --review argument or a production/review-mode.txt file.

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

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.

How does the skill handle a blocked or failing subagent?

It surfaces the blocker immediately, checks whether downstream phases depend on that agent's output, and offers to skip with a noted gap, retry with narrower scope, or stop and resolve the issue. A partial report is always produced.