Architecture Review

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — INTEGRATED SYSTEM FIRST: this skill is one piece of the complete "Claude Code Game Studios" template (49 agents, 74 skills, studio templates and a studio CLAUDE.md, per the repository README). Each skill assumes that template is installed, with its conventions, its project.yaml / project.local.yaml configuration, its .claude/docs/ mode documents, its hooks (for example hooks/yaml-helper.sh, outside this skill's folder) and its .claude/scripts/ helpers. Installing this listing alone copies only this skill's folder, without the rest of the system: the skill may reference template agents, files, hooks or scripts that are absent outside the full template, and it may not run as designed on its own. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Install "Architecture Review" for me. It is the Game Studios architecture quality gate: it loads every GDD and ADR in the project, extracts the technical requirements from each GDD, builds the requirements-to-ADR traceability matrix, detects cross-ADR conflicts, cross-checks engine compatibility against the pinned engine version, checks architecture-document coverage, and reports with verdicts PASS, CONCERNS, NOT ASSESSED or FAIL, writing the review and handing it off through the template's review-receipt machinery (the template's .claude/scripts/review-receipts.sh, adr-dep-graph.sh and registry.sh helpers are called at use time). Focus arguments select full, coverage, consistency, engine, a single GDD, or the extended rtm matrix that also chains story and test files into docs/architecture/requirements-traceability.md. Each phase is a separate file under references/ that the SKILL.md reads and follows in turn. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/architecture-review/ folder at the pinned commit: 10 files in total) Pinned version: install the code at commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a temporary folder, check out commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418, and copy the .claude/skills/architecture-review/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 0219e6c2545af2416775bff139d921c1bc3c3e9cc1ffc25a25d6186f8e444f6e - references/1-load.md: SHA-256 d866809875b0d6499cb9ae243ea28643c6d7a72bb06a0dec0894853c45f807ce - references/2-extract-requirements.md: SHA-256 c34e4466059db1c71ccbd42946a91ee62964db38f761f333288cb59db2a84263 - references/3-traceability.md: SHA-256 dd90c9669632cb844d45ca3a1ce2007fd0f34dbf8b13031f22db100cc8961a75 - references/4-conflicts.md: SHA-256 b20b53754a69064941366d5ab8ca34cc1aced6f0e40ef09b4d39a0b6d48d2d57 - references/5-engine.md: SHA-256 6d48c267b83bca7de2fba89e7c57685277d2fa5c728a10dc6d01a6b876cd3939 - references/6-document-coverage.md: SHA-256 f902dc64c01721cee13fd880a3670704c409cc82b9686eb7c0b7609dbdd5fcb7 - references/7-report.md: SHA-256 d0d31c337e976a1427a770d5f8d761212de181ad66455963a87900a196b966cc - references/8-write.md: SHA-256 f7c34fad5198874728b61cb23faae6555debaa63bed376082ed2da1f24e165bc - references/9-handoff.md: SHA-256 5620d237cb8f5c429215ec60921ec1ea83f723b004611217f7ccd11422eb7516 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 10 files: SKILL.md plus 9 phase files under references/ (1-load, 2-extract-requirements, 3-traceability, 4-conflicts, 5-engine, 6-document-coverage, 7-report, 8-write, 9-handoff). Nothing in the folder is run during installation; companion files are instructions/references the skill reads at use time, copied as-is. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no project of mine is read or modified. - Integrated-system reality, from the files: at use time the skill resolves studio configuration by running the template's hooks/yaml-helper.sh, reads the template's .claude/docs/ mode documents, and may spawn template agents or call template scripts under .claude/scripts/ — files and agents that live outside this skill's folder and are absent in a standalone install, so parts of it cannot run outside the full template. Inside the template it works on my project's own files, locally. - No account, key, payment or third-party service is named in the files I read; any file it writes at use time is in my own project and follows the template's ask-before-writing collaborative conventions described in the skill. - Do not run any template hook or script, do not spawn any template agent, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole architecture-review folder into the agent's skills directory, in a folder named exactly "architecture-review", keeping its 10 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: architecture-review), the 10 files in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that it belongs to the full Claude Code Game Studios template and may not run standalone (it calls template registry/receipt scripts and reads template docs), and that inside the template it reviews my project's GDD-to-ADR traceability and writes its review into my project). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.