What problem does it solve? Coordinating a software release involves many roles—release management, QA, DevOps, and production decisions—and doing it manually leads to missed steps, unclear sign-offs, and inconsistent quality gates. This Skill structures the entire release as a phased pipeline with delegated subagents and explicit approval checkpoints. ## Core Features & Use Cases - Phased Release Pipeline: Runs seven phases from release planning through post-release monitoring, with user approval required at each phase transition. - Role-Based Delegation: Spawns release-manager, qa-lead, devops-engineer, and producer subagents via the Task tool, running independent phases in parallel where possible. - Quality Gates and Go/No-Go: Enforces regression testing, build verification, localization and performance sign-off, and a formal go/no-go decision before deployment. - Use Case: When your milestone is complete and you need to ship version 2.4, invoke this Skill to cut the release branch, run the regression suite, collect sign-offs, deploy to production, and generate the release report. ## Quick Start Invoke the team-release skill with a version number such as "/team-release 2.4.0" to start the guided release pipeline.
