content-audit

To compare your Game Design Document against implemented game assets, run a content audit by parsing systems-index and GDD summaries, then scanning repository files for matching content types. This produces a structured gap table showing planned versus built elements.

Design-implementation drift occurs when your built game assets deviate from GDD specifications. You identify missing content by auditing specified counts of enemies, levels, or quests against file-system findings, generating a gap table that flags high-priority missing elements.

Yes, you can run a focused gap analysis for a single game system by passing the system name as an argument. This restricts the file scanning and GDD validation to that specific system rather than auditing the entire project portfolio.

Yes, content audit requires YAML-defined metadata-driven activation. You need structured GDD summaries and a systems-index in your repository so the deterministic parser can locate and scan the correct file types for the gap analysis.

You validate MVP or vertical-slice scope by auditing GDD-specified content against implemented project assets. The audit generates a backlog gap table with completeness status, highlighting exactly what planned game content is missing from your current build.

The best way to track planned versus built content is deterministic file scanning using tools like Grep and Glob to locate implemented assets. This scope tracking method directly compares file-system findings against your GDD counts to prevent production drift.