content-audit

To audit Godot game assets against a game design document, this skill scans project directories to extract implemented content counts and compares them against GDD specifications to classify completion gaps. It requires access to system indexes and engine-specific asset formats to produce prioritized reports.

Finding missing game content before production planning requires comparing planned design specifications with implemented project assets. This skill reads GDD files to identify specified enemies, levels, and quests, then scans implementation directories to calculate overall coverage and highlight high-priority MVP gaps.

You can check the implementation status of a single game system by invoking the audit with a specific system name like quests or dialogue. This focused audit investigates current production status for that targeted system rather than running a full project scan.

The content audit tool works with Godot engine project structures by scanning engine-specific asset formats within implementation directories. It applies to game production planning scenarios involving levels, enemies, characters, items, abilities, dialogue, and quests across the project hierarchy.

To generate a gap report comparing planned game content with implemented assets, the skill classifies completion status and calculates overall coverage. It optionally writes a dated audit report highlighting high-priority MVP gaps found between GDD requirements and actual implementation.

Preparing for a game content audit requires access to GDD files, system indexes, and implementation directories. These inputs allow the skill to extract specifications, scan assets, classify gaps, and produce prioritized reports comparing planned content with implemented game assets.