team-release

Name: team-release
Availability: InStock
Author: kay6198835

Coordinate a phase-gated multi-role release pipeline from candidate to deployment.

Updated Feb 8, 2024

Search Tags:#release #orchestration #governance #pipeline #milestones #team #stakeholders

Ready to run

npx skills add https://github.com/kay6198835/Game-RPG --skill team-release-kay6198835

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: team-release
Source: https://github.com/kay6198835/Game-RPG/tree/main/.claude/skills/team-release
Command: npx skills add https://github.com/kay6198835/Game-RPG --skill team-release-kay6198835

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a multi-role release pipeline to move a candidate build from milestone to deployment, ensuring alignment, traceability, and governance across teams.

Core Features & Use Cases

Phase-gated orchestration: coordinates planning, RC, QA, release gates, and deployment across roles.
Subagent delegation: spawns parallel subagents (release-manager, qa-lead, devops-engineer, security-engineer, analytics-engineer, community-manager, producer, network-programmer) with full context.
Decision logging & prompts: uses iterative asks for each phase transition and records full analysis for traceability.
End-to-end lifecycle: supports milestone checks, version inference, changelog generation, and post-release signaling.

Quick Start

To begin, provide the target version and milestone status so the orchestrator can initialize the release pipeline.

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 multi-role release pipeline across teams?▼

Multi-role release pipeline orchestration coordinates a candidate build from planning to deployment by delegating tasks to subagents like release-manager, qa-lead, and devops-engineer with full context. It enforces a phase-gated process to ensure cross-team alignment and governance.

What is phase-gated release governance and how does it manage milestones?▼

Phase-gated release governance enforces structured transitions between planning, RC, QA, release gates, and deployment. It manages milestones by validating version data from production sources and requiring iterative prompts for each phase transition to maintain traceability.

How do I coordinate parallel release tasks for QA, DevOps, and security teams?▼

Coordinating parallel release tasks is handled by spawning specialized subagents for qa-lead, devops-engineer, and security-engineer roles. Each subagent executes tasks concurrently with full operational context while the orchestrator logs decisions transparently for traceability.

Can I use release orchestration for multiplayer game deployments with network programming needs?▼

Release orchestration for multiplayer game deployments is supported through an optional network-programmer role within the pipeline. This role integrates alongside the producer and community-manager to address multiplayer-specific contexts during the phase-gated deployment process.

How do I generate changelogs and record decisions during a software release?▼

Generating changelogs and recording decisions during a software release is achieved through the pipeline's end-to-end lifecycle support. It infers version data, generates changelogs automatically, and logs full analysis from phase transitions for complete traceability.

Do I need to provide version and milestone data before starting release orchestration?▼

You need to provide the target version and milestone status to initialize the release orchestration pipeline. The orchestrator loads operational instructions and validates this milestone and version data against production sources before progressing the build.