Architecture Decision

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 Decision" for me. It is the Game Studios workflow for documenting a technical decision as an ADR: it parses its argument (a title, or retrofit <path>, or accept <ADR-id>), loads the project's engine context first, gathers the decision context, and generates an ADR that records the context, the alternatives considered and the consequences, at the prose depth the studio configuration selects (docs.density). The ADR skeleton is fixed by the companion CONTRACT.md in the same folder, the spawned template agents (technical-director for the TD-ADR gate and the engine specialist) validate it, and director gates from the template's .claude/docs/ govern the checks. Its phases live in references/ (accept and retrofit entry points, engine context, context gathering, decision and generation). Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/architecture-decision/ folder at the pinned commit: 8 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-decision/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - CONTRACT.md: SHA-256 f295ec9326ff3050d71219be899bc4a75a97fff28a1221ead0693006c8f8a2be - SKILL.md: SHA-256 b550883ebd9973ad6534c2984a77fdb6229f47eb8d2b2c31e7501d8a89f2cdf5 - references/0-accept.md: SHA-256 abc2ab957854d947d7ee01c132cebf9c19c851aef3dfa788e3ee21ce82881016 - references/0-retrofit.md: SHA-256 f41ba65eda577623b3dbcef762495672924bf8ab382e7c2650e61006a378d0ce - references/1-engine-context.md: SHA-256 0e0e4e96781ee752bff34d705c1dc26359fd662b50087ae7780495ddfaea353c - references/3-gather-context.md: SHA-256 f226269d8c23f6d9fbc784fbc0dbf050d12a860ec20be0a3388b9b9345ff2d55 - references/4-decide.md: SHA-256 14a595f2efc8c0fdbbd9dbf6c0912250b817073db2a1de17ebf1c831d0822f8a - references/5-generate.md: SHA-256 c6862e0d8ce98ad9b0d1c2287f685019d5cb47cb808456d1d164c6dd4deb3138 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 8 files: SKILL.md, CONTRACT.md (the ADR contract it follows), and 6 phase files under references/ (0-accept, 0-retrofit, 1-engine-context, 3-gather-context, 4-decide, 5-generate). 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-decision folder into the agent's skills directory, in a folder named exactly "architecture-decision", keeping its 8 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: architecture-decision), the 8 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 spawns template agents and reads template gate files), and that inside the template it creates ADR documents in my project for technical decisions). 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.