content-audit

Auditing game design document content counts against implemented assets involves parsing Markdown GDD files and scanning project asset trees using file reads, glob, and grep to identify design-to-implementation gaps and optionally write a dated Markdown report.

Design-to-implementation gap analysis for game development cross-references GDD-specified content counts with implemented codebase and asset files, revealing discrepancies between planned systems, enemies, levels, items, abilities, dialogues, and missions and actual project assets.

Yes, you can run a single-system audit for a targeted feature branch in Godot. The audit supports a single-system mode that isolates checks to specific systems rather than scanning the entire project asset and source tree.

The content audit optionally writes a dated Markdown report to the docs folder, automatically generating a file named content-audit-[YYYY-MM-DD].md. Alternatively, use the --summary mode to print results to the console without writing files.

The best way to find missing MVP systems before sprint planning is running a full content audit that compares GDD specifications against implemented game assets, surfacing high-priority design-to-implementation gaps in systems, levels, and missions.