content-audit

Name: content-audit
Availability: InStock
Author: kay6198835

Audit GDD-specified content counts against implemented content across systems.

Updated Feb 8, 2024

Search Tags:#grep #game-design #gdd #globbing #content-audit #audit-automation #content-counts

Ready to run

npx skills add https://github.com/kay6198835/Game-RPG --skill content-audit-kay6198835

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: content-audit
Source: https://github.com/kay6198835/Game-RPG/tree/main/.claude/skills/content-audit
Command: npx skills add https://github.com/kay6198835/Game-RPG --skill content-audit-kay6198835

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit GDD-specified content counts against implemented content. Identifies what's planned vs built.

Core Features & Use Cases

System-wide audits across all GDDs to verify planned content vs implemented content.
Single-system audits for targeted systems.
Summary mode to produce a high-level overview without writing files.

Quick Start

Run the content-audit with no arguments to perform a full audit across all systems, or pass a system name to audit a single system, or use --summary to generate only the summary table.

Frequently Asked Questions about content-audit

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

FAQPage Schema

How do I audit GDD content counts against implemented game assets?▼

To audit GDD content counts against implemented game assets, run a full system-wide scan comparing design/gdd specifications with inventoried assets to surface gaps. It verifies planned content versus built content across all systems.

Can I check what content is planned vs built for a single game system?▼

Yes, you can check planned vs built content for a single game system by passing the specific system name as an argument. This executes a targeted single-system audit instead of scanning all GDDs.

What is a GDD content audit and when do I need to run one?▼

A GDD content audit is a verification process comparing game design document specifications against actual implemented assets. Run an audit when tracking development progress and identifying missing content across systems.

How do I generate a summary overview of game content gaps without writing files?▼

To generate a summary overview of game content gaps without writing files, execute the audit using the --summary flag. This produces a high-level summary table showing planned versus implemented content counts.

Does the content audit automation support globbing and grep for scanning design files?▼

Yes, the content audit automation supports globbing and grep operations for scanning design/gdd files to extract specified content counts. It inventories implemented assets to surface gaps between planned and built content.

What is the best way to track game design document progress against actual development?▼

The best way to track game design document progress against actual development is running audit automation that scans GDDs for content counts and inventories implemented assets. This surfaces gaps between planned and built systems.