team-release

**Argument check:** If no version number is provided: 1. Read `production/session-state/active.md` and the most recent file in `production/milestones/` (if they exist) to infer the target version. 2. If a version is found: report "No version argument provided — inferred [version] from milestone data. Proceeding." Then confirm with `AskUserQuestion`: "Releasing [version]. Is this correct?" 3. If no version is discoverable: use `AskUserQuestion` to ask "What version number should be released? (e.g., v1.0.0)" and wait for user input before proceeding. Do NOT default to a hardcoded version string. When this skill is invoked, orchestrate the release team through a structured pipeline. **Decision Points:** At each phase transition, use `AskUserQuestion` to present the user with the subagent's proposals as selectable options. Write the agent's full analysis in conversation, then capture the decision with concise labels. The user must approve before moving to the next phase. ## Team Composition - **release-manager** — Release branch, versioning, changelog, deployment - **qa-lead** — Test sign-off, regression suite, release quality gate - **devops-engineer** — Build pipeline, artifacts, deployment automation - **security-engineer** — Pre-release security audit (invoke if game has online/multiplayer features or player data) - **analytics-engineer** — Verify telemetry events fire correctly and dashboards are live - **community-manager** — Patch notes, launch announcement, player-faci...