content-audit

Audit GDD-specified content counts against implemented XR/game assets.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/imclab/xrA1-swarm --skill content-audit-imclab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-audit
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/content-audit
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill content-audit-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the confusion and missed scope that happen when GDD-specified content counts and lists don’t match what has been implemented yet.

Core Features & Use Cases

  • Plans-to-Implementation Audit: Compares GDD “specified” content (counts/lists) against a scan of implemented assets and data files.
  • Multi-System Gap Reporting: Produces a per-system content gap table with COMPLETE / IN PROGRESS / EARLY / NOT STARTED status and HIGH PRIORITY flags.
  • Optional Fast Summary: Supports a summary-only mode so teams can quickly assess overall gaps without writing a report file.

Quick Start

Run content-audit with no arguments to perform a full audit across all systems and produce a gap report you can review.

Frequently Asked Questions about content-audit

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

FAQPage Schema
How do I audit game content against GDD specifications to find implementation gaps?

To audit game content, compare GDD-specified counts against implemented assets by scanning file globs and grep patterns. This produces a structured gap table with priority flags quantifying planned versus built content for levels, enemies, items, and quests.

What is a content audit for game design documentation?

A content audit for game design documentation validates what is planned versus what is built. It scans GDD summaries and implemented XR or game assets to extract explicit counts, generating a per-system gap table with COMPLETE, IN PROGRESS, or NOT STARTED statuses.

Can I check implementation progress for a single game system instead of the whole repository?

Yes, you can perform a single-system audit instead of a full-repository scan. The audit applies targeted file globs and grep patterns to specific systems like levels, abilities, or dialogue, producing a focused gap table with HIGH PRIORITY flags.

Do I need to generate a report file to review GDD content gaps?

No, you do not need to generate a report file to review GDD content gaps. You can use a summary-only mode to quickly assess overall gaps across systems without writing a report file, or use optional write-to-docs behavior for full reports.

How do I prioritize missing game assets during development?

Prioritize missing game assets by generating a structured gap table from your GDD and implementation scan. The table assigns COMPLETE, IN PROGRESS, EARLY, or NOT STARTED statuses alongside HIGH PRIORITY flags to help quantify and prioritize remaining content work.