adopt

A brownfield migration audit validates existing GDD, ADR, story, and infrastructure artifacts against template format compliance by checking required headings, internal fields, and placeholder-content risks. It classifies gaps into blocking, high, medium, and low tiers to prevent downstream pipeline skills from silently misbehaving.

Migrating an in-progress project safely requires auditing existing artifacts for format compliance and generating a prioritized, numbered migration plan. This plan classifies gaps into blocking, high, medium, and low tiers, ensuring downstream template pipeline skills do not silently break during the brownfield migration.

Downstream pipeline skills break when existing artifacts lack required internal formats, such as missing ADR Status headings or invalid parenthetical status values in systems-index.md. These brownfield gating risks cause template skills to silently misbehave if not triaged before adoption.

Yes, you can run a scoped audit targeting only ADRs, GDDs, stories, or infrastructure artifacts by passing the corresponding argument. This restricts the format compliance check and migration plan generation to the specified document type instead of running a full project audit.

A brownfield migration plan is a prioritized, checkable document generated at docs/adoption-plan-[date].md. It provides an ordered list of format compliance gaps classified by severity tiers, guiding the safe adoption of a template into an in-progress project.