メニュー
Use when auditing rollback, compatibility, corruption, or operational risks in a shipped or live-risky game.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when auditing structure, boundaries, coupling, or state-management risks in an existing game project.
Use when auditing UI sounds, reward/failure cues, danger cues, or audio feedback layering in a game.
Use when converting game audit findings into a structured multi-axis scorecard.
Use when choosing a backend profile for a game based on capabilities, project state, and quality target.
Use when reviewing a built or in-progress game against the locked brief before claiming completion.
Use when deciding development mode, quality target, task granularity, or refactor policy for game work.
| name | gsp-live-risk-audit |
| description | Use when auditing rollback, compatibility, corruption, or operational risks in a shipped or live-risky game. |
Audit shipped or high-risk projects before changes are proposed or applied.
Follow the gsp-orchestrator output strategy:
docs/game-studio/audit/audit-summary.md, docs/game-studio/audit/risk-register.md, docs/game-studio/audit/scorecard.json.Use:
./shared/checklists/live-risk-audit-checklist.md./shared/reference/project-state-and-risk.mdWhen risk is high, recommendations should bias toward small, reversible, well-isolated fixes.