unity-game-brieflisted
Install: claude install-skill tipoLi5890/unity-dev-skills
# unity-game-brief — the spec comes last
An idea arrives as one sentence, and the expensive mistake is to answer it with a plan. A plan is
a guess about how something will feel, written in the one form nobody can react to.
> **The first hour ends with a human playing something, not reading something.**
> One page, one locked image, one derived proposal, one playable interaction — in that order,
> because each is worthless before the one above it.
## Request → where to start
| The request | Go to |
|---|---|
| "I want to make a game where…", "here's my game idea", "write the brief" | §1 |
| The look, "lock the art direction" | §2 |
| "preview it before code", see the game before it is built | §2b |
| "propose an architecture" | §3 |
| "is this ready to build", a non-negotiable to test | §4 |
| "what should we build first" | §5 |
| "new feature — where do we start" | §1's new-feature variant (`reference/experience-brief.md`) |
| Existing files, unsure where you are | §0 |
The order is not a ritual. Constants written before the look settles get re-tuned when it does; an
architecture chosen before the constraints are written is a preference nobody can argue with; a
feature list written before anyone has played is a list of guesses, each of which will be built.
## 0. Where in the first hour are you?
```bash
ls GAME_BRIEF.md ARCHITECTURE_PROPOSAL.md ART_DIRECTION.md 2>/dev/null
grep -m1 '^Status:' ART_DIRECTION.md 2>/dev/null
grep -rln 'Situation\|\[PROBE\]' Assets --include