Audit GDD-specified content counts and lists against implemented repository content.
npx skills add https://github.com/WindXRan/y3td --skill content-audit-windxran
Please help me install this Agent Skill. Skill: content-audit Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/content-audit Command: npx skills add https://github.com/WindXRan/y3td --skill content-audit-windxran
It eliminates uncertainty about whether GDD-specified content (counts and lists) has been fully implemented, by producing an auditable comparison between design intent and repository implementation.
design/gdd system GDDs into a structured inventory.Run the content-audit skill to compare all systems’ GDD-specified content against what’s present in the codebase and assets.
High-intent search queries and answers about installing and using this skill.
To check if implemented content matches your Game Design Document, you need a spec-to-code gap analysis comparing GDD-specified counts against repository assets. This skill extracts explicit content lists and scans your repo to reveal planned-versus-built gaps.
A content audit for game production parses GDD `## Summary` sections to extract specified counts for levels, enemies, items, and quests, then scans the repository to generate a gap table flagging missing items for backlog planning.
Tracking GDD implementation progress involves scanning your repository by content type and comparing it against design specs. This skill outputs a structured gap table with statuses like COMPLETE, IN PROGRESS, or NOT STARTED for each system.
Yes, you can audit a single game system's implementation status. This skill applies to both full-project and single-system checks, allowing targeted gap analysis for specific levels, characters, abilities, or dialogue sets.
Missing game assets are prioritized in a gap analysis report by flagging HIGH PRIORITY gaps for MVP, Vertical Slice, or blocking systems. This ensures critical path content for game production is addressed first in backlog planning.
Yes, the content audit requires parsing GDDs that use a `## Summary` section and explicit content-count language. It relies on these structured design documents to extract specified lists for levels, enemies, items, abilities, dialogue, and quests.
scomofoAudit GDD-specified content against implemented repository files.
johnatas-henriqueAudits game design documents against implemented project assets to identify content gaps.
polseguCompare GDD-specified content counts against repository assets to identify missing game content.
dnkrowAudit GDD-specified content counts against implemented assets and data files.