adopt

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

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill adopt-hechaoyannet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adopt
Source: https://github.com/HechaoYannet/3kingdom-unity/tree/main/.claude/skills/adopt
Command: npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill adopt-hechaoyannet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brownfield onboarding audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /project-stage-detect (which checks what exists) — this checks whether what exists will actually work with the template's skills.

Core Features & Use Cases

  • Phase 1: Detect Project State — checks and reports on artifact existence and readiness (e.g., production/stage, design GDDs, ADRs, and stories) to determine project phase and readiness.
  • Phase 2: Format Audit — validates that artifacts conform to the required internal formats (GDD sections, ADR sections, systems-index, story metadata, and infrastructure docs).
  • Phase 3: Classify and Prioritise Gaps — aggregates findings into BLOCKING, HIGH, MEDIUM, and LOW gaps with clear impacts.
  • Phase 4: Build the Migration Plan — composes a prioritized, actionable plan with exact commands and steps to remediate gaps.
  • Phase 5–7: Present, Review, and Execute — provides a summary, asks to write an adoption plan, sets review mode, and guides one-action-at-a-time remediation.

Quick Start

Run /adopt to begin auditing an existing project and generate 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 an existing project for template compliance?

To audit an existing project for template compliance, validate the internal formats of artifacts like GDDs, ADRs, and stories to classify gaps by impact and generate a prioritized migration plan with concrete fixes.

What is the best way to plan a migration when joining an in-progress brownfield project?

Planning a migration for a brownfield project involves detecting artifact readiness, validating formats like GDD sections and ADRs, and aggregating findings into BLOCKING, HIGH, MEDIUM, and LOW gaps to produce an actionable remediation plan.

How do I upgrade an existing project from an older template version?

Upgrading from an older template version requires auditing existing artifacts against current format requirements, classifying compliance gaps by impact, and executing a step-by-step migration plan with exact commands to remediate issues.

Does this project audit check artifact formats or just file existence?

This project audit checks both artifact existence and internal format compliance, verifying that GDD sections, ADR sections, systems-index, and story metadata conform to required structures to ensure compatibility with template skills.

How are project artifact gaps prioritized in a migration plan?

Project artifact gaps are prioritized by aggregating audit findings into BLOCKING, HIGH, MEDIUM, and LOW impact categories, composing a numbered migration plan that guides one-action-at-a-time remediation.

What artifacts are validated during a brownfield project onboarding?

During brownfield project onboarding, validated artifacts include design GDDs, ADRs, stories, systems-index, and infrastructure docs, which are checked for existence and internal format compliance to determine project phase and readiness.