القائمة
Use when reviewing a built or in-progress game against the locked brief before claiming completion.
التثبيت باستخدام 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 deciding development mode, quality target, task granularity, or refactor policy for game work.
Use when backend uncertainty remains and only a narrow two- or three-option compare is needed.
| name | gsp-build-review |
| description | Use when reviewing a built or in-progress game against the locked brief before claiming completion. |
Default review stage between implementation and runtime verification. Catch shape drift, weak scope decisions, and fake-complete output before verifier time is spent.
Follow the gsp-orchestrator output strategy:
docs/game-studio/build-review.md.For each issue, report:
This is not the runtime verifier. Review the implementation against the concept, brief, and plan so the verifier receives a build worth testing.