adopt

Audits XR project artifacts and generates prioritized migration plans for template compliance.

1|Updated May 3, 2026

Search Tags:#architecture review #project onboarding #template migration #documentation governance #requirements compliance #artifact auditing #XR pipeline

Ready to run

npx skills add https://github.com/imclab/xrA1-swarm --skill adopt-imclab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adopt
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/adopt
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill adopt-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The adopt skill prevents brownfield projects from failing silently by auditing whether existing artifacts (GDDs, ADRs, stories, and infra files) actually match the template’s required internal formats.

Core Features & Use Cases

Format compliance audit for GDDs, ADRs, stories, and key infrastructure artifacts (e.g., stage file, manifest, engine reference).
Gap classification into BLOCKING, HIGH, MEDIUM, and LOW so you can prioritize fixes that unblock the pipeline.
Produces a persistent, checkable migration plan file under docs/ for controlled remediation.

Quick Start

Use the adopt skill to scan a current project and generate an adoption plan by running: /adopt full.

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 XR project to a new template pipeline?▼

To migrate an existing XR project to a new template pipeline, run an adoption skill that audits your current artifacts against required formats and generates a prioritized migration plan for controlled remediation.

What is artifact format compliance auditing for brownfield projects?▼

Artifact format compliance auditing for brownfield projects checks whether existing files like GDDs, ADRs, stories, and infrastructure configs match the template's required internal formats to prevent silent pipeline failures.

How do I fix template compliance gaps in project documentation?▼

You fix template compliance gaps in project documentation by classifying them into BLOCKING, HIGH, MEDIUM, and LOW priorities, then executing a persistent migration plan file to enforce required fields and structure.

When do I need to run an architecture review for project onboarding?▼

You need to run an architecture review for project onboarding when joining an in-progress project or upgrading from an older template version where existing artifacts may not be compatible with the pipeline.

What ADR metadata is required for template pipeline compatibility?▼

Required ADR metadata for template pipeline compatibility includes specific section headings, ADR status fields, systems-index table conventions, and technical preferences configuration to ensure proper artifact governance.

Does the template migration process work with existing infrastructure files?▼

Yes, the template migration process works with existing infrastructure files by auditing key artifacts like stage files, manifests, and engine references to ensure they comply with the required template structure.