adopt

Audits existing project artifacts for template format compliance and generates a prioritized migration plan.

13|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/frabcd/codex-ai-game-studio --skill adopt-frabcd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adopt
Source: https://github.com/frabcd/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/adopt
Command: npx skills add https://github.com/frabcd/codex-ai-game-studio --skill adopt-frabcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Joining an in-progress game project or upgrading from an older template version often means existing GDDs, ADRs, and stories exist but are in formats that silently break downstream pipeline skills. This Skill audits what exists for actual format compliance, classifies gaps by severity, and produces a numbered, checkable migration plan. ## Core Features & Use Cases - Format Compliance Audits: Checks GDDs for 8 required sections, ADRs for Status and dependency fields, systems-index.md for invalid status values, and stories for TR-ID and ADR references. - Severity Classification: Organizes every gap into BLOCKING, HIGH, MEDIUM, and LOW tiers so you know what breaks pipelines versus what is optional polish. - Migration Plan Generation: Writes a persistent, checkbox-tracked plan to docs/adoption-plan-[date].md with exact fix commands, time estimates, and infrastructure bootstrap ordering. - Use Case: You inherit a Unity project with 12 GDDs and 5 ADRs from a previous team. Run the audit to discover that 3 ADRs are missing Status sections (blocking story-readiness checks) and get a step-by-step plan to retrofit them before generating stories. ## Quick Start Use the adopt skill to audit this project's existing artifacts for template format compliance and write a migration plan.

Frequently Asked Questions about adopt

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

FAQPage Schema
How do I migrate an existing game project to a new template?

Run the adopt audit to scan existing GDDs, ADRs, stories, and infrastructure files for format compliance. It produces a prioritized migration plan at docs/adoption-plan-[date].md with exact fix commands and checkboxes for each gap.

What is the difference between adopt and project-stage-detect?

project-stage-detect answers what artifacts exist in the project, while adopt answers whether what exists will actually work with the template's skills. A project can have GDDs and ADRs that still break pipeline skills due to wrong internal formats.

Can I audit only GDDs or only ADRs instead of everything?

Yes, the skill accepts argument modes: gdds, adrs, stories, or infra to scope the audit to one artifact type. Running with no argument performs the full audit across all types.

Will adopting the template break my existing stories?

No, existing stories continue to work because new format checks like TR-ID validation auto-pass when fields are absent. They simply will not benefit from staleness tracking until regenerated, and in-progress stories should not be regenerated.

Why do parenthetical status values in systems-index.md break skills?

Values like "Needs Revision (see notes)" break exact-string matching in gate-check, create-stories, and architecture-review. They are classified as BLOCKING and listed as the first fix item in the migration plan.