Menu
Use when game implementation should default to a builder-reviewer-verifier loop instead of one monolithic pass.
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-subagent-build-loop |
| description | Use when game implementation should default to a builder-reviewer-verifier loop instead of one monolithic pass. |
Turn a game build into a default multi-agent workflow: builder, reviewer, verifier. The goal is stronger and more stable output from one user prompt, not thrift.
Follow the gsp-orchestrator output strategy:
docs/game-studio/subagent-build-loop.md.For each meaningful build task or end-to-end slice:
gsp-build-review.gsp-playability-verifier.Parallel builders are allowed only when ownership is disjoint. Examples: core loop vs HUD, feedback vs content pass, gameplay slice vs menus. Do not parallelize builders that fight over the same files or architectural choices.
Do not claim completion after the builder finishes. Review and verification are expected to find problems.