Menu
Use when a requested game feature should land as a maintainable product-grade feature, not a prototype slice.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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-production-feature |
| description | Use when a requested game feature should land as a maintainable product-grade feature, not a prototype slice. |
Build or modify a feature so it can live in a serious codebase, not just impress in a quick demo.
A valid production feature usually includes:
Use:
./shared/checklists/production-feature-checklist.md./shared/checklists/production-code-checklist.mdFollow the gsp-orchestrator output strategy:
docs/game-studio/quality-target.md.