菜单
Use before major game work to classify the repo as greenfield, prelaunch, shipped, or live-risky.
用 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-project-state-assessment |
| description | Use before major game work to classify the repo as greenfield, prelaunch, shipped, or live-risky. |
Determine what kind of project this is before choosing scope, architecture, or task sizing.
Follow the gsp-orchestrator output strategy:
docs/game-studio/project-state.md using ./shared/templates/project-state-assessment.md.Use:
./schemas/project-state.schema.jsonLook for evidence such as:
If critical status cannot be inferred, ask only a few decisive questions. Do not ask long interviews.