adopt

Audit game project GDDs, ADRs, and stories for template format compliance.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill adopt-xganqaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adopt
Source: https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios/tree/main/.claude/skills/adopt
Command: npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill adopt-xganqaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brownfield (already-started) game projects often have design docs and ADRs that exist but don’t match the template’s required internal formats, causing later pipeline skills to silently fail or produce incorrect outputs.

Core Features & Use Cases

  • Format compliance auditing: Verifies required section headings, required header fields (like ADR status), and table structures (like systems-index) so downstream skills behave correctly.
  • Gap severity classification: Detects BLOCKING, HIGH, MEDIUM, and LOW gaps and explains the functional impact of each.
  • Actionable migration plan: Produces a numbered, checkable adoption plan (written to docs/adoption-plan-[date].md) that orders fixes to preserve pipeline bootstrapping dependencies.

Quick Start

Run /adopt to scan your existing project for template format gaps and generate an adoption plan at docs/adoption-plan-[date].md.

Frequently Asked Questions about adopt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate existing game project documentation to a required template format?

Brownfield project documentation migration requires auditing existing GDDs, ADRs, and infrastructure against template format compliance, then generating a numbered migration plan with checkable remediation steps.

Why do downstream pipeline skills silently fail when processing my project's design docs?

Downstream pipeline skills silently fail when existing design docs and ADRs lack required section headings, header fields, and table structures mandated by the template's strict internal format.

How do I audit an in-progress game project for operational readiness and documentation compliance?

Audit in-progress game projects by reading project artifacts, running scoped format checks by argument mode, and classifying documentation gaps by severity from BLOCKING to LOW.

What is the best way to classify documentation format gaps for a brownfield project onboarding?

Classify documentation format gaps by detecting BLOCKING, HIGH, MEDIUM, and LOW severity levels, explaining the functional impact of each gap on downstream pipeline skills.

Does the migration plan ordering matter when fixing template format compliance issues?

Migration plan ordering matters because the generated numbered adoption plan orders remediation fixes specifically to preserve pipeline bootstrapping dependencies and prevent silent failures.

Can I upgrade older template versions in my game project without breaking existing ADRs and stories?

Upgrade older template versions by running a format compliance audit on existing ADRs and stories, then following the generated migration plan to systematically resolve detected format gaps.