adopt

To audit existing project artifacts for template format compliance, scan expected section headings and fields in GDDs, ADRs, and stories. The process validates structural requirements, classifies gaps by severity, and outputs a prioritized migration plan.

Planning a migration from an older project template involves auditing current infrastructure artifacts against required internal formats, classifying detected gaps into BLOCKING, HIGH, MEDIUM, and LOW severity levels, and generating a persistent adoption plan.

Onboarding an in-progress project safely requires running a full mode scan to check whether existing artifacts match the template's required internal formats, ensuring downstream skills receive structurally valid inputs without breaking.

A brownfield project artifact audit includes verifying structural requirements for GDDs, ADRs, stories, and key infrastructure files, checking not just whether files exist but validating expected section headings and fields.

You need to generate an adoption plan when upgrading older template versions across GDDs, ADRs, and stories, or onboarding an in-progress project. The plan categorizes format compliance gaps by severity and provides actionable fixes.

Migration gaps are prioritized by classifying issues into BLOCKING, HIGH, MEDIUM, and LOW severity levels. This classification determines what must be fixed first, producing a checkable plan file with actionable fixes and phase-detection workflow.