skills.rest
cenconq25
cenconq25COMMUNITY
Explore all skills by this author →
GitHub

content-audit

Compare PRD content plans against implemented codebase assets and output a read-only report.

39|6|Updated May 3, 2026
Search Tags:#onboarding#assets#prd#report#screens#locales#content-audit
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill content-audit-cenconq25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: content-audit
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/content-audit
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill content-audit-cenconq25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compares PRD content commitments with the live implementation to reveal gaps in screens, strings, locales, and assets.

Core Features & Use Cases

  • Inventory PRD-stated content (screens, locales, onboarding steps, assets) and compare against codebase.
  • Generate a read-only report highlighting planned vs implemented content to guide pre-release checks.
  • Use during sprint planning to track progress and inform localization or asset work.

Quick Start

Run the content audit to compare PRD content plans against the current repository and generate a read-only report.

Frequently Asked Questions about content-audit

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

FAQPage Schema
How do I audit gaps between PRD content plans and the implemented codebase assets?▼

A content audit identifies gaps between PRD content plans and implemented codebase assets by parsing PRD documents, inventorying live content using standard file patterns, and outputting a read-only report highlighting planned versus implemented screens, strings, and locales.

What is PRD content gap analysis used for during pre-release checks?▼

PRD content gap analysis compares planned screens, copy, locales, images, and onboarding steps against the live implementation. It is used for pre-release checks, mid-sprint validation, and post-copy readiness to reveal missing assets before deployment.

Can I track localization progress by comparing PRD commitments against implemented locales?▼

Yes, you can track localization progress by inventorying PRD-stated locales and comparing them against the codebase. The generated report highlights planned versus implemented content, informing localization work during sprint planning.

Does a content audit require specific dependencies or components to parse PRD documents?▼

No specific dependencies or components are required. The content audit parses PRD documents outlining screens and assets, inventories implemented content using standard file patterns, and generates a read-only report without needing external modules.

What is the best way to validate onboarding steps and push categories before a release?▼

The best way to validate onboarding steps and push categories is running a content audit. It compares PRD commitments against the repository's implemented content, generating a read-only gap report for pre-release checks and mid-sprint validation.

Related Skills

Explore More Product & Management Skills→
JonahSussmanJonahSussman

spec-driven-translation

Translate and modernize codebases through PRD, specification, and implementation plans.

Community
Advanced
MichaelSolatiMichaelSolati

content-audit

Audit GDD content against implemented game assets to identify gaps.

Community
Advanced
SeongHuniSeongHuni

asset-audit

Audit game assets for naming, size, format, and pipeline compliance.

Community
Advanced
MmtBknMmtBkn

swe-tdd

Convert PRDs into E2E test specification documents with traceability maps.

Community
Advanced