adopt

You audit project documentation for format compliance by scanning GDDs, ADRs, stories, and infrastructure files for required internal structure and critical fields. It then ranks identified gaps by impact to output a prioritized migration plan.

Template skills silently malfunction during brownfield onboarding because existing project artifacts often lack required internal structure and critical fields, causing pipeline failures when processing incomplete or non-compliant documentation.

You generate a migration plan for upgrading project artifacts by running a format compliance audit on existing GDDs, ADRs, and stories. The system classifies gaps by severity and outputs a numbered remediation plan to docs/adoption-plan-[date].md.

Yes, you can check ADR and story readiness without regenerating in-progress work. The audit uses safety-first workflow controls that verify format compliance and critical fields while ensuring existing stories continue to work uninterrupted.

In artifact audits, BLOCKING severity gaps represent missing critical fields or structure that cause template pipeline failures, while HIGH severity gaps indicate significant formatting issues requiring priority remediation but not completely halting processing.

Yes, the migration plan supports focused audits on specific artifact types. You can run targeted scans using focus modes including full, gdds, adrs, stories, and infra to produce checkable remediation plans scoped to your desired documentation set.