content-audit

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

When this skill is invoked:

Parse the argument:

No argument → full audit across all systems
```
[system-name]
```
→ audit that single system only
```
--summary
```
→ summary table only, no file write

调用此Skill时：

解析参数：

无参数 → 对所有系统进行全面审核
```
[system-name]
```
→ 仅审核该单个系统
```
--summary
```
→ 仅生成汇总表格，不写入文件

Phase 1 — Context Gathering

第一阶段 — 上下文收集

Read
design/gdd/systems-index.md
for the full list of systems, their categories, and MVP/priority tier.
L0 pre-scan: Before full-reading any GDDs, Grep all GDD files for
```
## Summary
```
sections plus common content-count keywords:
```
Grep pattern="(## Summary|N enemies|N levels|N items|N abilities|enemy types|item types)" glob="design/gdd/*.md" output_mode="files_with_matches"
```
For a single-system audit: skip this step and go straight to full-read. For a full audit: full-read only the GDDs that matched content-count keywords. GDDs with no content-count language (pure mechanics GDDs) are noted as "No auditable content counts" without a full read.
Full-read in-scope GDD files (or the single system GDD if a system name was given).
For each GDD, extract explicit content counts or lists. Look for patterns like:
- "N enemies" / "enemy types:" / list of named enemies
- "N levels" / "N areas" / "N maps" / "N stages"
- "N items" / "N weapons" / "N equipment pieces"
- "N abilities" / "N skills" / "N spells"
- "N dialogue scenes" / "N conversations" / "N cutscenes"
- "N quests" / "N missions" / "N objectives"
- Any explicit enumerated list (bullet list of named content pieces)
Build a content inventory table from the extracted data:

System Content Type Specified Count/List Source GDD

Note: If a GDD describes content qualitatively but gives no count, record "Unspecified" and flag it — unspecified counts are a design gap worth noting.

**读取
```
design/gdd/systems-index.md
```
**以获取系统完整列表、系统分类以及MVP/优先级层级。
L0预扫描：在完整读取任何GDD之前，使用Grep在所有GDD文件中查找
```
## Summary
```
章节以及常见的内容数量关键词：
```
Grep pattern="(## Summary|N enemies|N levels|N items|N abilities|enemy types|item types)" glob="design/gdd/*.md" output_mode="files_with_matches"
```
若为单系统审核：跳过此步骤，直接进行完整读取。若为全面审核：仅完整读取匹配到内容数量关键词的GDD。对于无内容数量描述的GDD（纯机制类GDD），标记为“无可审核内容数量”，无需完整读取。
完整读取范围内的GDD文件（若指定了系统名称，则读取该单系统的GDD）。
针对每个GDD，提取明确的内容数量或列表。查找以下模式：
- "N enemies" / "enemy types:" / 已命名敌人列表
- "N levels" / "N areas" / "N maps" / "N stages"
- "N items" / "N weapons" / "N equipment pieces"
- "N abilities" / "N skills" / "N spells"
- "N dialogue scenes" / "N conversations" / "N cutscenes"
- "N quests" / "N missions" / "N objectives"
- 任何明确的枚举列表（已命名内容项的项目符号列表）
根据提取的数据构建内容清单表格：

系统内容类型指定数量/列表来源GDD

注意：若GDD仅定性描述内容但未给出数量，记录为“未指定”并标记——未指定数量属于值得关注的设计缺口。

Phase 2 — Implementation Scan

第二阶段 — 实现扫描

For each content type found in Phase 1, scan the relevant directories to count what has been implemented. Use Glob and Grep to locate files.

Levels / Areas / Maps:

Glob

assets/**/*.tscn

assets/**/*.unity

assets/**/*.umap

Glob
```
src/**/*.tscn
```
,
```
src/**/*.unity
```
Look for scene files in subdirectories named
```
levels/
```
,
```
areas/
```
,
```
maps/
```
,
```
worlds/
```
,
```
stages/
```
Count unique files that appear to be level/scene definitions (not UI scenes)

Enemies / Characters / NPCs:

Glob

assets/data/**/enemies/**

assets/data/**/characters/**

Glob
```
src/**/enemies/**
```
,
```
src/**/characters/**
```
Look for
```
.json
```
,
```
.tres
```
,
```
.asset
```
,
```
.yaml
```
data files defining entity stats
Look for scene/prefab files in character subdirectories

Items / Equipment / Loot:

Glob

assets/data/**/items/**

assets/data/**/equipment/**

assets/data/**/loot/**

Look for
```
.json
```
,
```
.tres
```
,
```
.asset
```
data files

Abilities / Skills / Spells:

Glob

assets/data/**/abilities/**

assets/data/**/skills/**

assets/data/**/spells/**

Look for
```
.json
```
,
```
.tres
```
,
```
.asset
```
data files

Dialogue / Conversations / Cutscenes:

Glob

assets/**/*.dialogue

