メニュー
Use when auditing responsiveness, rewards, failures, danger telegraphing, or state-transition feedback in a 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-feedback-audit |
| description | Use when auditing responsiveness, rewards, failures, danger telegraphing, or state-transition feedback in a game. |
Audit whether the game clearly responds to the player and communicates consequences.
Follow the gsp-orchestrator output strategy:
docs/game-studio/audit/audit-summary.md, docs/game-studio/audit/ux-findings.md, docs/game-studio/audit/scorecard.json.Use:
./shared/checklists/feedback-audit-checklist.md./shared/checklists/game-feel-pillars.md./shared/reference/audit-confidence-and-evidence.mdA feature that technically works but gives weak or missing feedback should be marked as partially complete, not fully complete.