Files
Claude-Code-Game-Studios/.claude/skills/create-architecture/references/8-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.4 KiB

/create-architecture — Phase 8: Handoff

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

Phase 8: Handoff

Step 1 — Update session state: Write a summary to production/session-state/active.md covering: artifact written, TD/LP sign-off verdicts, any blockers, required ADRs remaining, and next step.

Step 2 — Output the handoff using exactly this template (no freeform prose, no rephrasing of section titles):


Architecture Complete

docs/architecture/architecture.md v[N] — [TD-ARCHITECTURE: APPROVE / CONCERNS (accepted) / REVISED after CONCERNS / REVISED after REJECT / NOT ASSESSED / skipped — [mode] mode]. [One sentence on what the architecture covers.]


Run These ADRs Next

1. /architecture-decision "[Title]" → ADR-[XXXX] [One sentence: what it defines and what it unblocks.]

2. /architecture-decision "[Title]" → ADR-[XXXX] [One sentence.]

3. /architecture-decision "[Title]" → ADR-[XXXX] [One sentence.]

Then: /architecture-review, and /create-control-manifest once it passes and those ADRs are Accepted — it turns them into the layer rules manifest.

List top 3 from Phase 6 in priority order. If fewer than 3 remain, list only what's outstanding.


Gate-Check Readiness

Required before /gate-check pre-production:

  • Accept ADRs: [list Proposed ADR IDs that must be Accepted]
  • Write ADRs: [list ADR IDs that must still be written]
  • Run /architecture-review — writes the review report and the traceability index (docs/architecture/requirements-traceability.md) the gate reads
  • Run /test-setup — scaffolds tests/unit/, tests/integration/, CI workflow, and an example test file
  • Run /ux-design — creates design/ux/interaction-patterns.md and design/accessibility-requirements.md

Run /gate-check pre-production when all boxes are checked.

If nothing is blocking, write instead:

No blockers — run /gate-check pre-production now.


Open Questions to Watch

ID Summary Priority Resolution Path
QQ-XX [short description] High / Medium / Low [ADR or system that resolves it]

Omit this section entirely if there are no open QQs.


(End of handoff. Do not add trailing commentary after the closing rule.)