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.
77%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/next-step/SKILL.mdThis 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.
!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.stage from the config block is the authoritative phase for Step 2
— it already applies the project.yaml → production/stage.txt fallback, and
preserves values containing spaces (Systems Design).workflow from the config block is the tier for Steps 2 and 5 — do not re-read it..claude/docs/config-resolution.md.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.
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.).
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.stage from the config block above — it is already resolved. Map its value to a catalog phase key:
conceptsystems-designtechnical-setuppre-productionproductionpolishreleaseIf neither is set, infer phase from artifacts (most-advanced match wins):
productionproduction/epics/**/story-*.md exists → pre-productiondocs/architecture/adr-*.md exists → technical-setupdesign/gdd/systems-index.md exists → systems-designdesign/gdd/game-concept.md (or design/game-brief.md) exists → conceptconcept (fresh project)workflow was 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).
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:
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.
For each step in the current stage (from the catalog):
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.
sprint-status.yamlWhen the current stage is production, check for production/sprint-status.yaml
before doing any glob-based story checks. If it exists, read it directly:
status: in-progress → surface as "currently active"status: ready-for-dev → surface as "next up"status: done → count as completestatus: blocked → surface as blocker with the blocker fieldThis gives precise per-story status without markdown scanning. Skip the glob
artifact check for the implement and story-done steps — the YAML is authoritative.
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.
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-setup not PRESENT → the main path first. Look for
prototypes/*/index.html:
→ Next up is to play it
and ask for changes in plain words ("make the jump higher"). Once
played (its folder has a feel-log.md or a REPORT.md, or its brief
an After play: line or a line under ## Keep) → → Next up is to
grow it: /prototype and say grow it (its
verdict, then one question: keep iterating, or grow it into a real web
project), with /setup-engine under "Coming up after that" for an
engine instead→ Next up is /prototype with 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→ Next up is /prototype (make a game you can play),
with /setup-engine under "Coming up after that" as the way to start
on an engine instead. With design documents in design/gdd/, it is
built from their concept doc, as in Step 5's A design with nothing to play
(its first case)/setup-engine, as beforegame-brief not PRESENT → /reverse-document design [code root] when the
code root already holds the game (10 or more source files, the test Step 2
uses for production): at minimal it writes design/game-brief.md from
what is built. Otherwise, with nothing under prototypes/ yet, the main
path first: → Next up is /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 /brainstorm under "Coming up after that" for
someone with no idea yet. With a prototype made, /brainstorm (at minimal
it writes the one-page brief), which on a built game would start a new idea.create-stories not PRESENT:
production/qa/evidence/grow-*/replay.args file) → → Next up is 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. /cut goes under "Coming up after
that". Stories, epics and gates only when the person asks for them (then
/create-stories, as below)/create-stories with no argument (at minimal it builds the
stories straight from the brief's Features list). When the brief has no
[ ] Features item and its ## Your systems list has no thin stand-in
or later system, → Next up is: every feature in the brief is built, so
say what to add next, in your own words, and /create-stories adds it to
the brief's Features (with your yes) and makes its stories. /cut goes
under "Coming up after that".claude/scripts/story-status.sh
before you read this skill: one line per unfinished story, already in
the route's order — IN_REVIEW, then IN_PROGRESS, then TODO (a
Ready or Not Started story) in build order — then BLOCKED, OTHER,
NO_STATUS and the COMPLETE count:!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-done makes a story Complete. Recommend
/story-done [path] only if the user, active.md or the git log says
its implementation is written; otherwise /dev-story [path] to carry onTODO → /dev-story [path]TODO story, or an IN_PROGRESS one
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.md for "a shop"). None there → Next up is /design-system <system>
first, and say why in one plain line: "Story NNN builds 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 lineBLOCKED story → name it and its blocker; it is never Next upIN_REVIEW, IN_PROGRESS or TODO line, but BLOCKED, OTHER or
NO_STATUS lines 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 an
OTHER or NO_STATUS story a Status: line the route reads (Ready
once it can be built)Complete (or Done) → the brief's build order is done.
Say so, and offer three ways on: play the build; the next feature: on a grown game, /prototype builds it, one feature a sitting; otherwise
say what to add next, in your own words, and /create-stories adds it to the brief's Features
(with your yes) and makes its stories; or, if the game has outgrown a one-page
brief, /project-settings to raise modes.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.
From the completion data, determine:
full, list all of them; at standard, list an optional doc only if it is
required for the current system/phase (do not flag genuinely-optional docs as
gaps). At minimal this step does not run — Step 4m replaces itIf 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:
web: → Next up is a playable first, /prototype built
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 /prototype writes is
only a summary for the build." The blocker found above goes first under
"Coming up after that", with /project-stage-detect and /adopt after it.web: the blocker stays → Next up. Add under "Also
available" that /prototype --path html is the fast option: a browser sketch
of the core game, thrown away when the engine build starts.If active.md shows an active task or epic:
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 nowVerdict: COMPLETE — next steps identified.
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:
/gate-check when ready."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).
Donchitos/Claude-Code-Game-Studios
abc0de7
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.