adopt

An artifact audit evaluates existing project files like GDDs, ADRs, and stories against internal template formats. It checks for correct structural compliance rather than just file presence, generating a persistent migration plan at docs/adoption-plan-[date].md to guide systematic remediation.

The best way to generate a prioritized migration plan is to audit your repository's existing artifacts for template compliance. This produces a persistent, checkable migration plan at docs/adoption-plan-[date].md, guiding systematic remediation to align your brownfield project with the template's skills.

Yes, you can scope an artifact audit to only check ADRs and stories by using argument modes. The audit supports targeted modes including gdds, adrs, stories, infra, and full, allowing you to restrict the assessment to specific artifact types relevant to your migration needs.

You need to run a template migration audit when joining an in-progress project or upgrading from an older template version. The audit evaluates whether existing GDDs, ADRs, and stories conform to current internal formats, generating a plan to align them with the template's skills.

The artifact audit checks the internal format of GDDs, not just their presence. It evaluates whether artifacts like GDDs, ADRs, and stories conform to correct internal formats, ensuring structural compliance with the template rather than simply verifying that the files exist.

To start a phase-driven audit workflow for template adoption, run the audit on your repository. This initiates a structured, phase-driven process that evaluates artifacts for template compliance and generates a persistent adoption plan at docs/adoption-plan-[date].md to guide remediation.