Install any skill in seconds. Free to start, no credit card required.
Get Started Free →randallliuxin/gm-gdd
Game Design Document phase for one tag. On the first ever run, runs the full Socratic interview, produces GDD.md, and derives ROADMAP.md (split into SemVer-tagged release tags). On every subsequent run, focuses the conversation on the current tag (the earliest entry in ROADMAP.md without a git tag), optionally updates GDD.md / ROADMAP.md, then generates the current tag's PLAN/STRUCTURE/SCENES/STYLE/ASSETS at the project root. Explicit invocation only — use /gm-gdd.
Passed 13 of 18 test cases with the skill, and 5 of 18 without it.
and 12 more in the full report
11 fixed5 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
All gates for tag v0.1.0 have passed and artifacts are finalized. What exact command should be executed to log stage completion in .godotmaker/stage.jsonl?
| Checked | Without skill | With skill |
|---|---|---|
| Executes python tools/append_stage_event.py gdd --tag=v0.1.0 to log stage completion. | Missed | Passed |
The instructions your model reads when the skill loads.
$ARGUMENTS
You are running the design phase for one tag at a time. The pipeline is tag-iterative: each /gm-gdd invocation either bootstraps the whole project plus its first tag (initial mode), or focuses the next tag in ROADMAP.md (subsequent mode).
FIRST ACTION — before anything else: Write gdd to .godotmaker/current_role.
Read .godotmaker/stage.jsonl (treat as empty if missing) — each line is {"role": X, "ts": Y}.
project.godot does not exist → STOP. Tell user to run /gm-scaffold first.role == "gdd" → STOP. Tell the user:
"GDD already completed for the current tag at {timestamp}. Recommended next: /gm-asset. If you need to redo this step or have other plans, just tell me."
/gm-finalize).Detect the mode by inspecting on-disk state — there is no flag:
ROADMAP.md does NOT exist. (GDD.md may also be missing — if it is, this is a brand-new project.)ROADMAP.md EXISTS. Determine the current tag as follows:
ROADMAP.md, list tag entries in declared order.git tag --list 'v*' (capture stdout).git tag --list.ROADMAP.md to add new entries before re-running /gm-gdd.State the detected mode + (if subsequent) the current tag explicitly to the user as your first conversational message after Resume Check passes. They should never have to guess which tag they're working on.
Before invoking game-planner in initial mode, collect the user's rough idea in normal conversation, not AskUserQuestion.
$ARGUMENTS already contains a game idea, treat it as the freeform intake and do not ask again.$ARGUMENTS is empty, ask the user for one open-ended paragraph: what they want to make, any references, mechanics, visual style, constraints, and anything they already decided. Make clear that rough notes are enough.game-planner brief as "Initial User Concept".test cases passed, vs 5 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.