team-release

Coordinate staged software releases from candidate version to production deployment.

277|65|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/pixel-cellar/Claude-Code-Game-Studios --skill team-release-pixel-cellar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-release
Source: https://github.com/pixel-cellar/Claude-Code-Game-Studios/tree/main/.claude/skills/team-release
Command: npx skills add https://github.com/pixel-cellar/Claude-Code-Game-Studios --skill team-release-pixel-cellar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating release planning, approvals, and deployments across multiple roles can cause bottlenecks, miscommunication, and delays. This skill provides a structured workflow to align release-manager, qa-lead, devops-engineer, and producer through clearly defined stages and decision gates to ensure a smooth release.

Core Features & Use Cases

  • Structured delegation: automatically assigns each stage to the appropriate sub-agent and aggregates their proposals for user review.
  • Stage-gated release pipeline: enforces stage transitions (planning, candidate, quality gates, localization/performance, decision, deployment) with accountability.
  • End-to-end release visibility: share status, milestones, and risks with stakeholders and maintain traceability.

Quick Start

Initiate the release of version 1.2.3 by assigning subagents and starting Stage 1 planning with milestone checks.

Frequently Asked Questions about team-release

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

FAQPage Schema
How do I coordinate a software release pipeline across multiple roles like QA and DevOps?

Coordinate a software release pipeline by delegating tasks to specialized sub-agents for release management, QA, DevOps, and production. This enforces stage-gated transitions across planning, validation, and deployment to ensure team alignment.

What is stage-gated release management and how does it prevent deployment bottlenecks?

Stage-gated release management enforces structured transitions across planning, quality gates, and deployment. It prevents bottlenecks by assigning accountability to specific roles and aggregating proposals for user review before proceeding to the next pipeline stage.

How do I maintain stakeholder communication and end-to-end visibility during versioning and deployment?

Maintain stakeholder communication during deployment by sharing status, milestones, and risks throughout the release pipeline. This provides end-to-end release visibility and ensures traceability from candidate version to production deployment.

Can I use this release management workflow for both localization and performance validation stages?

Yes, the release management workflow supports localization and performance validation stages. It orchestrates these phases alongside quality gates and decision transitions to ensure comprehensive validation before production deployment.

What's the best way to start planning a new software release version with a coordinated team?

Start planning a new software release version by initiating Stage 1 planning and assigning sub-agents to their respective roles. This structured delegation triggers milestone checks to align the coordinated team for the deployment pipeline.

Why does cross-functional release coordination fail without structured delegation and decision gates?

Cross-functional release coordination fails without structured delegation due to miscommunication and delayed approvals between roles. Decision gates enforce accountability and aggregate proposals across QA, DevOps, and stakeholders to prevent bottlenecks.