菜单
Use when a game project is expanding too broadly and needs scope protection without losing the core goal.
用 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-guard |
| description | Use when a game project is expanding too broadly and needs scope protection without losing the core goal. |
Keep scope under control while preserving the value of the request.
Do not equate “scope control” with “remove everything interesting.”
Follow the gsp-orchestrator output strategy:
docs/game-studio/plan.md or docs/game-studio/build-strategy.md.Use gsp-scope-profile early to define the intended scope. This skill protects it later.