adopt

To audit brownfield project artifacts for template compliance, scan design docs, ADRs, and stories to classify format gaps by impact. This generates a prioritized migration plan saved as docs/adoption-plan-[date].md for stepwise remediation.

The best way to generate a migration plan for an in-progress project is to run an audit across design, production, docs, and standards artifacts. This produces a written, prioritized adoption roadmap to align the project with template skills.

Yes, the brownfield audit supports targeted scanning modes including cdds, adrs, stories, and infra. These modes tailor the scan scope to specific artifact types, ensuring focused compliance verification before generating the remediation workflow.

You can upgrade an older template version without manual checks by running a full audit mode. This automatically reads project artifacts across all categories, verifies format compliance, and outputs a stepwise migration plan for user approval.

A template compliance check is needed for brownfield governance to ensure existing artifacts remain compatible with the template's skills. It classifies structural gaps by impact, enabling a prioritized migration plan that aligns project standards.

Automated artifact migration planning limitations include requiring user approval for stepwise remediation and relying on reading existing project artifacts across design, docs, and standards. It audits format compliance rather than rewriting files automatically.