adopt
GitHub审计现有项目工件与模板技能管道的格式合规性，识别差异并生成优先级迁移计划，确保遗留项目能正确运行。
Trigger Scenarios
Install
npx skills add Donchitos/Claude-Code-Game-Studios --skill adopt -g -y
SKILL.md
Frontmatter
{
"name": "adopt",
"model": "sonnet",
"description": "Brownfield audit — do existing artifacts actually work? Numbered migration plan. Unlike \/project-stage-detect, checks compliance not existence.",
"allowed-tools": "Read, Glob, Grep, Write, AskUserQuestion, Bash(bash \"*\/.claude\/skills\/adopt\/..\/..\/hooks\/yaml-helper.sh\" resolve_config *), Bash(bash .claude\/scripts\/gdd-structure-check.sh *), Bash(bash .claude\/scripts\/migrate-v1-config.sh --dry-run*)",
"argument-hint": "[focus: full | gdds | adrs | stories | infra]",
"user-invocable": true
}
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,automation,automation_always_ask,workflow
Resolved above — use as-is. /adopt also inspects project.yaml and the legacy
config files directly when reporting and writing migration state; that raw
inspection is deliberate and separate from the resolved values above.
Adopt — Brownfield Template Adoption
This skill audits an existing project's artifacts for format compliance with the template's skill pipeline, then produces a prioritised migration plan.
This is not /project-stage-detect.
/project-stage-detect answers: what exists?
/adopt answers: will what exists actually work with the template's skills?
A project can have GDDs, ADRs, and stories — and every format-sensitive skill will still fail silently or produce wrong results if those artifacts are in the wrong internal format.
Output: docs/adoption-plan-[date].md — a persistent, checkable migration plan.
Argument modes:
Audit mode: $ARGUMENTS (blank = full)
- No argument /
full: Complete audit — all artifact types gdds: GDD format compliance onlyadrs: ADR format compliance onlystories: Story format compliance onlyinfra: Infrastructure artifact gaps only (registry, manifest, sprint-status, stage.txt)
Automation mode: Resolve modes.automation (project.local.yaml →
project.yaml → default collaborative). Every AskUserQuestion call follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
workflow (per .claude/docs/workflow-modes.md). It scopes the Phase 2 audit and
Phase 3 severity: full audits all doc types at full structure; standard audits
only the required docs/sections (optional sections are informational, not gaps);
minimal is a design/game-brief.md format check — GDDs/ADRs/UX are not expected. See Phase 2.
Phase 1: Detect Project State
Read references/1-detect.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Phase 2: Format Audit
Read references/2-format-audit.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Phase 3: Classify and Prioritise Gaps
Read references/3-classify.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Phase 4: Build the Migration Plan
Read references/4-migration-plan.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Phase 5: Present Summary and Ask to Write
Read references/5-summary.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Phase 6: Write the Adoption Plan
Read references/6-write.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Phase 7: Offer First Action
Read references/7-first-action.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Collaborative Protocol
Applies in collaborative mode (the default). For guided and
autonomous modes, see .claude/docs/automation-modes.md — the rules below
describe what collaborative mode requires, not universal behavior.
- Read silently — complete the full audit before presenting anything
- Show the summary first — let the user see scope before asking to write
- Ask before writing — always confirm before creating the adoption plan file
- Offer, don't force — the plan is advisory; the user decides what to fix and when
- One action at a time — after handing off the plan, offer one specific next step, not a list of six things to do simultaneously
- Never regenerate existing artifacts — only fill gaps in what exists; do not rewrite GDDs, ADRs, or stories that already have content
Version History
-
05ad7c8
Current 2026-10-19 11:43
重构故事技能以使用共享辅助脚本；增加大型设计文档读取防护；引擎引用更新至Godot 4.7和Unreal Engine 5.8；移除所有Shell命令的预批准规则。
-
7ed2c3e
2026-09-28 04:01
修复了配置解析命令在自动模式外的权限拦截问题；新增对 project.yaml 中 engine.name 及 technical-preferences.md 的读取支持；完善 Phase 1 存在性检查逻辑。
- 984023d 2026-07-25 09:36
