What problem does it solve? Game projects drift out of sync with their design documents: GDDs specify enemies, levels, items, and quests, but nobody tracks how much of that content is actually implemented. This Skill compares planned content counts against files present in the project and reports the gap. ## Core Features & Use Cases - GDD Content Extraction: Parses design documents for explicit content counts (enemies, levels, items, abilities, dialogue, quests) and flags GDDs with unspecified counts. - Implementation Scanning: Searches scene files (.tscn, .unity, .umap) and data files (.json, .tres, .asset, .yaml) across engine-specific directory conventions to count built content. - Gap Reporting: Produces a status table (COMPLETE, IN PROGRESS, EARLY, NOT STARTED) with HIGH PRIORITY flags for MVP-tagged systems, plus an optional dated report written to docs/. - Use Case: Before a sprint review, run a full audit to discover that the GDD specifies 12 enemy types but only 4 exist as data files, then generate backlog stories for the gap. ## Quick Start Ask the AI to run a content audit comparing the GDD-specified content counts against the implemented content in this project and report the gaps.