team-release
Argument check: If no version number is provided:
- Read
production/session-state/active.mdand the most recent file inproduction/milestones/(if they exist) to infer the target version. - 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?" - If no version is discoverable: use
AskUserQuestionto 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-facing messaging
- producer — Go/no-go decision, stakeholder communication, scheduling
More from donchitos/claude-code-game-studios
balance-check
Analyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-related data or design. Use when user says 'balance report', 'check game balance', 'run a balance check'.
125brainstorm
Guided game concept ideation — from zero idea to a structured game concept document. Uses professional studio ideation techniques, player psychology frameworks, and structured creative exploration.
95playtest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
94team-narrative
Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design.
92estimate
Estimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels.
81asset-audit
Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.
78