Menu
Use when turning an approved game brief into verifiable implementation tasks matched to the chosen build mode.
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-implementation-plan |
| description | Use when turning an approved game brief into verifiable implementation tasks matched to the chosen build mode. |
Turn the approved build brief into an execution plan.
Use ./shared/templates/task-plan.md.
Follow the gsp-orchestrator output strategy:
docs/game-studio/plan.md.Do not use one default task size for all situations. Use the chosen development mode.
Unless the user explicitly wants a cheap or minimal pass, assume the plan should support:
For benchmark, showcase, or polished-prototype work, plan with this loop in mind instead of assuming one pass from build to done.
Do not produce fake progress tasks like “set up scaffolding” unless that scaffold immediately enables real implementation. Prefer tasks that end in a stronger running build.