adopt

Audit game studio project artifacts for template format compliance and generate a gap report.

Updated May 13, 2026
One-click install
npx skills add https://github.com/FrancisVarga/the-dream-machine --skill adopt-francisvarga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adopt
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/adopt
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill adopt-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brownfield projects often contain GDDs, ADRs, and stories that exist but are not in the exact internal formats the template’s skills require, causing silent failures and incorrect outputs during later pipeline steps.

Core Features & Use Cases

  • Format compliance auditing: Verifies required internal sections and header fields for GDDs, ADRs, system indexes, stories, and infrastructure.
  • Gap severity classification: Organizes issues into BLOCKING, HIGH, MEDIUM, and LOW tiers based on how badly they break template skills.
  • Actionable migration planning: Produces a numbered, checkable adoption plan you can follow to migrate safely without regenerating in-progress stories.

Quick Start

Run the adopt skill in full mode to scan your current repo and propose a prioritized 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 studio project artifacts for template compliance?

Audit existing game studio project artifacts by scanning GDDs, ADRs, stories, and infrastructure files to verify required internal sections, detect breaking status conventions, and classify format gaps into severity tiers.

What is brownfield project migration planning for upgraded repositories?

Brownfield migration planning assesses in-progress repositories containing existing GDDs and ADRs, generating a persistent adoption plan file with prioritized, checkable steps to safely align project artifacts with required template formats.

How do I classify format gaps in game design docs and architecture decision records?

Classify format gaps in game design docs and architecture decision records by scanning their header structures and internal metadata, then organizing missing or non-compliant sections into BLOCKING, HIGH, MEDIUM, and LOW severity tiers.

Can I migrate in-progress stories without regenerating the entire repository?

You can migrate in-progress stories without regenerating the repository by following a numbered adoption plan that targets specific format compliance gaps, allowing you to preserve existing work while fixing template compatibility.

What's the best way to generate an adoption plan for non-compliant project artifacts?

Generate an adoption plan for non-compliant project artifacts by running a full repository scan that checks presence and section structure, classifies gaps by severity, and writes a persistent migration plan file with actionable steps.

Why do later pipeline steps fail silently after upgrading brownfield game projects?

Later pipeline steps fail silently because existing GDDs, ADRs, and stories in brownfield projects often lack the exact internal formats and metadata fields that downstream template skills require for correct processing.