RandallLiuXin/GodotMaker / skills/core/gm-accept
gm-accept
VerifiedPresent final results to the user for acceptance. Shows evaluation results, evaluator screenshots, and asks for confirmation. Explicit invocation only — use /gm-accept.
GodotMaker Accept
$ARGUMENTS
You are presenting the current tag's completed work to the user for acceptance. This is a per-tag gate — accepting now does NOT mean the whole game is done; it means this tag (vX.Y.Z) is ready to be sealed, archived, and git-tagged by /gm-finalize. The user can choose to continue to the next tag (/gm-gdd again) or stop the project here.
Session Setup
FIRST ACTION — before anything else: Write accept to .godotmaker/current_role. Do this on every invocation, even when the file already contains accept (for example an idempotent re-entry) — reading the file is not a substitute. The write must actually happen and must be your first action.
Resume Check
Read .godotmaker/stage.jsonl (treat as empty if missing) — each line is {"role": X, "ts": Y}. Also read .godotmaker/evaluation.json.
- If no event with
role == "evaluate"exists anywhere in the file ORevaluation.jsondoes not exist → STOP. Tell user to run/gm-evaluatefirst. - If
evaluation.jsonresultis"reject"→ STOP. Tell user to run/gm-fixgapfirst. - If the last event has
role == "accept"AND itsdecision == "accept"→ STOP. Tell the user:"Accept already recorded at {timestamp}. Recommended next: /gm-finalize. If you need to redo this step or have other plans, just tell me."
- Otherwise → proceed (re-invocation is valid if the previous accept event recorded a
fixordonedecision).
Process
1. Gather Results
Read these files:
.godotmaker/evaluation.json— evaluator results (mandatory)PLAN.md— task completion statusSTRUCTURE.md— architecture ownership, dependencies, ordering constraints, and stable invariantsGDD.md— original requirements
2. Collect Screenshots
Do NOT capture new screenshots. Use the screenshots already captured by the Evaluator:
- Look in
e2e/screenshots/forscene_{name}.pngfiles - Present each screenshot with the evaluator's
DESIGN.mdrule findings and observable scene-requirement verdict - If no evaluator screenshots exist, note this as a gap
3. Present to User
Format a clear summary:
## Tag Summary — {Tag from PLAN.md}
**Project:** {name}
**Tag delivers:** {one-liner from ROADMAP.md entry for this tag}
### What This Tag Built
- {N} new systems, {M} new components added in this tag
- Tag mechanics delivered: {Tag Mechanics list from PLAN.md, all PASS per evaluation.json `tag_mechanics`}
- Inherited mechanics still passing: {list each `<prev>-MN: pass` from evaluation.json `inherited_mechanics`}
### Test Results
- Unit tests: {from gm-verify results or PLAN.md}
- E2E suite: {evaluation.json `e2e_tests.passed`/`e2e_tests.total` — single suite covering both this tag's mechanics and inherited mechanics}
### Evaluation Result: APPROVED
- Mandatory checks: all passed
- Visual checks: {summary}
- Gameplay issues: {from evaluation.json, or "none"}
### Known Limitations
- {from evaluation minor_issues}
### How to Run
{instructions}
### Screenshots
{show evaluator screenshots with their design-rule and content verdicts}
### What's Next
- After /gm-finalize this tag will be archived to docs/tags/{Tag}/ and `git tag {Tag}` will be created.
- Remaining tags in ROADMAP.md: {list of unshipped tags}
- To start the next tag, re-run /gm-gdd; to stop here, just don't.
4. Ask for Decision
Use AskUserQuestion to ask:
- Accept → I'll record acceptance and recommend /gm-finalize.
- Fix issues → tell me what to fix and I'll dispatch /gm-fixgap.
- Done for now → progress is saved; you can resume any time."
Do NOT proceed until the user replies. Their reply drives the When Done branch below.
When Done
Always append a trace event to .godotmaker/stage.jsonl recording the user's decision, regardless of which branch was chosen. From the project root run:
python tools/append_stage_event.py accept --decision=<accept|fix|done>
This appends a {"role": "accept", "ts": "<server-generated UTC>", "decision": "<accept|fix|done>"} line. Do NOT hand-write the JSON or the timestamp — the helper exists so the timestamp comes from the system clock, not your own output.
Then: git add -A && git commit -m "chore(accept): <Tag> <decision>".
Then, based on the decision:
- accept → Inform the user:
Accepted. Recommended next: /gm-finalize - fix → Inform the user to run
/gm-fixgapwith specific fix instructions - done → Inform the user:
Progress saved; resume any time
Note: only events with decision == "accept" count as the role having truly completed for /gm-finalize's prerequisite check. The fix and done events are kept as audit trail.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |