next-step
Skill39k starsChanged 7 days agoMITView on GitHub
Names the one next step: make a game, change it after play, grow it, or the next studio-mode step. Use when asked what to do next, or stuck.
13 other projects use a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- dotslashsimran/simcrafttheir own version, first seen Nov 8, 2026
- scoobydrew83/skillstheir own version, first seen Nov 3, 2026
- Ovich/charrettetheir own version, first seen Nov 1, 2026
- spongetimblin/claude-skill-librarytheir own version, first seen Oct 25, 2026
- Ovich/swarmstormtheir own version, first seen Oct 25, 2026
- SHYXIN/skillstheir own version, first seen Oct 11, 2026
Who's talking about Donchitos/Claude-Code-Game-Studios
- Claudical“그림 파일 하나 없이 아이디어 한 줄로 만든 게임 | Claude Code Game Studios”YouTube · Oct 27, 2026 · 18k views
- Matheus Battisti“Criar jogos com IA ficou ABSURDO! (Claude Code com 49 agentes)”YouTube · Nov 2, 2026 · 5.6k views
- Chrono IT Channel“Letting 49 AI Agents Run a "Game Studio" — Claude Code Game Studios”YouTube · May 30, 2026 · 1.8k views
- AutomateNow“Claude Code Game Studios: Free Repo Turns Claude Code Into a 49-Agent Game Studio #Shorts”YouTube · Oct 30, 2026 · 1.4k views
- SkipCI“Claude Code Game Studios: 49 AI Agents, 74 Commands, Ranked Last in Blind Test”YouTube · Oct 31, 2026 · 1.4k views
The biggest 5 of 35 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 35
Talked about on YouTube and Bluesky (35 times).
On YouTube · 23
- Oct 27, 2026그림 파일 하나 없이 아이디어 한 줄로 만든 게임 | Claude Code Game Studios — Claudical18k views · 9 comments
- Nov 2, 2026Criar jogos com IA ficou ABSURDO! (Claude Code com 49 agentes) — Matheus Battisti - Hora de Codar5.6k views · 8 comments
- May 30, 2026Letting 49 AI Agents Run a "Game Studio" — Claude Code Game Studios — Chrono IT Channel1.8k views · 3 comments
- Oct 30, 2026Claude Code Game Studios: Free Repo Turns Claude Code Into a 49-Agent Game Studio #Shorts — AutomateNow1.4k views · 3 comments
- Oct 31, 2026Claude Code Game Studios: 49 AI Agents, 74 Commands, Ranked Last in Blind Test — SkipCI1.4k views · 4 comments
18 more on YouTube
- Oct 31, 2026Claude Code Game Studios: một phiên làm việc, cả studio game — Anh Nguyen Quoc (C5)813 views
- Oct 28, 2026Turn Claude Code Into a Game Studio (Part 1) — AI → AGI → ASI801 views
- Apr 16, 2026Donchitos/Claude-Code-Game-Studios - Gource visualisation — Gourcer740 views
- Oct 15, 2026Claude Code Game Studios GitHub Overview: How Sequential AI Roles Manage Game Projects — Alex Hitt734 views
- Oct 31, 2026Claude Code Game Studios: one session, a full game studio — GitHub Unboxed609 views
- Oct 28, 20261 Claude Code Chat = A Whole Game Studio 🤯 — Gadget Drop282 views · 1 comment
- Oct 15, 2026Claude-Code-Game-Studios: virtual game studio with a single chat — Next Horizon191 views · 1 comment
- Oct 16, 2026Claude Code Game Studios: 49 AI Agents to Run Your One-Person Game Studio — Not That Number188 views
- Oct 29, 2026Donchitos/Claude-Code-Game-Studios — Turn Claude Code into a full game dev studio — 49 AI agents, 72 — Git Radar104 views
- Nov 1, 2026Make a game solo like a whole studio? 49 agents in Claude Code | GitHub Radar #12 #Shorts — KIEU STUDIO54 views · 1 comment
- Oct 22, 2026Claude Code como estudio de VIDEOJUEGOS 🎮 49 agentes: ¿mito o verdad? (Game Studios) — BarbuPrime IA | Claude Code Vs Codex32 views · 1 comment
- Oct 31, 2026Donchitos/Claude-Code-Game-Studios is trending on GitHub. — Nexbit Studio18 views
- Oct 30, 2026게임 개발 도와주는 AI? Claude Code Game Studios로 할 수 있는 것 — 딴삽스튜디오12 views
- Oct 29, 2026Claude-Code-Game-Studios ⭐ 28601 | +538 today #github #opensource #shell — Git Radar12 views
- Nov 3, 2026Claude Code Just Became a FULL Game Development Studio 🎮🤖 — The Clever Machine10 views
- Nov 2, 2026Claude Code as a 49-Agent Game Studio (and Why More Docs Lost) — GitHub AI Repo10 views
- Oct 31, 2026【AIが49人のゲーム会社に】Claude Code Game Studiosの入れ方と全6ステップ|作らせたいゲーム募集 — にくまるOSS研究所8 views
- Nov 3, 2026【Claude-Code-Game-Studios】49エージェントの"ゲーム開発スタジオ"に1画面ゲームを頼んだらminimalは38分で遊べる物・standardは8ドルで設計書9本 — さつきのOSS研究室4 views · 1 comment
On Bluesky · 12
- Apr 19, 2026【GitHubトレンド調査】 Claude Codeをゲーム開発スタジオに変貌させる「Claude-Code-Game-Studios」が登場。… — @woody-ai-tools.bsky.social10 likes and reposts
- Apr 15, 2026🎉 Celebrating! 🎉 (500+ new stars) 📦 Donchitos / Claude-Code-Game-Studios ⭐ 9,860 (+523) 🗒 Shell Turn Claude Code into a full game dev… — @github-trending.bsky.social4 likes and reposts · 1 reply
- May 19, 2026This is the project in question. github.com/Donchitos/Cl... Most of these projects feel like toys or performance art masquerading as useful… — @impossible.bsky.social3 likes and reposts · 2 replies
- Apr 19, 2026🎉 Celebrating! 🎉 (500+ new stars) 📦 Donchitos / Claude-Code-Game-Studios ⭐ 13,024 (+828) 🗒 Shell Turn Claude Code into a full game dev… — @github-trending.bsky.social3 likes and reposts · 1 reply
- Nov 1, 2026Claude-Code-Game-Studios — Turn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination… — @thestackradar.bsky.social2 likes and reposts
7 more on Bluesky
- Nov 1, 2026An entire game dev studio in one Claude session? 🎮 Claude-Code-Game-Studios turns Claude Code into an AI production studio: 49 agents, 72… — @thestackradar.bsky.social1 likes and repost
- Oct 31, 2026今日のGitHubトレンド Donchitos/Claude-Code-Game-Studios Claude Codeのセッションを擬似的なゲーム開発スタジオとして運用するためのツールです。… — @dailygithubtrends.bsky.social1 likes and repost
- Apr 21, 2026https://github.com/Donchitos/Claude-Code-Game-Studios — @tom-doerr.bsky.social1 likes and repost
- Apr 1, 2026Un studio de 48 agents IA spécialisés dans Claude Code : hiérarchie complète (directors, leads, specialists), workflows automatisés et… — @camilleroux.com1 likes and repost
- Nov 2, 2026💎 Hidden Gem! 💎 (1000+ new stars) 📦 Donchitos / Claude-Code-Game-Studios ⭐ 33,084 (+1,380) 🗒 Shell Turn Claude Code into a full game… — @github-trending.bsky.social0 likes and reposts · 1 reply
- Oct 29, 2026🎉 Celebrating! 🎉 (500+ new stars) 📦 Donchitos / Claude-Code-Game-Studios ⭐ 28,645 (+538) 🗒 Shell Turn Claude Code into a full game dev… — @github-trending.bsky.social0 likes and reposts · 1 reply
- May 19, 2026It was this one: github.com/Donchitos/Cl... — @dphrygian.com0 likes and reposts · 1 reply
Used with
Projects with it also use simplify and interview.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Hugging FaceSkillsimplify
Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.
Also in 3 projects that use this
dazuckSkillinterview
Interview me about a plan to flesh out requirements before implementation. Asks non-obvious questions one at a time until all ambiguities are resolved.
Also in 3 projects that use this
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- bitwize-music-studio/claude-ai-music-skills★ 668same name
- dotslashsimran/simcraft★ 451same name
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- Ovich/charrette★ 18same name
- Ovich/swarmstorm★ 18same name
- SHYXIN/skills★ 6same name
- jordnlvr/MendixToolkit★ 2same name
- zahardev/aicontext★ 2same name
- jwd83/skills★ 1same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository82 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- design/CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- src/CLAUDE.mdCLAUDE.md
- studio-tests/CLAUDE.mdCLAUDE.md
- adoptSkill
- architecture-decisionSkill
- architecture-reviewSkill
- art-bibleSkill
- asset-auditSkill
- asset-specSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- bug-triageSkill
- changelogSkill
- code-reviewSkill
- consistency-checkSkill
- content-auditSkill
- create-architectureSkill
- create-control-manifestSkill
- create-epicsSkill
- create-storiesSkill
- cutSkill
- day-one-patchSkill
- design-reviewSkill
- design-systemSkill
- dev-storySkill
- estimateSkill
- gate-checkSkill
- helpSkill
- hotfixSkill
- launch-checklistSkill
- localizeSkill
- map-systemsSkill
- milestone-reviewSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- playtest-reportSkill
- project-settingsSkill
- project-stage-detectSkill
- propagate-design-changeSkill
- prototypeSkill
- qa-planSkill
- quick-designSkill
- regression-suiteSkill
- release-checklistSkill
- retrospectiveSkill
- reverse-documentSkill
- review-all-gddsSkill
- scope-checkSkill
- security-auditSkill
- settingsSkill
- setup-engineSkill
- skill-improveSkill
- skill-testSkill
- smoke-checkSkill
- soak-testSkill
- sprint-planSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
25 rules. 0 are common, 9 are distinctive, and 16 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
16
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 31
If no config block rendered, shell preprocessing is disabled.
- Very specific: line 38
Read .claude/docs/workflow-catalog.yaml.
- Very specific: line 46
After reading the catalog, list .claude/skills/*/SKILL.md to get the full list of installed skills.
- Distinctive: line 61
Only show this block if at least one uncataloged skill exists.
- Very specific: line 69
First, take
workflowfrom the config block above: If it is minimal, the project is on the minimal path, not the phase ladder: skip the … - Very specific: line 104
Read production/session-state/active.md if it exists — but only its STATUS and CHECKPOINT blocks (schema: …
- Very specific: line 133
Run it exactly as written, here and below: from the project root, with the relative path — no absolute path, no cd, no 2>&1.
- Very specific: line 148
Do not re-derive any of this by searching the files yourself.
- Very specific: line 161
When the current stage is production, check for production/sprint-status.yaml before doing any glob-based story checks.
- Very specific: line 204
When the person asks for a change to a made game, or says they love or hate it, → Next up is /prototype with their words, whatever else …
- Very specific: line 210
no match, and the code root holds fewer than 10 source files → no game yet: → Next up is /prototype (make a game you can play), with …
- Very specific: line 216
no match, and 10 or more source files → /setup-engine, as before
- Distinctive: line 301
Every one of them still runs if the user asks for it.
- Distinctive: line 324
If the user provided an argument (e.g.
- Very specific: line 327
A design with nothing to play: When design/gdd/ holds a .md file and Glob finds no prototypes/*/index.html, check engine.name in …
- Very specific: line 330
No engine set, or web: → Next up is a playable first, /prototype built from their concept doc (/prototype design/gdd/game-concept.md.
- Very specific: line 344
If active.md shows an active task or epic:
- Distinctive: line 352
Keep it short and direct. This is a quick orientation, not a report.
- Very specific: line 382
At
minimal: use this shape instead — no phase label, no gate line. - Distinctive: line 415
If a step has no command (e.g.
- Distinctive: line 426
After the current stage's steps, check if the user is likely approaching a gate:
- Very specific: line 427
If all required steps in the current stage are complete (or nearly complete), add: "You're close to the [Current] → [Next] gate.
- Distinctive: line 429
If multiple required steps remain, skip the gate warning — it's not relevant yet.
- Distinctive: line 435
After the recommendations, if the user seems stuck or confused, add:
- Distinctive: line 451
Only show this if the user's input suggested confusion (e.g.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Next Step — What Do I Do Next?
This skill is read-only — it reports findings but writes no files.
This skill figures out where the project is and tells you the one thing to do
next. The main path comes first: make a game (/prototype), change it after you
play it, then grow it into a project you keep building. The stages below, with
their design documents, agents, team-* pipelines and stage gates, are studio
mode, the path at workflow standard or full. It is lightweight — not a full
audit. For a full gap analysis, use /project-stage-detect.
Live Project State
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys project.stage,workflow
These are resolved before this skill runs. Use them as-is:
project.stagefrom the config block is the authoritative phase for Step 2 — it already applies theproject.yaml→production/stage.txtfallback, and preserves values containing spaces (Systems Design).workflowfrom the config block is the tier for Steps 2 and 5 — do not re-read it.- If no config block rendered, shell preprocessing is disabled; fall back to the
defaults in
.claude/docs/config-resolution.md.
Step 1: Read the Catalog
Read .claude/docs/workflow-catalog.yaml. This is the authoritative list of all
phases, their steps (in order), whether each step is required or optional, and
the artifact globs that indicate completion.
Step 1b: Find Skills Not in the Catalog
After reading the catalog, list .claude/skills/*/SKILL.md to get the full list
of installed skills. For each file, extract the name: field from its frontmatter.
Compare against the command: values in the catalog. Any skill whose name does
not appear as a catalog command is an uncataloged skill — still usable but not
part of the phase-gated workflow.
Collect these for the output in Step 7 — show them as a footer block:
### Also installed (not in workflow)
- `/skill-name` — [description from SKILL.md frontmatter]
- `/skill-name` — [description]Only show this block if at least one uncataloged skill exists. Limit to the 10 most relevant based on the project's stage (QA skills in production, team skills in production/polish, etc.).
Step 2: Determine the Current Stage
First, take workflow from the config block above. If it is minimal, the
project is on the minimal path, not the phase ladder: skip the rest of this step,
read the session context (Step 3), then go to Step 4m. At that tier, do
not map project.stage — nothing on the minimal path runs /gate-check, so
the stage reads Concept however far the
project has got, and walking the Concept stage would send a project that already
has stories back to the concept doc, art bible and systems map.
Otherwise, check in this order:
- Take
project.stagefrom the config block above — it is already resolved. Map its value to a catalog phase key:- "Concept" →
concept - "Systems Design" →
systems-design - "Technical Setup" →
technical-setup - "Pre-Production" →
pre-production - "Production" →
production - "Polish" →
polish - "Release" →
release
- "Concept" →
- If neither is set, infer phase from artifacts (most-advanced match wins):
- code root has 10+ source files →
production production/epics/**/story-*.mdexists →pre-productiondocs/architecture/adr-*.mdexists →technical-setupdesign/gdd/systems-index.mdexists →systems-designdesign/gdd/game-concept.md(ordesign/game-brief.md) exists →concept- Nothing →
concept(fresh project)
- code root has 10+ source files →
workflowwas taken at the top of this step (per.claude/docs/workflow-modes.md). It controls whether optional docs are surfaced as next steps (Step 5).
Step 3: Read Session Context
Read production/session-state/active.md if it exists — but only its STATUS
and CHECKPOINT blocks (schema: .claude/docs/templates/session-state.md); the
narrative below them can be long. Find the markers
(search production/session-state/active.md for <!-- /?(STATUS|CHECKPOINT) -->, with line numbers)
and read from the first to the last. A file with no markers predates the schema: read its
last ## Session Extract block instead. Extract:
- What was most recently worked on
- Any in-progress tasks or open questions
- Current epic/feature/task from STATUS block (if present)
This tells you what the user just finished or is stuck on — use it to personalize
the output. It runs at every tier: at minimal it is the only read of the
checkpoint Step 4m relies on (a checkpoint saying "Next step: /story-done" means
the work is written). From here, minimal goes to Step 4m, not Step 4.
Step 4: Check Step Completion for the Current Stage
For each step in the current stage (from the catalog):
Artifact-based checks
Resolve these deterministically — one call, not a glob per step:
bash .claude/scripts/artifact-check.sh --phase [current-phase]Run it exactly as written, here and below: from the project root, with the
relative path — no absolute path, no cd, no 2>&1. This skill's permission
grant matches that form; any other asks the user to approve it.
It evaluates every glob, pattern, min_count and any_of in the catalog
against the working tree and reports one line per step. Map its statuses:
| status | Report as |
PRESENT | Complete |
ABSENT | Incomplete |
SHORT | Incomplete — say how far short (count=/min= are given) |
PATTERN_MISS | Incomplete — the file exists but lacks its marker; say so, since "missing" would send the user to recreate a file they already have |
NO_CHECK | MANUAL if the step carries a note=, else UNKNOWN — completion is not trackable (e.g. repeatable implementation work) |
Do not re-derive any of this by searching the files yourself. any_of in particular is a list of
alternatives — one match is enough — and hand-evaluating it risks a false
"incomplete": engine-setup is satisfied by engine.name
in project.yaml or by the legacy Engine: line in
.claude/docs/technical-preferences.md, and the script reports which alternative
matched (alt=/match=).
NO_CHECK never means done. The script prints a NO_CHECK: total before the
rows; if most of a phase is NO_CHECK, say that plainly rather than implying the
phase is nearly complete.
Special case: the Production stage — read sprint-status.yaml
When the current stage is production, check for production/sprint-status.yaml
before doing any glob-based story checks. If it exists, read it directly:
- Stories with
status: in-progress→ surface as "currently active" - Stories with
status: ready-for-dev→ surface as "next up" - Stories with
status: done→ count as complete - Stories with
status: blocked→ surface as blocker with theblockerfield
This gives precise per-story status without markdown scanning. Skip the glob
artifact check for the implement and story-done steps — the YAML is authoritative.
Special case: repeatable: true (non-production)
For repeatable steps outside production (e.g. "System GDDs"), the artifact check tells you whether any work has been done, not whether it's finished. Label these differently — show what's been detected, then note it may be ongoing.
Step 4m: The Minimal Path (workflow: minimal only)
At minimal the route is the catalog's paths.minimal, not a phase: engine →
design/game-brief.md → stories → /dev-story ↔ /story-done. Resolve it in
one call:
bash .claude/scripts/artifact-check.sh --path minimalMap the statuses exactly as in Step 4. implement and story-done are
NO_CHECK by design — the story status lines below are their check. The next
step is the first of these that applies:
engine-setupnot PRESENT → the main path first. Look forprototypes/*/index.html:- a match → a game is made. Not played yet →
→ Next upis to play it and ask for changes in plain words ("make the jump higher"). Once played (its folder has afeel-log.mdor aREPORT.md, or its brief anAfter play:line or a line under## Keep) →→ Next upis to grow it:/prototypeand say grow it (its verdict, then one question: keep iterating, or grow it into a real web project), with/setup-engineunder "Coming up after that" for an engine instead - When the person asks for a change to a made game, or says they love or
hate it,
→ Next upis/prototypewith their words, whatever else this list finds: it makes a change with an accept-or-undo question and a checkpoint, takes a love-it as a Keep line, and on hate it it offers fix (recommended), pivot or kill. Never answer it with a change or a drop of your own - no match, and the code root holds fewer than 10 source files → no game
yet:
→ Next upis/prototype(make a game you can play), with/setup-engineunder "Coming up after that" as the way to start on an engine instead. With design documents indesign/gdd/, it is built from their concept doc, as in Step 5's A design with nothing to play (its first case) - no match, and 10 or more source files →
/setup-engine, as before
- a match → a game is made. Not played yet →
game-briefnot PRESENT →/reverse-document design [code root]when the code root already holds the game (10 or more source files, the test Step 2 uses forproduction): atminimalit writesdesign/game-brief.mdfrom what is built. Otherwise, with nothing underprototypes/yet, the main path first:→ Next upis/prototype(say the game in one line; on Web it is playable, and writes the brief, on an engine it is a quick throwaway build), with/brainstormunder "Coming up after that" for someone with no idea yet. With a prototype made,/brainstorm(atminimalit writes the one-page brief), which on a built game would start a new idea.create-storiesnot PRESENT:- a grown game (a
production/qa/evidence/grow-*/replay.argsfile) →→ Next upis one feature a sitting: say the next feature in your own words to/prototype(the brief's first[ ]Features line is the suggestion, when there is one); it is built, checked and committed in one sitting./cutgoes under "Coming up after that". Stories, epics and gates only when the person asks for them (then/create-stories, as below) - otherwise
/create-storieswith no argument (atminimalit builds the stories straight from the brief's Features list). When the brief has no[ ]Features item and its## Your systemslist has nothin stand-inorlatersystem,→ Next upis: every feature in the brief is built, so say what to add next, in your own words, and/create-storiesadds it to the brief's Features (with your yes) and makes its stories./cutgoes under "Coming up after that"
- a grown game (a
- Stories exist → the list below was printed by
.claude/scripts/story-status.shbefore you read this skill: one line per unfinished story, already in the route's order —IN_REVIEW, thenIN_PROGRESS, thenTODO(aReadyorNot Startedstory) in build order — thenBLOCKED,OTHER,NO_STATUSand theCOMPLETEcount:
!bash "${CLAUDE_SKILL_DIR}/../../scripts/story-status.sh"
Next up is the story on the first IN_REVIEW, IN_PROGRESS or TODO
line. The list is already current; do not run the script again, and do
not re-read or re-rank the story files:
an In Review story is closed before an In Progress one continues — its
work is written, and /story-done is quick.
IN_REVIEW→ its work is written and waiting to be closed:/story-done [path]IN_PROGRESS→ it is not done — whatever the code or commits suggest, only/story-donemakes a story Complete. Recommend/story-done [path]only if the user,active.mdor the git log says its implementation is written; otherwise/dev-story [path]to carry onTODO→/dev-story [path]- a story that deepens a system (a
TODOstory, or anIN_PROGRESSone with nothing written yet, whose header reads> **Build step**: deepen — <system>): look for that system's design doc,design/gdd/<system>.md(the name lowercased, a leading a, an or the dropped, spaces as hyphens:shop.mdfor "a shop"). None there → Next up is/design-system <system>first, and say why in one plain line: "Story NNN builds<system>out in full, and there is no design for it yet./design-system <system>writes one, for this one system, so the story is built from your choices and not the AI's guesses." The story goes first under Coming up after that. The doc is there →/dev-story [path]as for any story, with no design line - a
BLOCKEDstory → name it and its blocker; it is never Next up - no
IN_REVIEW,IN_PROGRESSorTODOline, butBLOCKED,OTHERorNO_STATUSlines remain → nothing can be built next, and the build order is not done. Name each of those stories with its status as written, and a blocked story's blocker (read it from that story's file). Next up is clearing the first of them: resolve its blocker, or give anOTHERorNO_STATUSstory aStatus:line the route reads (Readyonce it can be built) - every story
Complete(orDone) → the brief's build order is done. Say so, and offer three ways on: play the build; the next feature: on a grown game,/prototypebuilds it, one feature a sitting; otherwise say what to add next, in your own words, and/create-storiesadds it to the brief's Features (with your yes) and makes its stories; or, if the game has outgrown a one-page brief,/project-settingsto raisemodes.rigor.
A game past the light path's size. With stories, read the brief's Features
list (count its [x] and [ ] items, not a cut [-]) and its Skeleton line, if
it has one. The game has outgrown the light path when M on the COMPLETE
line is 9 or more, the Features list has 9 or more items, or the Skeleton line
names four or more systems. Nine is .claude/docs/settings-guidance.md § 4's
"about 9 systems"; four systems is the brief's own mark for a systemic game.
Then add the Studio mode line to the minimal shape in Step 7, naming the
count that passed. It is a suggestion: Next up stays the story, and nothing
waits on it. Show it once: only while the COMPLETE line reads 0 of M (no
story built yet, when switching costs least), and never twice in one
conversation. Once it shows, leave out Step 9's rigor line.
At minimal, never present any of these as required or as a blocker: the
game concept doc, art bible, systems map, GDDs, /create-epics, a sprint plan,
/gate-check, or sprint close-out (/smoke-check, /team-qa,
/retrospective). The brief replaces the design documents and its build order
replaces the sprint plan (.claude/docs/workflow-modes.md — minimal floor).
Every one of them still runs if the user asks for it; mention one only when the
user's argument asks about it. The one exception is a deepen story's design doc
above: one system's, named before that story only.
Then skip Steps 5 and 8, and present with the minimal shape in Step 7.
Step 5: Find Position and Identify Next Steps
From the completion data, determine:
- Last confirmed complete step — the furthest completed required step
- Current blocker — the first incomplete required step (this is what the user must do next)
- Optional opportunities — incomplete optional steps that can be done
before or alongside the blocker. Surface these per the workflow tier: at
full, list all of them; atstandard, list an optional doc only if it is required for the current system/phase (do not flag genuinely-optional docs as gaps). Atminimalthis step does not run — Step 4m replaces it - Upcoming required steps — required steps after the current blocker (show as "coming up" so user can plan ahead)
If the user provided an argument (e.g. "just finished design-review"), use that to advance past the step they named even if the artifact check is ambiguous.
A design with nothing to play. When design/gdd/ holds a .md file and
Glob finds no prototypes/*/index.html, check engine.name in project.yaml:
- No engine set, or
web:→ Next upis a playable first,/prototypebuilt from their concept doc (/prototype design/gdd/game-concept.md; with no concept doc, the GDD that describes the whole game). Say in one line: "Your design documents stay the source of truth; the brief/prototypewrites is only a summary for the build." The blocker found above goes first under "Coming up after that", with/project-stage-detectand/adoptafter it. - An engine other than
web: the blocker stays→ Next up. Add under "Also available" that/prototype --path htmlis the fast option: a browser sketch of the core game, thrown away when the engine build starts.
Step 6: Check for In-Progress Work
If active.md shows an active task or epic:
- Surface it prominently at the top: "It looks like you were working on [X]"
- Suggest continuing it or confirm if it's done
Step 7: Present Output
Keep it short and direct. This is a quick orientation, not a report.
## Where You Are: [Phase Label]
Studio mode (`workflow: [value]`): the design documents, agents and `team-*` pipelines. It fits a team, a long project, or someone who wants the paperwork.
**In progress:** [from active.md, if any]
### ✓ Done
- [completed step name]
- [completed step name]
### → Next up (REQUIRED)
**[Step name]** — [description]
Command: `[/command]`
### ~ Also available (OPTIONAL)
- **[Step name]** — [description] → `/command`
- **[Step name]** — [description] → `/command`
### Coming up after that
- [Next required step name] (`/command`)
- [Next required step name] (`/command`)
---
Approaching the **[next stage]** stage gate → run `/gate-check` when ready.The studio-mode line under the heading labels the path and changes no step.
At minimal use this shape instead — no phase label, no gate line. N
counts only stories whose status line says Complete or Done, and only those
go under ✓ Done. N and M are the two numbers on the COMPLETE line; it
names no finished story, so ✓ Done gives their count, not their titles:
## Where You Are: Minimal path — [N] of [M] stories complete
**In progress:** [from active.md, if any]
### ✓ Done
- Engine: [engine] · Game brief · [N] stories
### → Next up
**[Story NNN: title]** — [what it delivers]
Command: `/story-done [story-path]` for an In Review story, or an In Progress one whose work is written; otherwise `/dev-story [story-path]`, or `/design-system <system>` first for a deepen story whose system has no design doc (Step 4m), with its one line of why
### Coming up after that
- [the next Ready stories in build order, at most 3]
### ~ Studio mode (only when Step 4m's size check passed)
[M stories / N features / N systems]: past the size one brief fits. Studio mode adds a design doc per system and architecture decisions; `/project-settings` switches it on. Optional: the stories build as they are either way.A grown game with no stories: the heading reads Minimal path — grown game, [N] of [M] Features
built (the brief's [x] and [ ] lines), ✓ Done names the grow, and Next up is the next
feature, with /prototype as its command.
Formatting rules:
✓for confirmed complete→for the current required next step (only one — the first blocker)~for optional steps available now- Show commands inline as backtick code
- If a step has no command (e.g. "Implement Stories"), explain what to do instead of showing a slash command
- For MANUAL steps, ask the user: "I can't tell if [step] is done — has it been completed?"
Verdict: COMPLETE — next steps identified.
Step 8: Gate Warning (if close)
Skip this step at minimal — the minimal path has no stage gates.
After the current stage's steps, check if the user is likely approaching a gate:
- If all required steps in the current stage are complete (or nearly complete),
add: "You're close to the [Current] → [Next] gate. Run
/gate-checkwhen ready." - If multiple required steps remain, skip the gate warning — it's not relevant yet.
Step 9: Escalation Paths
After the recommendations, if the user seems stuck or confused, add:
---
Need more detail?
- `/project-stage-detect` — full gap analysis with all missing artifacts listed
- `/gate-check` — formal readiness check for your next stage
- `/start` — re-orient from scratch
- `/project-settings` — if the process feels mismatched to your project, adjust
`modes.rigor`. Apply the change-triggers in
`.claude/docs/settings-guidance.md § 4`: a **lower** tier when the user sounds
overwhelmed by process (and rigor isn't already `minimal`), or a **higher** tier
when the project has outgrown it (many systems, or in Production on
`workflow: minimal`)Only show this if the user's input suggested confusion (e.g. "I don't know", "stuck",
"lost", "not sure"). Don't show it for simple "what's next?" queries. Show the
/project-settings rigor line only when a settings-guidance.md § 4 trigger actually
fires — the user sounds overwhelmed (and rigor isn't already minimal), or the
project has outgrown its tier — not on every confused query. At minimal, leave
out the /gate-check line: the minimal path has no stage gates (Step 4m).
Collaborative Protocol
- Never auto-run the next skill. Recommend it, let the user invoke it.
- Ask about MANUAL steps rather than assuming complete or incomplete.
- Match the user's tone — if they sound stressed ("I'm totally lost"), be reassuring and give one action, not a list of six.
- One primary recommendation — the user should leave knowing exactly one thing to do next. Optional steps and "coming up" are secondary context.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

