Guide · Agent skill
How to use the Brownfield Template Adoption Audit agent skill (adopt)
Updated · written with AI from the project's own documentation and checked against our catalogue data
The adopt skill is an agent skill for Claude Code that audits an existing project against the Claude Code Game Studios template. It checks whether your design documents, decision records, stories and config files are in the format the template's other skills expect, not just whether those files exist. This guide explains what the skill does, how to install it, how to trigger it, and what to check before running it, so you can produce a numbered migration plan you can work through.
Brownfield Template Adoption AuditDonchitos/Claude-Code-Game-Studios · MIT Download the skill Quick start
- 1Download the ZIP. Get the adopt skill ZIP from the directory page.
- 2Unzip into a skills folder. Extract it into ~/.claude/skills/ for all projects, or into the project's .claude/skills/ for one project.
- 3Confirm the template folders exist. Make sure .claude/skills, .claude/hooks and .claude/scripts are present in the project.
- 4Start Claude Code in the project. Open the existing project so the skill can read its artifacts.
- 5Run the audit. Type /adopt for a full audit, or /adopt gdds, adrs, stories or infra for one area.
- 6Review the summary. Read the gaps sorted by severity before agreeing to write anything.
- 7Write and work through the plan. Confirm the write to docs/adoption-plan-[date].md, then tackle BLOCKING items first.
What the adopt skill makes the agent do
An agent skill is a folder of instructions that Claude Code loads when a task matches it. The adopt skill is meant for projects that already have work in progress. Its job is to find out whether that work will actually function with the template's skills. Many template skills are format-sensitive, so a document can exist and still cause them to fail silently or produce wrong results.
The skill runs in phases: it detects project state, audits formats for design docs (GDDs), decision records (ADRs), stories, infrastructure and config, classifies the gaps by severity, and drafts a migration plan. It then presents a summary and asks before writing anything.
- Checks format compliance, not just file existence
- Sorts problems into BLOCKING, HIGH, MEDIUM and lower severity tiers
- Writes a checkable plan to docs/adoption-plan-[date].md only after you agree
Install the adopt skill
Download the ZIP from the directory page and unzip it into one of two places. For all your projects, use ~/.claude/skills/. For a single project, use the .claude/skills/ folder inside that project.
If you use the Claude apps instead, upload the skill under Settings → Capabilities → Skills.
- Personal install: unzip into ~/.claude/skills/
- Project install: unzip into the project's .claude/skills/
- Claude apps: Settings → Capabilities → Skills, then upload
Check the requirements before you run it
The skill expects the template's folder layout to be present. It also runs helper scripts through Bash, so Bash must be available. Without these, the audit cannot complete.
The skill is listed as running scripts and not using the network. Read the safety notes below before running it on sensitive projects.
- Claude Code with the template's .claude/skills, .claude/hooks and .claude/scripts folders present
- Bash available to run yaml-helper.sh, gdd-structure-check.sh and migrate-v1-config.sh
- Runs scripts: yes. Uses network: no
Trigger the skill with natural requests
You can invoke the skill with the slash command /adopt. It accepts an optional focus argument: full, gdds, adrs, stories or infra. With no argument it runs a full audit.
You can also ask in plain language, such as asking whether your existing design docs will work with the template. Use the focus argument when you only need one area checked.
- /adopt — full audit of all artifact types
- /adopt gdds — GDD format compliance only
- /adopt adrs — ADR format compliance only
- /adopt stories — story format compliance only
- /adopt infra — registry, manifest, sprint-status and stage.txt gaps only
/adoptRead the output and the migration plan
The skill first prints a short scanning line, then reads silently and shows you a summary of scope before asking to write. Review the summary first. If you agree, the plan is written to docs/adoption-plan-[date].md as a checklist you can tick off.
The plan is advisory. The skill does not fix your files automatically, and you decide what to change and when. The skill also tells you it will not regenerate existing GDDs, ADRs or stories that already have content.
- Review the severity-sorted summary before answering the write question
- Work through BLOCKING items first
- Treat the plan as a checklist, not an automatic fix
Safety notes: scripts and local files
The skill runs helper scripts and reads local config files and project YAML files directly. This is by design, but it means the skill will look at those files. If you do not want that, do not run the skill on that project.
The reference files the skill loads were not included in the source review, so the exact write behaviour is unverified. Check the plan and your files after running it.
- Reads project.yaml and legacy config files directly
- Runs Bash helper scripts from the template's .claude folders
- Uses no network access, according to the listing
- Only asks before writing; confirm the plan path before accepting
What people use it for
- Checking whether an existing game design doc set will work with the template's story generation
- Finding out why template skills produce wrong output on current ADRs
- Building a prioritised checklist for a lead migrating a team's artifacts
- Auditing only infrastructure files such as the registry, manifest and sprint status before bootstrapping
Frequently asked questions
Is the adopt skill free to use?
The source describes the skill as MIT licensed. It does not state any price, so check the license terms in the repository before use.
What do I need to run the adopt skill?
You need Claude Code with the template's .claude/skills, .claude/hooks and .claude/scripts folders present, and Bash available to run the helper scripts. The skill is not meant for brand-new projects with no existing artifacts.
How do I install the adopt skill?
Download the ZIP from the directory page and unzip it into ~/.claude/skills/ for personal use or a project's .claude/skills/ folder. In the Claude apps, upload it under Settings → Capabilities → Skills.
Does the adopt skill fix my files automatically?
No. It only asks before writing a migration plan file. It is advisory, and you decide what to fix and when.
How is adopt different from /project-stage-detect?
project-stage-detect checks what exists in the project. adopt checks whether what exists is in the format the template's skills need to work correctly.
Does the adopt skill need internet access?
The listing says it does not use the network. It does run local helper scripts and reads project config files.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use adopt if you are bringing an existing game or project into the Claude Code Game Studios template and want a prioritised checklist before relying on its automated skills. Skip it for brand-new projects with nothing to audit, or if you do not want local config and project YAML files read. Because the reference files were not part of this review, verify the write behaviour on a copy of your project first.
Download the skill