team-release

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.

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.

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.

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.

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.

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.