content-audit

Name: content-audit
Availability: InStock
Author: scomofo

Audit GDD-specified content against implemented repository files.

Updated Mar 28, 2026

Search Tags:#content audit #gdd #file scanning #backlog planning #implementation gap #godot project #coverage reporting

Ready to run

npx skills add https://github.com/scomofo/dragon-forge --skill content-audit-scomofo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: content-audit
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/content-audit
Command: npx skills add https://github.com/scomofo/dragon-forge --skill content-audit-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Content plans in GDDs often drift from what’s actually implemented, making it hard to see what’s missing, incomplete, or overbuilt.

Core Features & Use Cases

Counts-to-code auditing: Compares explicit content counts and enumerated lists in GDDs against what exists in the repository via file scanning.
System-scoped or whole-repo coverage: Audits a single system when you provide a system name, or audits all systems when you don’t.
Gap reporting for execution: Produces a structured gap table with statuses like COMPLETE, IN PROGRESS, EARLY, and NOT STARTED, plus HIGH PRIORITY flags for MVP/vertical-slice/blocking gaps.
Optional report writing: Writes a dated report to docs/ unless you use summary-only mode.

Quick Start

Run the content-audit skill with no arguments to audit all systems against the content counts specified in the GDDs.

Frequently Asked Questions about content-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check if my Godot project implementation matches the GDD content counts?▼

To check if your Godot project matches the GDD, run a content audit to parse GDD summary language and scan tracked asset and scene files. This quantifies planned versus built content and identifies implementation gaps.

What is the best way to find spec gaps between a game design document and a repository?▼

Finding spec gaps requires a two-phase content audit: first extracting explicit counts and enumerated lists from the GDD, then scanning repository files to produce a structured gap table with status and priority classifications.

Can I scope a file scanning audit to a single system instead of the whole repo?▼

Yes, you can scope the audit to a single system by providing a system name argument. If you run the audit with no arguments, it defaults to auditing all systems against the content counts specified in the GDDs.

Does backlog planning require a dated gap report written to the docs directory?▼

Backlog planning uses a dated gap report written to the docs directory by default, containing statuses like COMPLETE and NOT STARTED with HIGH PRIORITY flags. Use summary-only mode to skip writing the full report file.

How does coverage reporting classify MVP blocking gaps during a content audit?▼

Coverage reporting classifies MVP blocking gaps using statuses like COMPLETE, IN PROGRESS, EARLY, and NOT STARTED, and applies HIGH PRIORITY flags to gaps that block MVP or vertical-slice development milestones.