Adopt

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 "Adopt" for me. 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. The skill itself audits an existing game project for brownfield adoption of the studio template: it detects the project state, audits each artifact type (GDDs, ADRs, stories, infrastructure) for format compliance with the template's skill pipeline — a project can have all the documents and still fail silently if their internal formats are wrong — classifies and prioritises the gaps by severity and workflow mode, builds a numbered migration plan, presents a summary and asks before writing docs/adoption-plan-[date].md, then offers a first migration action. Its argument selects the focus (full, gdds, adrs, stories or infra), and each of its seven phases is a separate file under references/ that the SKILL.md reads and follows in turn. It also runs the template's hooks/yaml-helper.sh to resolve the studio configuration (review_mode, automation, workflow) and may call template scripts such as .claude/scripts/gdd-structure-check.sh and a migrate-v1-config dry run — all template files outside this skill's folder. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/adopt/ 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/adopt/ 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 79547d656e76fde14f1761a6840cb3a6fbb058f69f33d7829d5e073390f46b98 - references/1-detect.md: SHA-256 4120e881103940ec84816951b7f4fd2b5e206b6ad0325fa172a0354b79575ea8 - references/2-format-audit.md: SHA-256 625b3d1dbfe60001089e66253a09f5e0e9dd62f5162d55bc4a79419212739c46 - references/3-classify.md: SHA-256 ba708873c7a72055da515a7f290be80b6a6b8e63610b4f6a1549fab82ed9e042 - references/4-migration-plan.md: SHA-256 27386c73a5fde71606320013f80d55d093c3cbbdca0318dbcbf70d13a9f7b99e - references/5-summary.md: SHA-256 0661b1c4feb24d630ad4a1fd6a888cee699d907fbe01cef18e8dc658b0178622 - references/6-write.md: SHA-256 cb23a80201a30fbe66b92f3356220945fb3fd18ff4ea8966238dff4804152ed9 - references/7-first-action.md: SHA-256 290607da90ceea57ddceccf45c4444c1136fc8e258a8bd631658121ec55462bf 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 plus 7 phase files under references/ (1-detect, 2-format-audit, 3-classify, 4-migration-plan, 5-summary, 6-write, 7-first-action). Nothing in the folder is a program; the phase files are instructions the skill reads at use time. - 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 audited 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 and can call template scripts under .claude/scripts/ — files 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 reads my project's GDDs, ADRs, stories and config files locally. - At use time it writes only after asking: its persistent output is docs/adoption-plan-[date].md in my project, plus any migration state it records when I approve the write phase. No third-party service, account or credential is named in the files I read. - Do not audit any project, do not run any template hook or script, 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 adopt folder into the agent's skills directory, in a folder named exactly "adopt", keeping its 8 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: adopt), 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 calls the template's yaml-helper hook and .claude/scripts helpers), and that inside the template it audits my existing project's artifacts and writes a migration plan only after asking). 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.