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.