Files
Claude-Code-Game-Studios/.claude/skills/architecture-review/references/9-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

2.0 KiB

/architecture-review — Phase 9: Handoff

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

Phase 9: Handoff

After completing the review and writing approved files, present:

  1. Immediate actions: List the top 3 ADRs to create (highest-impact gaps first, Foundation layer before Feature layer)
  2. Pre-gate checklist: Check whether these exist via Glob and mark each ✅ or ❌:
    • the engine's test root — tests/unit/ and tests/integration/ (Godot), Assets/Tests/EditMode/ and Assets/Tests/PlayMode/ (Unity), Source/<Module>/Private/Tests/ (Unreal) — if ❌: run /test-setup
    • .github/workflows/tests.yml — if ❌: run /test-setup
    • design/accessibility-requirements.md — if ❌: run /ux-design
    • design/ux/interaction-patterns.md — if ❌: run /ux-design Present ❌ items as required steps before gate-check. Do not offer /gate-check as an option if any item is ❌ — offer the missing skill to run instead.
  3. Rerun trigger: "Re-run /architecture-review after each new ADR is written to verify coverage improves"

Then close with AskUserQuestion tailored to the pre-gate checklist state:

  • If ADR gaps remain or any pre-gate item is ❌:
    • "Architecture review complete. What would you like to do next?"
      • [A] Write a missing ADR — open a fresh session and run /architecture-decision [system]
      • [B] Run /test-setup — required before gate-check (only show if test infrastructure is ❌)
      • [C] Run /ux-design — required before gate-check (only show if UX/accessibility files are ❌)
      • [D] Stop here for this session
  • If all pre-gate checklist items are ✅ and no blocking ADR gaps remain:
    • "Architecture review complete. All pre-gate items confirmed. What would you like to do next?"
      • [A] Run /gate-check pre-production
      • [B] Write a missing ADR — open a fresh session and run /architecture-decision [system]
      • [C] Stop here for this session