team-release

Coordinate game release workflows from planning through deployment with phase-gate approvals.

Updated Dec 22, 2024
One-click install
npx skills add https://github.com/imgamer/AILearn --skill team-release-imgamer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-release
Source: https://github.com/imgamer/AILearn/tree/main/game-studios/Claude-Code-Game-Studios-e375f/.claude/skills/team-release
Command: npx skills add https://github.com/imgamer/AILearn --skill team-release-imgamer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates the major release roles needed to take a candidate build through quality gates, go/no-go approval, and deployment without missing critical checks.

Core Features & Use Cases

  • Release planning and authorization: Align scope and acceptance criteria through producer-led go/no-go preparation.
  • Release candidate preparation: Cut the release branch, bump versions, generate a checklist, and freeze for release.
  • Parallel quality gates: Run QA regression, build/artifact verification, and optional security/network stability reviews.
  • Deployment and player communication: Tag/changelog, deploy to staging and production, and coordinate patch notes and launch messaging.

Quick Start

Ask the AI to run the team-release skill to orchestrate the full release pipeline for version v1.2.3.

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 pipeline with versioning and phase-gate approvals?

Game release orchestration coordinates release-manager, qa-lead, devops-engineer, and producer roles to move a candidate build through quality gates, go/no-go approval, and deployment using phase-gate checks.

What is the best way to manage release-candidate branching and regression validation?

Release-candidate preparation involves cutting the release branch, bumping target versions, and freezing the build. You then run parallel quality gates including qa regression and build/artifact verification before deployment.

Can I use this release workflow for both single-player and multiplayer online games?

Yes, the release workflow applies to single-player and online multiplayer games. For online titles, it adds optional security and network stability sign-offs alongside standard telemetry and analytics checks before go/no-go approval.

How do I automate patch notes and launch communication during a deployment?

Deployment coordination tags the release and generates a changelog. It orchestrates staging and production deployments alongside final patch notes and launch messaging to ensure player communication aligns with the release.

Does the release process require resolving a target version before starting?

Yes, the workflow requires resolving the target version from provided arguments or milestone/session-state files before proceeding. This version resolution ensures all downstream release-candidate branching and build validation steps target the correct milestone.

What happens if a quality gate or security audit fails during release orchestration?

Release orchestration enforces phase-gate approvals via AskUserQuestion interactions. If qa regression, build verification, or security audits fail, the pipeline halts to prevent a flawed build from advancing to deployment.