菜单
Use when auditing whether delivered features actually match the promised scope and quality target.
用 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-scope-completeness-audit |
| description | Use when auditing whether delivered features actually match the promised scope and quality target. |
Audit what the project is supposed to be, what it currently is, and where scope or completeness assumptions are misleading.
Follow the gsp-orchestrator output strategy:
docs/game-studio/audit/audit-summary.md, docs/game-studio/audit/scorecard.json, docs/game-studio/audit/repair-roadmap.md.Use:
./shared/checklists/scope-completeness-audit-checklist.md./shared/reference/scope-tiers.md./shared/reference/quality-targets.mdfirst-playable, polished-prototype, production-feature, live-patch)