← ClaudeAtlas

game-brieflisted

Use when someone is planning a Unity 6 mobile game before generating or coding it or asks what to prepare before code, wants a game brief, pitch, MVP list or pillars, or asks whether a game's scope has crept or whether a new feature still fits.
whinstudio/skills · ★ 0 · AI & Automation · score 66
Install: claude install-skill whinstudio/skills
# game-brief Two modes. `brief` writes **one file, `design/brief.md`, that fits one screen**. `scope-check` compares the project with that file and writes nothing. Pick the mode from the argument or the request; "should we add X" or "has scope crept" means `scope-check`. ## Mode: brief The output is the filled template below and nothing else: no other documents, no analysis before or after it. Tell the user the file path and the three `(guess)` markers you are least sure of. **Where.** Normally `design/brief.md` (create `design/` if missing). If there is no Unity project yet, write `brief.md` in the current folder and tell the user to move it to `design/brief.md` after `game-new-project`. If `design/brief.md` already exists, show what would change and ask before overwriting. **Asking.** From the request, fill everything you can. Ask only what cannot be inferred, in one short message with at most four questions. If the genre or the camera (2D or 3D) cannot be inferred, ask about it even when the user says "go ahead". Everything else still open becomes a guess marked `(guess)` in the file so the user can correct it. Do not ask for a field you can reasonably propose. **Template** for the brief (at most 60 lines): ```markdown # <Working title> **Pitch:** <one sentence> ## Core loop - <do> -> <get> -> <why again> (2-4 bullets) ## Player goal and fail <what the player wants; how a run ends. 1-2 lines, testable> ## MVP (7 items at most) - <feature without which this is no