メニュー
Use when a game request is vague, contradictory, or under-specified and needs a production-ready brief.
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-requirements-brainstorm |
| description | Use when a game request is vague, contradictory, or under-specified and needs a production-ready brief. |
Turn the request into a requirement set that is specific enough to build a strong result.
Follow the gsp-orchestrator output strategy:
docs/game-studio/requirements.md and docs/game-studio/quality-target.md.Use:
./shared/templates/requirements-brief.md./shared/templates/quality-target.mdfirst-playable, polished-prototype, production-feature, or live-patch.For greenfield showcase work, do not reduce the ask to a bare minimum. Default to high-precision questioning rather than question minimization.