菜单
Use when game work is too large for one session and needs a guarded external build/verify/repair loop.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | gsp-rolling-supervisor |
| description | Use when game work is too large for one session and needs a guarded external build/verify/repair loop. |
Push a game project through repeated autonomous passes without letting one long context rot into uselessness.
Follow the gsp-orchestrator output strategy:
docs/game-studio/rolling-supervisor.md and docs/game-studio/rolling/state.json.Use:
./shared/templates/rolling-supervisor-plan.md./shared/reference/rolling-supervisor-architecture.md./schemas/rolling-state.schema.json./schemas/session-result.schema.jsonTypical graph:
The supervisor belongs outside the plugin runtime. The plugin defines the contracts; an external Python supervisor executes them.
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.