team-release

Automate end-to-end game release workflows with structured phase gates and go/no-go decisions.

Updated Jul 22, 2025
One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill team-release-michaelsolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-release
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/team-release
Command: npx skills add https://github.com/MichaelSolati/mkai --skill team-release-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Game releases require coordinating multiple specialized cross-functional roles, which is error-prone and disjointed when managed manually, leading to missed quality gates, delayed launches, or post-release issues.

Core Features & Use Cases

  • Structured 7-Phase Release Pipeline: Guides teams through release planning, candidate cutting, parallel quality gates, go/no-go decisions, deployment, and post-release monitoring with clear phase outputs.
  • Configurable Review Modes: Supports full, lean, and solo review modes to adapt to team size and release criticality, skipping non-essential gates for smaller or low-risk releases.
  • Use Case: A game studio preparing to ship a major update can use this skill to automate the entire release process, from inferring the target version from milestone data to coordinating parallel testing, security audits, and deployment, with built-in error recovery for blocked tasks.

Quick Start

Use the team-release skill to execute the full release pipeline for the next version of your game project.

Frequently Asked Questions about team-release

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

FAQPage Schema
How do I automate game release workflows for cross-functional teams?

Game release workflows can be automated using a structured 7-phase pipeline that handles release planning, candidate cutting, parallel quality gates, go/no-go decisions, deployment, and post-release monitoring. This eliminates disjointed manual coordination across cross-functional teams.

What is a go/no-go decision process in a game release pipeline?

A go/no-go decision process in a game release pipeline is an enforced phase gate that evaluates parallel quality checks and regression tests before allowing deployment. It ensures versioned game software meets structured criteria before proceeding to the next release phase.

Can I skip quality gates for smaller game releases or updates?

Yes, you can skip non-essential quality gates for smaller or low-risk game releases by using configurable review modes. The pipeline supports full, lean, and solo review modes to adapt the release orchestration to your team size and release criticality.

How do I manage release branches and coordinate regression testing for a game update?

Release branch management and regression test coordination are handled within the release candidate cutting and parallel quality gate phases. The pipeline automates these tasks sequentially, inferring target versions from milestone data to ensure structured phase outputs.

What is the best way to handle error recovery during game deployment automation?

Deployment automation error recovery is best handled through built-in protocols within the release pipeline that manage blocked tasks. This allows the orchestration workflow to recover from errors encountered during the parallel quality checks or deployment phases.

Does game release orchestration support post-release monitoring?

Yes, game release orchestration includes post-release monitoring as the final phase of the structured pipeline. After the go/no-go decision and deployment automation, the workflow continues to monitor the versioned game software release for any post-release issues.