Turn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Skill Test Spec: /prototype
Skill Summary
/prototype [concept] [--path html|engine|paper] [--review full|lean|solo] [--spike] runs a throwaway concept prototype before GDDs are written. It first
confirms intent with AskUserQuestion (Prototype this concept / Skip — concept
already proven / Mid-production spike), forms a falsifiable hypothesis ("If the
player [does X], they will feel [Y] — we will know this is true if [Z]") and asks
for the riskiest assumption. It picks an HTML, Engine or Paper path (genre table,
recommendation pre-stated), presents a 3–5 bullet plan, asks to record it as a
checkpoint in production/session-state/active.md, then asks "May I create the prototype
directory at prototypes/[concept-name]-concept/ and begin implementation?".
Every prototype file starts with a PROTOTYPE - NOT FOR PRODUCTION header in
that file's own comment syntax (# in GDScript and Python, // in C#, C++ and
JavaScript, <!-- --> in HTML and Markdown), and standards are intentionally
relaxed.
After a one-question-at-a-time debrief, it fills
.claude/docs/templates/prototype-report.md, asks to write
prototypes/[concept-name]-concept/REPORT.md and add its row to
prototypes/index.md (one ask naming both). Verdicts are PROCEED / PIVOT / KILL. PIVOT writes a
PIVOT-NOTE.md; KILL runs a five-item soundness check and appends to
prototypes/GRAVEYARD.md. In full review mode creative-director reviews the
result via CD-PLAYTEST and answers APPROVE / CONCERNS / REJECT: APPROVE keeps
the recommendation; CONCERNS go to the user, who decides (Revise / Accept /
Discuss); REJECT means a PROCEED cannot stand — the user chooses PIVOT or KILL,
and REPORT.md records the director's reason. A NOT ASSESSED answer (the director
lacked an input) is never an approval. --spike replaces the
whole flow with a ~4-hour spike that asks before creating its folder, asks
before writing SPIKE-NOTE.md and clearing the spike from active.md, and has
no CD gate and no PROCEED/PIVOT/KILL.
Static Assertions (Structural)
Checked against the SKILL.md by /skill-test spec — no fixture needed.
- Has required frontmatter fields:
name,description,argument-hint,user-invocable,allowed-tools - Has ≥2 phase headings
- Contains verdict keywords: PROCEED, PIVOT, KILL, NOT ASSESSED (a prototype nobody has played)
- Contains "May I create" / "May I write" language before creating the prototype directory and the report
- Has a next-step handoff per verdict (PROCEED →
/design-review,/gate-check,/map-systems,/design-system; PIVOT →/prototypeor/brainstorm; KILL →/brainstorm)
Director Gate Checks
- Full mode: CD-PLAYTEST —
creative-directorreceives the REPORT.md content, the hypothesis and the pillars (fromdesign/gdd/game-concept.md, or the pitch and "what they feel" line fromdesign/game-brief.md) and returns APPROVE / CONCERNS / REJECT, or NOT ASSESSED when it lacked an input. APPROVE → the recommendation stands; CONCERNS → shown with the recommendation, and the user decides (Revise / Accept / Discuss); REJECT → a PROCEED cannot stand: the user chooses PIVOT or KILL, and REPORT.md records the director's reason; NOT ASSESSED → never an approval: the missing input is named, and the gate is re-run or the review recorded as NOT ASSESSED. If neither document exists: "CD-PLAYTEST skipped — game pillars not yet defined at concept prototype stage." - Lean mode: skipped — "CD-PLAYTEST skipped — Lean mode."
- Solo mode: skipped — "CD-PLAYTEST skipped — Solo mode."
- Spike mode: no CD gate and no phase gate, in any review mode.
Fixture Defaults
Every case's project.yaml sets modes.rigor: minimal and
modes.automation: collaborative, with no project.local.yaml, unless its own
Fixture says otherwise. Rules: studio-tests/CLAUDE.md §
Fixture defaults.
Test Cases
Case 1: Happy Path — Engine Prototype, PROCEED
Fixture:
design/gdd/game-concept.mddescribes a 2D platformer;project.yamlhasengine.name: Godotandengine.language: GDScriptprototypes/has nograpple-hook-concept/- Review mode:
solo;modes.workflow: standard(pinned: unset resolves to minimal, which routes PROCEED to/create-storiesand/dev-storyinstead of the step 7 list — Case 6 covers that route) - In the debrief the user reports the hypothesis CONFIRMED and answers PROCEED
Input: /prototype grapple-hook traversal
Expected behavior:
AskUserQuestionconfirms intent; user picks "Prototype this concept"- Skill states a falsifiable hypothesis in the If / feel / know-if form and asks for the riskiest assumption
- Path widget pre-states an Engine recommendation (traversal feel is the hypothesis)
- Plan is presented and confirmed, with the ask naming
production/session-state/active.md; the checkpoint is written there - Skill asks "May I create the prototype directory at
prototypes/grapple-hook-concept/and begin implementation?"; every GDScript file it writes starts with# PROTOTYPE - NOT FOR PRODUCTION(GDScript comments use#; a//header would not parse) - Debrief questions are asked one at a time; report drafted from
.claude/docs/templates/prototype-report.md; "May I write this report toprototypes/grapple-hook-concept/REPORT.mdand add its row toprototypes/index.md?"; a row is appended toprototypes/index.md - Note "CD-PLAYTEST skipped — Solo mode."; PROCEED routes to
/design-review,/gate-check,/art-bible,/map-systems,/design-system,/review-all-gdds
Assertions:
- The hypothesis is falsifiable, with a measurable signal
- Engine is recommended in the path prompt before the user chooses
- The directory ask names
prototypes/grapple-hook-concept/and comes before any prototype file is written - Every prototype script carries the
PROTOTYPE - NOT FOR PRODUCTIONheader as a#comment, never//; no file is written under the code root - REPORT.md is written only after its ask, that ask also names
prototypes/index.md, and the index gains a row with verdict PROCEED - PROCEED next steps include
/map-systemsand/design-system
Case 2: PIVOT — Carry-Forward Note Written
Fixture:
- A paper prototype of
trade-routeshas just been debriefed - User answers PIVOT: the route planning was engaging, the upkeep maths was not
- Review mode:
solo
Input: /prototype trade-routes --path paper
Expected behavior:
- Paper path writes
prototypes/trade-routes-concept/rules.mdandplay-log.mdafter the directory ask - REPORT.md is written after its ask with verdict PIVOT
- Skill asks, one at a time: "What specifically worked in this prototype that we should preserve…?" and "What is the single most important thing to change?"
- Skill asks "May I write this to
prototypes/trade-routes-concept/PIVOT-NOTE.md?" - The note holds the original hypothesis, what to keep, what to change and the
revised hypothesis; next steps are
/prototype [revised-concept]or/brainstorm [hint]
Assertions:
-
--path paperis honoured and producesrules.mdandplay-log.md - The two carry-forward questions are asked separately
- "May I write" names
PIVOT-NOTE.mdbefore it is written - The note contains a revised hypothesis
- Next steps offer
/prototypefor the revised concept or/brainstorm
Case 3: KILL — Soundness Check and Graveyard Entry
Fixture:
- An HTML prototype of
procedural-dialoguehas been debriefed - User answers KILL; the debrief shows testers never understood the core action after 2 playtests, no fun moment was observed, and the concept only worked when the developer explained it
Input: /prototype procedural-dialogue --path html
Expected behavior:
- REPORT.md is written after its ask with verdict KILL
- Skill runs the five-item KILL checklist; 3 items apply, so the verdict is sound
- Skill asks "May I append this concept to
prototypes/GRAVEYARD.md?" - The entry has Kill reason, What worked, What failed and Next time, with a specific kill reason (not "it was boring")
- Next step:
/brainstorm openor/brainstorm [new-hint]
Assertions:
- The KILL checklist is applied, with the 2+ rule deciding soundness
- "May I append" names
prototypes/GRAVEYARD.mdbefore writing - The graveyard entry has all four fields and a specific kill reason
- Next steps route to
/brainstorm
Case 4: Spike Mode — No Debrief, No Gate, No PROCEED/PIVOT/KILL
Fixture:
- Project is in Production
- Review mode:
full;modes.workflow: standard(pinned: unset resolves to minimal, whose spike note andactive.mdwording Case 7 covers) production/sprints/sprint-004.mdis the current sprint andactive.mdshows it
Input: /prototype rope-physics --spike
Expected behavior:
- Skill skips Phases 1–9 and runs Spike Mode
- Asks for the spike question in plain text: "Can we [do X] using [approach Y]?"
- Path widget as in Phase 3; scope limited to 2–3 bullets; ~4-hour cap
- Asks "May I create
prototypes/rope-physics-spike-[date]/and build the spike there?" before writing any spike file - Asks "Did the spike answer the question? YES or NO, and why in one sentence."
- Asks once, naming both files, "May I write
prototypes/rope-physics-spike-[date]/SPIKE-NOTE.mdand clear the spike fromproduction/session-state/active.md?"; then writes the note (question, result YES / NO / PARTIAL, what to do next) and updatesactive.md - The note's "what to do next" offers: add to the current sprint / investigate
further / abandon the idea.
active.mdis cleared back to the current sprint state
Assertions:
- The intent widget and hypothesis/debrief phases are skipped
- The spike folder is created only after its ask
-
SPIKE-NOTE.mdandactive.mdare written only after an ask that names both - Output is
SPIKE-NOTE.mdin a-spike-[date]folder, not a REPORT.md - No CD-PLAYTEST spawn or skip note, even though review mode is
full - No PROCEED / PIVOT / KILL verdict is issued
- At
standard, the note's next-step options say "add to current sprint", andactive.mdreturns to the current sprint state
Case 5: Director Gate — CD-PLAYTEST by Review Mode and Pillars
Fixture:
- A concept prototype has been built and REPORT.md written with a PROCEED recommendation
- Run A:
--review full,design/gdd/game-concept.mdexists with pillars;creative-directorreturns REJECT — the core fantasy is not present; the user, asked PIVOT or KILL, picks PIVOT - Run B:
--review full, neithergame-concept.mdnordesign/game-brief.mdexists - Run C:
--review lean
Input: /prototype [concept] --review [mode]
Expected behavior:
- Run A:
creative-directoris spawned for CD-PLAYTEST with the REPORT.md content, hypothesis and pillars. Its REJECT means the PROCEED recommendation cannot stand: the skill asks the user to choose PIVOT or KILL (it does not pick for them), the user picks PIVOT, and after an ask naming REPORT.md andprototypes/index.mdthe report records the director's verdict and reason and the final PIVOT recommendation; Phase 9 then runs the PIVOT route - Run B: no spawn; note "CD-PLAYTEST skipped — game pillars not yet defined at concept prototype stage."
- Run C: no spawn; note "CD-PLAYTEST skipped — Lean mode."
Assertions:
- Run A spawns
creative-directorfor CD-PLAYTEST after REPORT.md is written - Run A: the director's verdict is read as one of APPROVE / CONCERNS / REJECT, not as a PROCEED / PIVOT / KILL of its own
- Run A: after the REJECT, PROCEED is not kept; the user is asked to choose PIVOT or KILL
- Run A's final recommendation is the user's PIVOT, and REPORT.md records it with the director's reason
- Run B skips with the "game pillars not yet defined" note instead of spawning without pillars
- Run C skips with the Lean-mode note
- No other director gate is spawned
Case 6: NOT ASSESSED (Unplayed) and the workflow: minimal PROCEED Route
Fixture:
- Run A: the prototype was built this session but nobody has played it yet
- Run B: a PROCEED recommendation,
project.yamlhasmodes.workflow: minimal
Input: /prototype [concept]
Expected behavior:
- Run A: with no fun evidence yet, PROCEED/PIVOT/KILL are all unreachable; the
skill reports NOT ASSESSED and stops rather than guessing, naming "play it,
then run
/prototype [same concept]again" as the next step - Run B: Phase 9's PROCEED route offers
/create-stories(from the brief) then/dev-storyon the first story, not the GDD//map-systems//art-biblepath
Assertions:
- Run A's verdict is NOT ASSESSED, not a guessed PROCEED/PIVOT/KILL
- Run A's report and
prototypes/index.mdrow both read NOT ASSESSED until a playtest happens - Run B's recommended path is the
workflow: minimalroute (/create-stories,/dev-story), not thestandard/fullGDD pipeline
Case 7: Spike Mode at workflow: minimal — the build order, not a sprint
Fixture:
project.yaml:modes.workflow: minimal(pinned: this case tests theminimalwording, the opposite of Case 4); review modefull- No
production/sprints/directory.design/game-brief.mdlists a build order; the story in progress isproduction/epics/core/story-002.md(Status: In Progress), andproduction/session-state/active.mdnames it as the current task - The user answers YES to the spike question
Input: /prototype rope-physics --spike
Expected behavior:
- The spike runs as in Case 4, with the same asks: the spike folder, then one ask
naming
SPIKE-NOTE.mdandactive.md SPIKE-NOTE.mdholds the question tested, the result (YES / NO / PARTIAL) and what to do next: add the mechanic to the brief's build order / investigate further / abandon the idea. It does not offer "add to current sprint"active.mdis updated to clear the spike and return to the story in progress (story-002), not to a sprint state- No CD gate and no PROCEED / PIVOT / KILL
Assertions:
- The note's next-step options name the brief's build order instead of the current sprint
- After the write,
active.mdnames story-002 as the current task and no sprint - The spike folder and the note-and-
active.mdwrite each follow an ask that names the files - No sprint file is created or referenced
- No CD-PLAYTEST spawn or skip note and no PROCEED / PIVOT / KILL verdict is issued
Protocol Compliance
- Confirms intent with
AskUserQuestionbefore building (unless--spike) - Forms a falsifiable hypothesis and stops if the concept is too vague to form one
- Presents the plan and gets confirmation before building
- Asks before creating
prototypes/[concept-name]-concept/and before writing REPORT.md (with itsprototypes/index.mdrow), PIVOT-NOTE.md or GRAVEYARD.md - In spike mode, asks before creating the spike folder and before writing
SPIKE-NOTE.mdandactive.md - Keeps prototype files under
prototypes/, each with thePROTOTYPE - NOT FOR PRODUCTIONheader in its own comment syntax - Applies the review mode before CD-PLAYTEST and prints the skip note when skipped
- Ends with the per-verdict next steps
Coverage Notes
- "Skip — concept already proven" (records the evidence, suggests
/map-systemsor/design-system, and stops) is not tested. - A concept too vague to form a hypothesis (skill stops and asks the user to narrow it) is covered only by protocol compliance.
- Reading a prior
PIVOT-NOTE.mdon the next run to seed the revised hypothesis is not tested. - The engine-path multi-turn fix loop and the 2-hour sunk-cost rule need a live run to verify.
- CD-PLAYTEST APPROVE (the recommendation stands), CONCERNS (the user decides: Revise / Accept / Discuss), REJECT on a PIVOT or KILL recommendation (it stands) and NOT ASSESSED (never an approval) are not separately tested.