Files
Claude-Code-Game-Studios/.claude/skills/review-all-gdds/references/7-handoff.md
T
DonchitosandClaude Opus 5.5 be8993bbc5 Release 1.1.3 — long skills keep their later steps
Fix release for 1.1.2: the 14 longest skills keep their later phases
after a compaction, a question nobody answered is never taken as an
answer, settings read the same from a subfolder, the commit check works
for a project in a subfolder of a larger repository, every skill opens
with a title, and the shipped allow rules no longer approve deleting a
branch or writing files without asking. Details in CHANGELOG.md; upgrade
steps in UPGRADING.md (v1.1.2 → v1.1.3).

Refs #83
Refs #133

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0185en4t76fPn7315q4c3nko
2026-10-08 17:52:48 +11:00

1.8 KiB

/review-all-gdds — Phase 7: Handoff

Part of /review-all-gdds. SKILL.md names when to read this file; the settings it resolved and the rules under its later headings still apply here.

Phase 7: Handoff

After all file writes are complete, use AskUserQuestion for a closing widget.

Before building options, check project state:

  • Are there any Warning-level items that are simple edits (flagged with "30-second edit", "brief addition", or similar)? → offer inline quick-fix option
  • Are any GDDs in the "Flagged for Revision" table? → offer /design-review option for each
  • Read systems-index.md for the next system with Status: Not Started → offer /design-system option
  • Is the verdict PASS or CONCERNS? → offer /gate-check or /create-architecture

Build the option list dynamically — only include options that apply:

Option pool:

  • [_] Apply quick fix: [W-XX description] in [gdd-name].md — [effort estimate] (one option per simple-edit warning; only for Warning-level, not Blocking)
  • [_] Run /design-review [flagged-gdd-path] — address flagged warnings (one per flagged GDD, if any)
  • [_] Run /design-system [next-system] — next in design order (always include, name the actual system)
  • [_] Run /create-architecture — begin architecture (verdict is PASS/CONCERNS) (include only if the verdict is PASS or CONCERNS — never on FAIL or NOT ASSESSED)
  • [_] Run /gate-check — validate Systems Design phase gate (include if verdict is PASS)
  • [_] Stop here

Assign letters A, B, C… only to included options. Mark the most pipeline-advancing option as (recommended).

In collaborative and guided modes, never end the skill with plain text — always close with this widget. In autonomous mode, print the verdict and recommended next step, then record via log_decision (no widget).