adopt

Auditing legacy artifacts for template compliance involves validating existing GDDs, ADRs, and stories against required structures. The process flags gaps by impact and generates a prioritized migration plan file to guide your team's rollout execution.

Artifact existence checks verify what documents exist in a project, while template format readiness validates whether those artifacts have the correct structure to function with the template's skills. Brownfield onboarding requires strict format validation.

To generate a migration plan, run an audit on your in-progress project. This validates artifact structures, classifies gaps by impact, and outputs a reproducible adoption plan file in your docs directory for structured team execution.

Yes, you can focus the audit on specific artifact types. The process supports targeted modes to check GDDs, ADRs, stories, and infrastructure artifacts independently, ensuring the migration plan prioritizes the correct document formats.

You should run an artifact audit when joining an in-progress project or upgrading from an older template version. This ensures your existing artifacts meet required formats and identifies structural gaps before attempting a migration.

An adoption plan file contains a numbered migration plan with prioritized actions. It classifies structural gaps by impact and provides a reproducible roadmap to transition your brownfield project to a template-ready state.