assets/**/*.csv

assets/**/*.ink

Grep for dialogue data files in
```
assets/data/
```

Quests / Missions:

Glob

assets/data/**/quests/**

assets/data/**/missions/**

Look for
```
.json
```
,
```
.yaml
```
definition files

Engine-specific notes (acknowledge in the report):

Counts are approximations — the skill cannot perfectly parse every engine format or distinguish editor-only files from shipped content
Scene files may include both gameplay content and system/UI scenes; the scan counts all matches and notes this caveat

针对第一阶段中发现的每种内容类型，扫描相关目录以统计已实现的内容。使用Glob和Grep定位文件。

关卡/区域/地图：

匹配

assets/**/*.tscn

assets/**/*.unity

assets/**/*.umap

匹配
```
src/**/*.tscn
```
,
```
src/**/*.unity
```
查找名为
```
levels/
```
,
```
areas/
```
,
```
maps/
```
,
```
worlds/
```
,
```
stages/
```
的子目录中的场景文件
统计看起来是关卡/场景定义的唯一文件（排除UI场景）

敌人/角色/NPC：

匹配

assets/data/**/enemies/**

assets/data/**/characters/**

匹配
```
src/**/enemies/**
```
,
```
src/**/characters/**
```
查找定义实体属性的
```
.json
```
,
```
.tres
```
,
```
.asset
```
,
```
.yaml
```
数据文件
查找角色子目录中的场景/预制件文件

物品/装备/战利品：

匹配

assets/data/**/items/**

assets/data/**/equipment/**

assets/data/**/loot/**

查找
```
.json
```
,
```
.tres
```
,
```
.asset
```
数据文件

能力/Skill/法术：

匹配

assets/data/**/abilities/**

assets/data/**/skills/**

assets/data/**/spells/**

查找
```
.json
```
,
```
.tres
```
,
```
.asset
```
数据文件

对话/交谈/过场动画：

匹配

assets/**/*.dialogue

assets/**/*.csv

assets/**/*.ink

在
```
assets/data/
```
中使用Grep查找对话数据文件

任务/使命：

匹配

