菜单
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.
用 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 documenting reproducible game builds, signing, artifact promotion, distribution, staged rollout, rollback, crash diagnosis, matchmaking operations, live events, remote config, economy controls, support, or incidents.
| name | 30-game-delivery-evidence-and-greenlight-pack |
| description | 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. |
| metadata | {"portable":true,"compatible_with":["claude-code","codex"]} |
| Artefact | Source or provider | Required? | Behaviour when missing |
|---|---|---|---|
| Brief, traces, builds, manifests, risks and approvals | Product, engineering, QA and governance | Yes | Stop the gate and record missing evidence. |
| Player, learning, culture/rights, wellbeing, ads/privacy, commercial, security, access, platform and independent evidence | Specialist owners | Conditional | Mark claim not assessed or fail its gate. |
| Artefact | Consumer | Acceptance condition |
|---|---|---|
| Game evidence and greenlight pack | Sponsor, client, release board and auditor | Decisions link to inspectable evidence, gaps and approval. |
| Evidence | Reviewer | Acceptance condition |
|---|---|---|
| Evidence manifest and gate ledger | Independent reviewer | Identity, provenance, result, limitation and disposition are explicit. |
Read and search are allowed; review is read-only. Editing evidence, waiving blockers or approving release requires authority.
Return the narrowest qualified report, mark unavailable checks not assessed, and never infer a pass.
| Choice or condition | Action | Failure or risk avoided |
|---|---|---|
| Build identity mismatches | Fail release gate. | Untested approval. |
| Prose exists without execution | Withhold proof credit. | Inflated maturity. |
| Waiver lacks expiry | Reject waiver. | Permanent exception. |
