菜单
Use when documenting reproducible game builds, signing, artifact promotion, distribution, staged rollout, rollback, crash diagnosis, matchmaking operations, live events, remote config, economy controls, support, or incidents.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when defining a game's player promise, product hypotheses, platform options, production model, vertical-slice evidence, commercial boundaries, or greenlight decision before detailed requirements.
Use when specifying testable game software requirements for player experience, gameplay state, platforms, multiplayer, saves, content, performance, accessibility, telemetry, security, builds, release, or live operations.
Use when designing game client, authoritative state, engine integration, content, saves, multiplayer backend, platform adapters, telemetry, security, build, and live-operations architecture from an approved game SRS.
Use when turning approved game requirements and architecture into implementable Unity, Godot, Unreal, Apple-native, multiplayer, content-pipeline, build, and telemetry work packages with code and asset contracts.
Use when planning game QA, playtesting, balance, deterministic simulation, save migration, multiplayer network conditions, device performance, accessibility, localisation, security, certification, and release-candidate evidence.
Use when assembling or reviewing game greenlight, milestone, release, rights, security, player-research, build, test, live-operations, and independent-replication evidence without inflating capability claims.
| name | 22-game-release-and-live-operations-runbook |
| description | Use when documenting reproducible game builds, signing, artifact promotion, distribution, staged rollout, rollback, crash diagnosis, matchmaking operations, live events, remote config, economy controls, support, or incidents. |
| metadata | {"portable":true,"compatible_with":["claude-code","codex"]} |
| Artefact | Source or provider | Required? | Behaviour when missing |
|---|---|---|---|
| Artefact, checksum, symbols, manifest, signing custody, channels and rollback | Build, QA and platform owners | Yes | Stop promotion. |
| Data/economy/ad config, privacy/child treatment, capacity, support and communications | Specialist owners | Conditional | Disable or block affected live scope. |
| Artefact | Consumer | Acceptance condition |
|---|---|---|
| Game release/liveops runbook | Release, operations and support | Artefact, steps, signals, owners, rollback and communications are executable. |
| Evidence | Reviewer | Acceptance condition |
|---|---|---|
| Promotion/rehearsal ledger | Release approver | Checksums, approvals, failures and rollback proof are retained. |
Read and search are allowed. Signing, submission, production config, messaging or rollback require authorised operators.
Return a qualified dry run, mark unavailable checks not assessed, and keep promotion blocked.
| Choice or condition | Action | Failure or risk avoided |
|---|---|---|
| Checksum differs | Reject artefact. | Untested promotion. |
| Threshold breaches | Halt or roll back. | Expanded harm. |
| Live change mutates state | Simulate, version and rehearse reversal. | Corruption. |
