team-release

End-to-end game release orchestration coordinates release-manager, qa-lead, devops-engineer, and producer subagents across structured phases. It moves builds from candidate to deployment by delegating planning, build integration, quality gates, and launch communications through a phase-based pipeline.

A go/no-go decision gate is an enforced user approval point within the release pipeline. The orchestration pauses at critical phase transitions, prompting the user via AskUserQuestion to explicitly approve or halt progression before downstream deployment actions proceed.

Generating release artifacts like checklists and patch notes is handled automatically during release orchestration. The pipeline coordinates subagents to track phase completion, compile changelogs, and produce formatted patch notes alongside deployment approvals.

Coordinating QA quality gates and localization within a single release workflow is supported natively. The pipeline delegates validation tasks to a qa-lead subagent and integrates localization steps before enforcing user approvals at the final launch communications phase.

Release orchestration here requires no external devops pipeline dependencies. It internally simulates the devops-engineer role through phase-driven subagent delegation, enforcing go/no-go approvals and generating artifacts without integrating external CI/CD platforms.

Phase-based release orchestration pipelines should not be used for rapid, continuous deployment cycles requiring no manual intervention. Its structured go/no-go approval gates and multi-role subagent delegation prioritize traceable, end-to-end game releases over automated, unattended patch delivery.