team-release

Orchestrate cross-functional release teams through planning, deployment, and post-release monitoring.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/johnatas-henrique/overdrive --skill team-release-johnatas-henrique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-release
Source: https://github.com/johnatas-henrique/overdrive/tree/main/.opencode/skills/team-release
Command: npx skills add https://github.com/johnatas-henrique/overdrive --skill team-release-johnatas-henrique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the disjointed, error-prone manual coordination of cross-functional teams during game software releases, ensuring all release phases are completed in order with proper stakeholder approvals.

Core Features & Use Cases

  • Full Release Pipeline Orchestration: Manages the entire release lifecycle from planning and release candidate creation to quality gates, deployment, and post-release monitoring.
  • Cross-Functional Team Coordination: Spawns and manages specialized subagents (release manager, QA lead, DevOps, producer, etc.) to handle domain-specific tasks in parallel where possible.
  • Go/No-Go Governance: Enforces structured decision points with user approval at each phase transition, plus error recovery protocols for blocked agents or failed steps.
  • Use Case: For a 90s F1-style racing game like Overdrive, this Skill coordinates all release roles to cut a release branch, run regression tests, deploy to staging and production, and handle post-release monitoring.

Quick Start

Use the team-release skill to execute the full release pipeline for version v1.2.0 of the Overdrive racing game.

Frequently Asked Questions about team-release

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

FAQPage Schema
How do I orchestrate cross-functional teams for a game release pipeline?

Cross-functional game release pipeline orchestration is handled by spawning specialized subagents for release management, QA, DevOps, and security to execute domain-specific tasks in parallel with enforced phase gates.

What is the go/no-go decision protocol in release management?

The go/no-go decision protocol in release management enforces structured approval points at each phase transition, ensuring stakeholders explicitly authorize progression before deployment and subsequent post-release monitoring begins.

How do I manage end-to-end deployment automation from planning to post-release monitoring?

End-to-end deployment automation manages the full release lifecycle from release candidate creation and quality gates to staging, production deployment, and post-release monitoring using orchestrated cross-functional teams.

Can I use pipeline orchestration to coordinate QA, DevOps, and security teams for complex software releases?

Yes, pipeline orchestration coordinates QA, DevOps, security, and community teams by spawning specialized subagents to handle domain-specific tasks concurrently while maintaining strict release governance and approval workflows.

What happens when a blocked agent or failed step occurs during release pipeline orchestration?

When a blocked agent or failed step occurs during release pipeline orchestration, the system applies error recovery protocols to manage the failure and maintain release governance integrity across cross-functional teams.

Does release management automation work for gaming applications requiring multi-phase deployment?

Release management automation works for gaming applications by coordinating all release roles to cut release branches, run regression tests, deploy across staging and production environments, and handle post-release monitoring.