adopt

Audit project artifacts for template compliance and generate a prioritized migration plan.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nevesb/idol-agency-maker --skill adopt-nevesb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adopt
Source: https://github.com/nevesb/idol-agency-maker/tree/main/.claude/skills/adopt
Command: npx skills add https://github.com/nevesb/idol-agency-maker --skill adopt-nevesb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brownfield projects often contain files that superficially exist but do not match the internal formats required by template-driven skills, causing silent failures or incorrect outputs. This Skill performs a deep format audit and produces a prioritized, actionable migration plan so template workflows can run reliably.

Core Features & Use Cases

  • Comprehensive detection: scans project phase, counts GDDs, ADRs, and story files, and locates prior adoption plans.
  • Format validation: checks required GDD headings, ADR sections (including blocking Status), systems-index table integrity, story metadata, and infrastructure artifacts.
  • Classification & prioritization: groups gaps into BLOCKING/HIGH/MEDIUM/LOW, orders fixes, and generates docs/adoption-plan-[date].md with checkboxes and time estimates.
  • Interactive workflow: prompts the user before writing the plan, offers to fix urgent issues (e.g., parenthetical systems-index statuses), and records review-mode choices in production/review-mode.txt.
  • Use cases: onboarding into an in-progress game repo, upgrading template versions, and preflight checks before running /create-stories or other pipeline skills.

Quick Start

Run /adopt with no arguments in the project root to perform a full audit and produce 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 audit existing game development artifacts for template format compliance?

To audit game development artifacts for template format compliance, scan brownfield repositories to validate GDD headings, ADR sections, systems-index tables, and story metadata, then generate a prioritized migration plan classifying gaps by severity.

What is a migration plan for brownfield repository template adoption?

A migration plan for brownfield repository template adoption is a prioritized document that identifies format gaps in existing GDDs, ADRs, and story files, classifying fixes as blocking, high, medium, or low, with checkboxes and time estimates to ensure reliable template workflows.

How do I check ADR and GDD formats before upgrading templates?

Check ADR and GDD formats before upgrading templates by verifying required headings, detecting parenthetical status values, and confirming ADR Status sections exist to prevent silent failures or incorrect outputs from template-driven skills.

Can I validate systems-index table integrity and story metadata in a brownfield game repo?

Yes, you can validate systems-index table integrity and story metadata in a brownfield game repo by scanning for required fields, detecting incorrect parenthetical status values, and recording interactive review-mode choices to fix urgent issues.

Why do template-driven skills fail silently on existing project files?

Template-driven skills fail silently on existing project files because brownfield repositories often contain artifacts that superficially exist but do not match internal formats, lacking required headings or fields, which causes incorrect outputs during pipeline execution.