Translation Comparison - design-review

When this skill is invoked:

Read the target design document in full.
Read the master CLAUDE.md to understand project context and standards.
Read related design documents referenced or implied by the target doc (check
```
design/gdd/
```
for related systems).
Evaluate against the Design Document Standard checklist:
- Has Overview section (one-paragraph summary)
- Has Player Fantasy section (intended feeling)
- Has Detailed Rules section (unambiguous mechanics)
- Has Formulas section (all math defined with variables)
- Has Edge Cases section (unusual situations handled)
- Has Dependencies section (other systems listed)
- Has Tuning Knobs section (configurable values identified)
- Has Acceptance Criteria section (testable success conditions)
Check for internal consistency:
- Do the formulas produce values that match the described behavior?
- Do edge cases contradict the main rules?
- Are dependencies bidirectional (does the other system know about this one)?
Check for implementability:
- Are the rules precise enough for a programmer to implement without guessing?
- Are there any "hand-wave" sections where details are missing?
- Are performance implications considered?
Check for cross-system consistency:
- Does this conflict with any existing mechanic?
- Does this create unintended interactions with other systems?
- Is this consistent with the game's established tone and pillars?
Output the review in this format:

undefined

调用该技能时执行以下操作：

完整阅读目标设计文档
阅读主CLAUDE.md文件，了解项目上下文和标准规范。
阅读目标文档引用或关联的相关设计文档 （可在
```
design/gdd/
```
目录下查找相关系统文档）。
对照设计文档标准检查清单进行评估：
- 包含概述部分（单段落总结）
- 包含玩家预期体验部分（想要传递给玩家的感受）
- 包含详细规则部分（清晰无歧义的机制说明）
- 包含公式部分（所有计算逻辑都有明确定义的变量）
- 包含边界情况部分（对异常场景的处理说明）
- 包含依赖项部分（列出所有关联的其他系统）
- 包含可调参数部分（明确所有可配置的数值）
- 包含验收标准部分（可测试的成功判定条件）
检查内部一致性：
- 公式输出的数值是否与描述的行为匹配？
- 边界情况处理是否与主规则冲突？
- 依赖关系是否双向互通（关联的其他系统是否知晓该系统的存在）？
检查可实现性：
- 规则是否足够精准，程序员无需猜测即可实现？
- 是否存在缺失细节、模糊带过的部分？
- 是否考虑了性能影响？
检查跨系统一致性：
- 该设计是否与现有任何机制冲突？
- 该设计是否会与其他系统产生预期外的交互？
- 该设计是否符合游戏已确立的调性和核心设计原则？
按照以下格式输出评审结果：

undefined

Design Review: [Document Title]

Completeness: [X/8 sections present]

[List missing sections]

Consistency Issues

[List any internal or cross-system contradictions]

Implementability Concerns

[List any vague or unimplementable sections]

Balance Concerns

[List any obvious balance risks]

Recommendations

[Prioritized list of improvements]

Verdict: [APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED]


9. **Contextual next step recommendations**:
   - If the document being reviewed is `game-concept.md` or `game-pillars.md`:
     - Check if `design/gdd/systems-index.md` exists
     - If it does NOT exist, add to Recommendations:
       > "This concept is ready for systems decomposition. Run `/design-systems`
       > to break it down into individual systems with dependencies and priorities,
       > then write per-system GDDs."
   - If the document is an individual system GDD:
     - Check if the systems index references this system
     - If so, suggest updating its status: "Update the systems index status for
       this system from 'In Design' to 'Designed'."


9. **上下文相关的下一步建议**：
   - 如果评审的是`game-concept.md`或`game-pillars.md`文档：
     - 检查`design/gdd/systems-index.md`是否存在
     - 如果不存在，在建议中添加：
       > "该概念已就绪可进行系统拆解。运行`/design-systems`将其拆解为带有依赖关系和优先级的独立系统，之后编写各系统的GDD。"
   - 如果评审的是单个系统的GDD：
     - 检查系统索引文件是否引用了该系统
     - 如果已引用，建议更新其状态："将该系统在系统索引中的状态从'设计中'更新为'已设计'。"

design-review

Original

Translation

Design Review: [Document Title]

Design Review: [Document Title]

Completeness: [X/8 sections present]

Completeness: [X/8 sections present]

Consistency Issues

Consistency Issues

Implementability Concerns

Implementability Concerns

Balance Concerns

Balance Concerns

Recommendations

Recommendations

Verdict: [APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED]

Verdict: [APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED]