game
Use when the user asks where the game stands, what to work on next, or to bring the plan and its GitHub Project up to date.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-13
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- game
- description
- Use when the user asks where the game stands, what to work on next, or to bring the plan and its GitHub Project up to date.
- disable-model-invocation
- true
03 SKILL.md 正文
/game: where the game is, and what next
status gathers the facts; you judge them, and every judgement cites its evidence. What you conclude goes into files
the user can read (docs/GDD.md, plan/STATUS.md, plan/plan.json); the GitHub Project mirrors the plan, and when the
user has moved an item, the user's move wins.
1. Facts
pwsh ${CLAUDE_PLUGIN_ROOT}/ci/godot/hyperdot.ps1 status -Json # add -Project <dir> when the game is not the current folder
features[] (with taggedTests, tasks, testedAndPassing), plan (phase, open gates, tasks with itemId and
boardColumn), runs (latest run per command), git, inventory, suggestedCommands (kit commands that are due, each with its reason), handoffs (what the godot-verifier and
godot-architect subagents were last asked and answered, newest first), warnings. If runs.test is missing or older than
git.lastCommit, run test -Json -Quiet first so the evidence is current.
2. The GDD (first run only)
If gdd is null, draft docs/GDD.md from ${CLAUDE_PLUGIN_ROOT}/ci/godot/templates/GDD.md. Base it on what exists:
inventory (scenes, main scene, autoloads, input actions), the scripts behind them, and any notes in the repository.
Each feature gets an id (F1, F2...), a guessed priority, the kinds of fun it serves (Fun:, from game-design) and
"Done when" lines describing behaviour you can see in the code. Keep Status: draft in it. A game jam entry starts from
${CLAUDE_PLUGIN_ROOT}/ci/godot/templates/GDD-jam.md instead (game-plan, jam mode).
Then confirm it with the user, section by section, with multiple-choice questions: pitch and pillars, audience, core
loop, the first session, then features in groups of at most four (Keep, Change, Drop, Later), then out of scope; the
other sections only when the user wants them. Write each answer in before the next question. Remove Status: draft only when every section is confirmed. Never measure progress against a draft.
Ask once whether to tag existing tests: a GDD:F<n> comment on each test that checks a feature's "Done when", so
status can find the proof next time.
First-session stubs
gdd.firstSession lists the GDD's first-session steps (S1, S2...), each with the tests and stubs tagged
GDD:S<n>. Once the GDD is confirmed, write a stub for each step that has neither:
test/flows/first_session_s<n>.stub.json: a flow in theui-flowsformat,"name": "GDD:S<n> <the step>",scenethe main scene, and asstepswhat the step says the player does and sees, as far as the node paths exist.- One
playthrough.stub.jsonbesideproject.godot:"covers"lists every step'sGDD:S<n>,"expect"one log line a step's milestone prints ("[Run] S3 exit reached"), the ending last (theplaythroughrunner's format).
No runner plays a .stub.json, so stubs never turn a run red. Each stubbed step gets a task
(plan -Do add -Title "S2 <step> - flow" -Column backlog). Starting it renames the stub to .flow.json, finishes it and
watches it fail before the code (godot-test-loop); playthrough.stub.json becomes playthrough.json once the game's
--autoplay bot exists (automation-hooks).
3. Assess every feature
| Mark | Meaning | Evidence to cite |
|---|---|---|
| missing | no code for it | where you looked |
| started | code exists, some "Done when" lines are not met | files, the unmet lines |
| works | the code meets every "Done when" line, but no tagged test proves it | files, a passing smoke or flow run |
| proven | tagged tests or flows cover every "Done when" line, and the latest test run passed | test names (file:line), run time |
Design and architecture review
Tests passing is not the whole picture. Look for at most five problems, design first, each one line with its evidence; leave out anything without evidence, and fix nothing here (each finding becomes a task in step 4 or a question in step 6):
- Design: a must or should feature with no
Fun:line, or serving none of the game's main kinds of fun; tasks indoingforcouldfeatures whilemustfeatures are missing; code for something the GDD does not have; a core loop (the GDD's) that no tagged test or flow plays through. - Architecture: the
architecturerunner'swarningsin the latesttest -Jsonyou ran (runtest -Json -Quiet -Runners architectureif there is none this session), most frequent rule first; an autoload ininventory.autoloadsthat no file indocs/decisions/names;docs/ARCHITECTURE.mdmissing once the game has an autoload or a decision, or its autoloads and main scene differ frominventory(thegodot-architectsubagent writes and updates it); decisions stillProposed; atodoCountthat keeps growing;handoffswhere the verifier's latest verdict for a check is a FAIL with nothing passing after it, or an architect proposal nobody answered.
Write plan/STATUS.md (replace it each run): the date and current phase with its open gates; a table Feature | Priority |
Mark | Evidence | Next step; a "Review" section with the findings above (or "nothing found", with what you looked at);
the warnings worth acting on; the decisions still Proposed, which wait for the user; and a "Board changes" section
(step 5).
4. Plan tasks
Every feature that is not proven and not won't needs a task:
plan -Do add -Title "<feature> - <next step>" -Feature F3 -Column backlog. A proven feature's tasks go to done
(plan -Do move -Id t3 -Column done; several at once as -Id t3,t4,t5, one call instead of three). plan -Do move refuses
doing past the work-in-progress limit; finish or move something back instead. A task for a feature the user dropped goes with plan -Do remove -Id t3.
5. The GitHub Project
The project is projectBoard in plan -Json (<owner>/<number>), shown as plan.board in status. plan -Do sync does
this whole step with the GitHub CLI (signed in with the project scope: gh auth refresh -s project), so no connector is
needed. If there is no project yet, make one: plan -Do sync -Board @me (or the owner's login) creates a private project
titled "<game> plan" with a Column field (Backlog, Design, To Do, Doing, Testing, Done), links it to the game's repository
and puts every task on it; tell the user to set the project's Board view to group by Column (gh project view <number> --owner <owner> --web), which the CLI cannot do. To use a project that exists, plan -Do link -Board <owner>/<number>.
-Column takes either the column or the option's name, and -Item takes a project item id (PVTI_...).
Run plan -Do sync and read sync in the result:
movedtasks were moved by the user on the board: the board wins, and the plan has been updated.itemsMoveditems followed a task you moved in the plan;createditems are new tasks;archiveditems belonged to removed tasks.importedtasks are items the user added on the board; if one is not in the GDD, raise it under the scope rule below.warningsname items that are gone or that the kit made for a task nobody links; mention them.
List every item created or moved under "Board changes" in STATUS.md. If sync fails with project-credentials, tell
the user to run gh auth refresh -s project and carry on with the plan alone. The plugin's Stop hook runs the same sync
after a turn that changed the plan (HYPERDOT_PROJECT_SYNC=off stops it), so the board is rarely behind.
6. What next
Run the suggestedCommands whose reason is a failed or missing run before judging (a stale test makes every mark below unreliable), and list the rest under "Checks due" in STATUS.md. End with one multiple-choice question: the three best next tasks, each with its reason in one line (must-haves first,
then what unblocks the current phase's gates, then risks from warnings and the review), and "Something else". When the user picks
one, move it to doing in the plan (the sync moves the item), and start it with godot-test-loop.
Scope rules
- Not in the GDD: before building anything the GDD does not contain, ask: add it as a new feature (with priority and "Done when"), or drop it. Never build it silently.
- New structure: a next task that adds a system, an autoload or a dependency between scenes starts with the
godot-architectsubagent, and its decision is accepted before code is written. - Too much in progress: respect the work-in-progress limit; suggest finishing a task instead of starting one.
- Over the timebox: when the phase is past its timebox, propose which
couldandshouldfeatures to cut, starting with those that serve none of the game's main kinds of fun. Never propose cutting tests. - Pixel art: a next task that draws or animates sprites starts by checking
.mcp.jsonfor anasepriteserver. If it is missing and the user draws in Aseprite, offerinit -McpAseprite "<the folder or Aseprite.exe>"(godot-editor-bridge); ask for the path, never guess it. - Is it fun: a new feature names the kind of fun it serves before it is built; if it serves none of the game's main
kinds, say so when you ask whether to add it (
game-design).
Kit notes
When the kit gets in the way during the session (a command or flag that is wrong or missing, a confusing error, a check
that misses or misfires, a skill that sent you the wrong way, a step that took several tries), append one line to
docs/kit-notes.md in the game, in the format at its top: yyyy-mm-dd <command, skill or subagent>: <what got in the way> - <what would have helped>. Create the file from ${CLAUDE_PLUGIN_ROOT}/ci/godot/templates/kit-notes.md if it is
missing. Do not change the kit from the game's chat; /retro and the weekly review turn the notes into proposals.
04 同仓库更多 Skills
over-budget
Use when a fixture exceeds the size budget.
bad-yaml
暂无简介
bad-workflow-description
Use when testing; runs the kit and then reads the JSON.
bad-version
Use when a fixture quotes a stale package version.
bad-value
Use when a fixture passes a value outside a parameter's set.
bad-trigger
Helps with Godot tests.