adopt

To audit existing game project artifacts for template format compliance, run a brownfield audit that scans GDDs, ADRs, stories, and infrastructure to verify required section headings and fields are present. This process classifies structural gaps by severity.

A brownfield migration plan for in-progress game development projects is a prioritized, numbered checklist that remediates template format gaps. It guides the upgrade of existing artifacts like GDDs and ADRs to meet newer template requirements.

To check ADR readiness and GDD structure when joining a project midstream, execute a targeted audit that reads key stage and technical preference files. This validates required internal formats and identifies blocking gaps in the documentation.

Yes, you can limit the scope of a brownfield audit to only stories or infrastructure files. By specifying a scope parameter like stories or infra, the audit focuses solely on those artifacts and generates a scoped migration plan.

The best way to prioritize remediation for mismatched project templates is to classify detected format gaps into BLOCKING, HIGH, MEDIUM, and LOW severity levels. This severity-classified approach provides clear ordering for fixing structural issues.

Downstream skills fail silently when existing project artifacts do not match template formats because they expect specific internal section headings and fields. Running an adoption audit detects these structural mismatches before they cause incorrect outputs.