Audit game development documentation against implemented content and report discrepancies.
npx skills add https://github.com/LeKay/ai-game --skill content-audit-lekay
Please help me install this Agent Skill. Skill: content-audit Source: https://github.com/LeKay/ai-game/tree/main/.claude/skills/content-audit Command: npx skills add https://github.com/LeKay/ai-game --skill content-audit-lekay
This Skill helps streamline the process of auditing content in a game development project, ensuring that planned features are implemented and progress is tracked effectively.
Run 'content-audit' to initiate a full content audit or specify a system with 'content-audit system-name'.
High-intent search queries and answers about installing and using this skill.
To audit game design documents against implemented content, you run a full content audit that scans asset directories to identify discrepancies. It utilizes file scanning and Grep to compare planned features with actual project assets.
You can generate a gap report for missing game development features by running a content audit. The audit produces detailed Markdown reports highlighting discrepancies between your planned design documents and the implemented project content.
The best way to track planned versus implemented game systems is by running a targeted system audit. This process scans specific game system directories and provides a summary table comparing documented features against actual implemented assets.
You need access to game design documents and asset directories to perform design document analysis. The audit utilizes Glob and Grep for content analysis and outputs the resulting gap reports directly in Markdown format.
Yes, you can audit a specific game system by specifying the system name when initiating the audit. This focuses the file scanning and discrepancy analysis on that single system rather than scanning the entire project.
sumilee-pcuParse design documents and scan project directories to calculate game content gap metrics.
samdaeAnalyze architecture design documents to identify missing or ambiguous implementation details.
zerAdaCreate phases to close gaps from milestone audit results.
s0613Verifies implemented software features against original product requirement documents.