assets/data/**/quests/**

assets/data/**/missions/**

查找
```
.json
```
,
```
.yaml
```
定义文件

引擎特定说明（需在报告中提及）：

统计结果为近似值——该Skill无法完美解析所有引擎格式，也无法区分仅编辑器文件与发布内容
场景文件可能同时包含游戏玩法内容和系统/UI场景；扫描会统计所有匹配项并注明此限制

Phase 3 — Gap Report

第三阶段 — 差异报告

Produce the gap table:

| System | Content Type | Specified | Found | Gap | Status |
|--------|-------------|-----------|-------|-----|--------|

Status categories:

```
COMPLETE
```
— Found ≥ Specified (100%+)
```
IN PROGRESS
```
— Found is 50–99% of Specified
```
EARLY
```
— Found is 1–49% of Specified
```
NOT STARTED
```
— Found is 0

Priority flags: Flag a system as

HIGH PRIORITY

in the report if:

Status is
```
NOT STARTED
```
or
```
EARLY
```
, AND
The system is tagged MVP or Vertical Slice in the systems index, OR
The systems index shows the system is blocking downstream systems

Summary line:

Total content items specified (sum of all Specified column values)
Total content items found (sum of all Found column values)
Overall gap percentage:
```
(Specified - Found) / Specified * 100
```

生成差异表格：

| System | Content Type | Specified | Found | Gap | Status |
|--------|-------------|-----------|-------|-----|--------|

状态分类：

```
COMPLETE
```
— 已找到数量 ≥ 指定数量（100%及以上）
```
IN PROGRESS
```
— 已找到数量为指定数量的50–99%
```
EARLY
```
— 已找到数量为指定数量的1–49%
```
NOT STARTED
```
— 已找到数量为0

优先级标记： 若满足以下条件，在报告中将系统标记为

HIGH PRIORITY

：

状态为
```
NOT STARTED
```
或
```
EARLY
```
，且
系统在系统索引中标记为MVP或Vertical Slice，或
系统索引显示该系统会阻塞下游系统

汇总行：

指定的内容项总数（所有Specified列值之和）
已找到的内容项总数（所有Found列值之和）
总体差异百分比：
```
(Specified - Found) / Specified * 100
```

Phase 4 — Output

第四阶段 — 输出

Full audit and single-system modes

全面审核和单系统模式

Present the gap table and summary to the user. Ask: "May I write the full report to

docs/content-audit-[YYYY-MM-DD].md

If yes, write the file:

markdown

undefined

向用户展示差异表格和汇总信息。询问：“是否将完整报告写入

docs/content-audit-[YYYY-MM-DD].md

？”

若用户同意，写入文件：

markdown

undefined

Content Audit — [Date]

Summary

Total specified: [N] content items across [M] systems
Total found: [N]
Gap: [N] items ([X%] unimplemented)
Scope: [Full audit | System: name]

Note: Counts are approximations based on file scanning. The audit cannot distinguish shipped content from editor/test assets. Manual verification is recommended for any HIGH PRIORITY gaps.

Total specified: [N] content items across [M] systems
Total found: [N]
Gap: [N] items ([X%] unimplemented)
Scope: [Full audit | System: name]

Note: Counts are approximations based on file scanning. The audit cannot distinguish shipped content from editor/test assets. Manual verification is recommended for any HIGH PRIORITY gaps.

Gap Table

System	Content Type	Specified	Found	Gap	Status

System	Content Type	Specified	Found	Gap	Status

HIGH PRIORITY Gaps

[List systems flagged HIGH PRIORITY with rationale]

Per-System Breakdown

[System Name]

GDD:
```
design/gdd/[file].md
```
Content types audited: [list]
Notes: [any caveats about scan accuracy for this system]

GDD:
```
design/gdd/[file].md
```
Content types audited: [list]
Notes: [any caveats about scan accuracy for this system]

Recommendation

Focus implementation effort on:

[Highest-gap HIGH PRIORITY system]
[Second system]
[Third system]

Focus implementation effort on:

[Highest-gap HIGH PRIORITY system]
[Second system]
[Third system]

Unspecified Content Counts

The following GDDs describe content without giving explicit counts. Consider adding counts to improve auditability: [List of GDDs and content types with "Unspecified"]


After writing the report, ask:

> "Would you like to create backlog stories for any of the content gaps?"

If yes: for each system the user selects, suggest a story title and point them
to `/create-stories [epic-slug]` or `/quick-design` depending on the size of the gap.

The following GDDs describe content without giving explicit counts. Consider adding counts to improve auditability: [List of GDDs and content types with "Unspecified"]


写入报告后，询问：

> "是否为内容差异创建待办事项？"

若用户同意：针对用户选择的每个系统，建议一个事项标题，并引导用户根据差异大小使用`/create-stories [epic-slug]`或`/quick-design`。

--summary mode

--summary模式

Print the Gap Table and Summary directly to conversation. Do not write a file. End with: "Run

/content-audit

without

--summary

to write the full report."

直接在对话中打印差异表格和汇总信息，不写入文件。结尾提示：“运行

/content-audit

且不带

--summary

参数即可写入完整报告。”

Phase 5 — Next Steps

第五阶段 — 后续步骤

After the audit, recommend the highest-value follow-up actions:

If any system is
```
NOT STARTED
```
and MVP-tagged → "Run
```
/design-system [name]
```
to add missing content counts to the GDD before implementation begins."
If total gap is >50% → "Run
```
/sprint-plan
```
to allocate content work across upcoming sprints."
If backlog stories are needed → "Run
```
/create-stories [epic-slug]
```
for each HIGH PRIORITY gap."
If
```
--summary
```
was used → "Run
```
/content-audit
```
(no flag) to write the full report to
```
docs/
```
."

Verdict: COMPLETE — content audit finished.

审核完成后，推荐最高价值的后续操作：

若有标记为MVP的系统处于
```
NOT STARTED
```
状态 → “运行
```
/design-system [name]
```
在开始实现前为GDD补充缺失的内容数量。”
若总差异占比>50% → “运行
```
/sprint-plan
```
在即将到来的迭代中分配内容开发工作。”
若需要待办事项 → “针对每个HIGH PRIORITY差异运行
```
/create-stories [epic-slug]
```
。”
若使用了
```
--summary
```
模式 → “运行
```
/content-audit
```
（不带参数）将完整报告写入
```
docs/
```
目录。”

结论：COMPLETE — 内容审核完成。