GDD Requirements Addressed【免费下载链接】Claude-Code-Game-StudiosTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.项目地址: https://gitcode.com/GitHub_Trending/cl/Claude-Code-Game-StudiosGDD SystemRequirementHow This ADR Addresses It[system-name].md[specific rule, formula, or performance constraint from that GDD][how this decision satisfies it]--- ## 3. 阶段 1–3参数校验与变更识别 ### 3.1 校验参数阶段 1 GDD 路径参数是**必需**的缺参直接失败并提示 Usage: /propagate-design-change design/gdd/[system].md Provide the path to the GDD that was changed. 随后校验文件存在性不存在则报 [path] not found. Check the path and try again. ### 3.2 读取当前版本与历史版本阶段 2–3 先完整读取变更后的 GDD再通过 git 获取上一提交版本 bash git show HEAD:design/gdd/[filename].md这里存在两条重要分支新文件无历史报告 No previous version in git — this appears to be a new GDD, not a revision. Nothing to propagate.——新 GDD 没有旧假设可失效直接结束传播存在历史版本做概念性差异conceptual diff重点识别新增规则、删除规则、公式修改、验收标准变化、调优旋钮tuning knobs变化同时标记未变化章节。差异结果整理为变更摘要其模板为## Change Summary: [GDD filename] Date of revision: [today] Changed sections: - [Section name]: [what changed — new rule, removed rule, formula modified, etc.] Unchanged sections: - [Section name] Key changes affecting architecture: - [Change 1 — likely to affect ADRs] - [Change 2]仓库佐证这种旧版对当前版的比对逻辑与 docs/architecture/tr-registry.yaml 的修订纪律一脉相承——需求被改写意图不变时保留 ID 并加revised日期需求被删除时标记deprecated被拆分/替换时标记superseded-by。变更摘要中公式修改与调优旋钮变化正是最可能触发 TR-ID 状态变更的源头。4. 阶段 4加载架构输入读取docs/architecture/下全部 ADR对每个 ADR完整读取文件提取## GDD Requirements Addressed表格记录该 ADR 引用了哪些 GDD 文档及需求 ID。随后读取docs/architecture/architecture-traceability.md若存在并报告Loaded [N] ADRs. [M] reference [gdd filename].仓库佐证可追溯性索引的定位可在 architecture-review SKILL 第 8 阶段看到——该技能输出的索引文件包含 Coverage Summary、Full Matrix、Known Gaps 以及Superseded RequirementsRequirements whose GDD was changed after the ADR was written。换句话说architecture-review负责建索引propagate-design-change负责在 GDD 变更后让索引中过期条目被识别并处置。此外gate-check SKILL 的 Technical Setup → Pre-Production 门禁把architecture traceability index exists列为必需产物说明该索引是架构可追溯性的正式载体。5. 阶段 5影响分析核心方法论对每个引用了被变更 GDD 的 ADR逐条比对GDD Requirements Addressed条目与 GDD 的变更章节定位需求该需求在当前 GDD 中是否仍然存在对比ADR 撰写时 GDD 的说法 vs. 现在的说法评估该架构决策是否仍然成立。每个受影响 ADR 被归入三态之一状态含义✅Still ValidGDD 变更不影响该 ADR 的决策内容⚠️Needs ReviewGDD 变更可能影响该 ADR —— 需要人工判断Likely SupersededGDD 变更与该 ADR 的假设直接矛盾每个受影响 ADR 产出如下影响条目含引语级证据### ADR-NNNN: [title] Status: [Still Valid / Needs Review / Likely Superseded] What the ADR assumed about this GDD: [relevant quote from the ADRs GDD Requirements Addressed section] What the GDD now says: [relevant quote from the current GDD] Assessment: [Explanation of whether the ADR decision is still valid, and why] Recommended action: [Keep as-is | Review and update | Mark Superseded and write new ADR]仓库佐证三态分类的矛盾检测语义与 architecture-review SKILL 第 4 阶段的 Cross-ADR Conflict Detection 互补——后者检测ADR 之间的矛盾数据所有权冲突、接口契约冲突、性能预算冲突、依赖环、模式冲突、状态管理冲突而本技能检测ADR 与 GDD 之间随时间推移产生的失配。推荐动作中的 Mark Superseded and write new ADR 对应 architecture-decision SKILL 中的 ADR 状态枚举[Proposed | Accepted | Deprecated | Superseded by ADR-XXXX]。6. 阶段 6呈现影响报告关键纪律在询问任何行动之前先把完整影响报告呈现给用户。报告格式## Design Change Impact Report GDD: [filename] Date: [today] Changes detected: [N sections changed] ADRs referencing this GDD: [M] ### Not Affected [ADRs referencing this GDD whose decisions remain valid] ### Needs Review ([count]) [ADRs that may need updating] ### Likely Superseded ([count]) [ADRs whose assumptions are now contradicted]这一先展示全貌、再征求意见的协作模式在 .claude/docs/review-workflow.md 中有制度性背书Architecture changes require sign-off fromtechnical-director——架构变更的最终确认权在技术总监而技术总监代理的协作协议.claude/agents/technical-director.md明确你是最高层的顾问但所有最终战略决策由用户做出因此报告必须完整、可读、证据充分让用户能基于事实决策。7. 阶段 6b导演门禁 TD-CHANGE-IMPACT在派生子代理之前必须先做审查模式Review Mode检查。审查模式全局配置存放在production/review-mode.txt单行full、lean或solo由/start初始化可直接编辑文件修改每次技能运行时也可用--review [full|lean|solo]参数覆盖仅对当次运行生效详见 .claude/docs/director-gates.md。本技能的门禁检查逻辑solo→ 跳过记录 TD-CHANGE-IMPACT skipped — Solo mode.直接进入阶段 7lean→ 跳过记录 TD-CHANGE-IMPACT skipped — Lean mode.直接进入阶段 7full→ 正常派生。在full模式下通过Task以门禁TD-CHANGE-IMPACT定义于 .claude/docs/director-gates.md派生technical-director子代理传入阶段 6 的完整影响报告变更摘要、全部受影响 ADR 及其三态分类、推荐动作。技术总监审查三件事影响分类是否正确是否存在被低估分类的 ADR推荐动作在架构上是否成立是否遗漏了对其他 ADR 或系统的级联影响。裁决处理APPROVE→ 进入阶段 7 解决工作流CONCERNS→ 用AskUserQuestion呈现被标记的 ADR/建议选项为Revise the impact assessment/Accept with noted concerns/Discuss furtherREJECT→ 不得进入解决阶段需重新分析影响。仓库佐证门禁的裁决格式约定在 .claude/agents/technical-director.md 的## Gate Verdict Format节当通过导演门禁被调用时如TD-CHANGE-IMPACT响应第一行必须是独立的裁决 token[GATE-ID]: APPROVE/CONCERNS/REJECT调用方技能读取第一行获取裁决 token——本技能第 6b 阶段的应用裁决逻辑正是消费这一约定的标准流程。此外.claude/docs/director-gates.md 定义了三种模式的含义full全量门禁适合团队/学习型用户、lean仅 PHASE-GATE默认适合独立开发者、solo完全无门禁适合 Game Jam 与原型冲刺。8. 阶段 7解决工作流对每个标记为 Needs Review 或 Likely Superseded 的 ADR逐个征询用户意见不批量决策每个 ADR 可能有不同处置ADR-NNNN ([title]) — [status]. What would you like to do? Options:Mark Superseded (Ill write a new ADR) — updates ADR status line toSuperseded by: [pending]Update in place (minor revision) — opens the ADR for editing; note what to reviseKeep as-is (the change doesnt actually affect this decision)Skip for now (revisit later)对标记为Superseded的 ADR更新其 Status 字段为Superseded by ADR-[next number] (pending — see change-impact-[date]-[system].md)询问用户May I update the status in [ADR filename]?仓库佐证Superseded by ADR-[next number]的编号语义与 architecture-decision SKILL 阶段 2扫描docs/architecture/确定下一个 ADR 编号一致ADR 模板中## Status节.claude/docs/templates/architecture-decision-record.md的合法值即为[Proposed | Accepted | Deprecated | Superseded by ADR-XXXX]。同时注意非破坏性原则见第 10 节协作协议绝不删除 ADR 内容只追加 Superseded by 注记这与 TR 注册表ID 永久、绝不删除的哲学同源。9. 阶段 8更新可追溯性索引若docs/architecture/architecture-traceability.md存在将被变更的 GDD 需求追加到 Superseded Requirements 表## Superseded Requirements | Date | GDD | Requirement | Changed To | ADRs Affected | Resolution | |------|-----|-------------|------------|---------------|------------| | [date] | [gdd] | [old requirement text] | [new requirement text] | ADR-NNNN | [Superseded/Updated/Valid] |随后询问May I update the traceability index?仓库佐证该表与 architecture-review SKILL 阶段 8 中索引文件的## Superseded Requirements区块Requirements whose GDD was changed after the ADR was written完全对应——propagate-design-change负责向该表写入新条目而architecture-review负责在后续全量审查中消费这些条目其第 5b 阶段Design Revision Flags会把 GDD 中与已验证引擎行为/已接受 ADR 冲突的假设标记为待修订。两者一写一读构成可追溯性闭环。10. 阶段 9–10落盘变更影响文档与后续行动10.1 输出变更影响文档阶段 9询问May I write the change impact report todocs/architecture/change-impact-[date]-[system-slug].md?文档包含四部分内容阶段 3 的变更摘要阶段 5 的完整影响分析阶段 7 做出的解决决策需要新写或更新的 ADR 清单。裁决规则用户批准写入 → Verdict:COMPLETE— change impact report saved用户拒绝 → Verdict:BLOCKED— user declined write。10.2 后续行动建议阶段 10根据解决决策给出闭环建议被标记 Superseded 的 ADRRun/architecture-decision [title]to write the replacement ADR. Then re-run/propagate-design-changeto verify coverage.先写替代 ADR再重跑传播验证覆盖需就地更新的 ADR列出每个 ADR 需要更新的具体字段若大量 ADR 受影响Run/architecture-reviewafter all ADRs are updated to verify the full traceability matrix is still coherent.全部更新后跑架构审查验证完整可追溯矩阵仍然自洽。仓库佐证此处的先/architecture-decision再/architecture-review顺序与 architecture-decision SKILL 阶段 6 的固定提示一致——其要求在全新会话中运行/architecture-review以确保审查代理独立于撰写上下文避免作者偏见。此外/architecture-review的 Phase 2 会预加载 docs/architecture/tr-registry.yaml 以复用既有 TR-ID、防止跨轮次重编号这保证了后续传播分析引用的需求 ID 稳定。11. 协作协议协作规范该技能以五条协作纪律收尾它们与仓库整体Collaborative Design Principle一脉相承Read silently—— 先静默计算完整影响再呈现任何内容不边读边播报Show the full report first—— 先让用户看到影响全貌再询问行动对应阶段 6Ask per-ADR—— 逐个询问而非批量决策对应阶段 7Ask before writing—— 修改任何文件前必须先确认贯穿阶段 7/8/9 的多次 May I... 询问Non-destructive—— 绝不删除 ADR 内容只追加 Superseded by 注记。对比可见这套协议与 architecture-review SKILL 的协作协议Read silently / Show the matrix / Dont guess / Ask before writing / Non-blocking高度同构是仓库中审查型技能的通用行为模式。12. 在整体工作流中的位置与实战建议12.1 技能协同关系图/architecture-decision → 撰写 ADR含 GDD Requirements Addressed 表 ↓ /architecture-review → 全量审查建立可追溯矩阵 Superseded Requirements 索引 ↓ GDD 被修订 ↓ /propagate-design-change本文技能技术总监执行 ├─ 阶段 5逐 ADR 三态分类 ├─ 阶段 6bTD-CHANGE-IMPACT 导演门禁full 模式 ├─ 阶段 7逐 ADR 处置Superseded / 就地更新 / 保留 / 暂缓 ├─ 阶段 8追加 Superseded Requirements 条目 └─ 阶段 9-10落盘影响文档 建议重跑 /architecture-decision 与 /architecture-review【免费下载链接】Claude-Code-Game-StudiosTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.项目地址: https://gitcode.com/GitHub_Trending/cl/Claude-Code-Game-Studios创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考 GDD Requirements Addressed
GDD Requirements Addressed【免费下载链接】Claude-Code-Game-StudiosTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.项目地址: https://gitcode.com/GitHub_Trending/cl/Claude-Code-Game-StudiosGDD SystemRequirementHow This ADR Addresses It[system-name].md[specific rule, formula, or performance constraint from that GDD][how this decision satisfies it]--- ## 3. 阶段 1–3参数校验与变更识别 ### 3.1 校验参数阶段 1 GDD 路径参数是**必需**的缺参直接失败并提示 Usage: /propagate-design-change design/gdd/[system].md Provide the path to the GDD that was changed. 随后校验文件存在性不存在则报 [path] not found. Check the path and try again. ### 3.2 读取当前版本与历史版本阶段 2–3 先完整读取变更后的 GDD再通过 git 获取上一提交版本 bash git show HEAD:design/gdd/[filename].md这里存在两条重要分支新文件无历史报告 No previous version in git — this appears to be a new GDD, not a revision. Nothing to propagate.——新 GDD 没有旧假设可失效直接结束传播存在历史版本做概念性差异conceptual diff重点识别新增规则、删除规则、公式修改、验收标准变化、调优旋钮tuning knobs变化同时标记未变化章节。差异结果整理为变更摘要其模板为## Change Summary: [GDD filename] Date of revision: [today] Changed sections: - [Section name]: [what changed — new rule, removed rule, formula modified, etc.] Unchanged sections: - [Section name] Key changes affecting architecture: - [Change 1 — likely to affect ADRs] - [Change 2]仓库佐证这种旧版对当前版的比对逻辑与 docs/architecture/tr-registry.yaml 的修订纪律一脉相承——需求被改写意图不变时保留 ID 并加revised日期需求被删除时标记deprecated被拆分/替换时标记superseded-by。变更摘要中公式修改与调优旋钮变化正是最可能触发 TR-ID 状态变更的源头。4. 阶段 4加载架构输入读取docs/architecture/下全部 ADR对每个 ADR完整读取文件提取## GDD Requirements Addressed表格记录该 ADR 引用了哪些 GDD 文档及需求 ID。随后读取docs/architecture/architecture-traceability.md若存在并报告Loaded [N] ADRs. [M] reference [gdd filename].仓库佐证可追溯性索引的定位可在 architecture-review SKILL 第 8 阶段看到——该技能输出的索引文件包含 Coverage Summary、Full Matrix、Known Gaps 以及Superseded RequirementsRequirements whose GDD was changed after the ADR was written。换句话说architecture-review负责建索引propagate-design-change负责在 GDD 变更后让索引中过期条目被识别并处置。此外gate-check SKILL 的 Technical Setup → Pre-Production 门禁把architecture traceability index exists列为必需产物说明该索引是架构可追溯性的正式载体。5. 阶段 5影响分析核心方法论对每个引用了被变更 GDD 的 ADR逐条比对GDD Requirements Addressed条目与 GDD 的变更章节定位需求该需求在当前 GDD 中是否仍然存在对比ADR 撰写时 GDD 的说法 vs. 现在的说法评估该架构决策是否仍然成立。每个受影响 ADR 被归入三态之一状态含义✅Still ValidGDD 变更不影响该 ADR 的决策内容⚠️Needs ReviewGDD 变更可能影响该 ADR —— 需要人工判断Likely SupersededGDD 变更与该 ADR 的假设直接矛盾每个受影响 ADR 产出如下影响条目含引语级证据### ADR-NNNN: [title] Status: [Still Valid / Needs Review / Likely Superseded] What the ADR assumed about this GDD: [relevant quote from the ADRs GDD Requirements Addressed section] What the GDD now says: [relevant quote from the current GDD] Assessment: [Explanation of whether the ADR decision is still valid, and why] Recommended action: [Keep as-is | Review and update | Mark Superseded and write new ADR]仓库佐证三态分类的矛盾检测语义与 architecture-review SKILL 第 4 阶段的 Cross-ADR Conflict Detection 互补——后者检测ADR 之间的矛盾数据所有权冲突、接口契约冲突、性能预算冲突、依赖环、模式冲突、状态管理冲突而本技能检测ADR 与 GDD 之间随时间推移产生的失配。推荐动作中的 Mark Superseded and write new ADR 对应 architecture-decision SKILL 中的 ADR 状态枚举[Proposed | Accepted | Deprecated | Superseded by ADR-XXXX]。6. 阶段 6呈现影响报告关键纪律在询问任何行动之前先把完整影响报告呈现给用户。报告格式## Design Change Impact Report GDD: [filename] Date: [today] Changes detected: [N sections changed] ADRs referencing this GDD: [M] ### Not Affected [ADRs referencing this GDD whose decisions remain valid] ### Needs Review ([count]) [ADRs that may need updating] ### Likely Superseded ([count]) [ADRs whose assumptions are now contradicted]这一先展示全貌、再征求意见的协作模式在 .claude/docs/review-workflow.md 中有制度性背书Architecture changes require sign-off fromtechnical-director——架构变更的最终确认权在技术总监而技术总监代理的协作协议.claude/agents/technical-director.md明确你是最高层的顾问但所有最终战略决策由用户做出因此报告必须完整、可读、证据充分让用户能基于事实决策。7. 阶段 6b导演门禁 TD-CHANGE-IMPACT在派生子代理之前必须先做审查模式Review Mode检查。审查模式全局配置存放在production/review-mode.txt单行full、lean或solo由/start初始化可直接编辑文件修改每次技能运行时也可用--review [full|lean|solo]参数覆盖仅对当次运行生效详见 .claude/docs/director-gates.md。本技能的门禁检查逻辑solo→ 跳过记录 TD-CHANGE-IMPACT skipped — Solo mode.直接进入阶段 7lean→ 跳过记录 TD-CHANGE-IMPACT skipped — Lean mode.直接进入阶段 7full→ 正常派生。在full模式下通过Task以门禁TD-CHANGE-IMPACT定义于 .claude/docs/director-gates.md派生technical-director子代理传入阶段 6 的完整影响报告变更摘要、全部受影响 ADR 及其三态分类、推荐动作。技术总监审查三件事影响分类是否正确是否存在被低估分类的 ADR推荐动作在架构上是否成立是否遗漏了对其他 ADR 或系统的级联影响。裁决处理APPROVE→ 进入阶段 7 解决工作流CONCERNS→ 用AskUserQuestion呈现被标记的 ADR/建议选项为Revise the impact assessment/Accept with noted concerns/Discuss furtherREJECT→ 不得进入解决阶段需重新分析影响。仓库佐证门禁的裁决格式约定在 .claude/agents/technical-director.md 的## Gate Verdict Format节当通过导演门禁被调用时如TD-CHANGE-IMPACT响应第一行必须是独立的裁决 token[GATE-ID]: APPROVE/CONCERNS/REJECT调用方技能读取第一行获取裁决 token——本技能第 6b 阶段的应用裁决逻辑正是消费这一约定的标准流程。此外.claude/docs/director-gates.md 定义了三种模式的含义full全量门禁适合团队/学习型用户、lean仅 PHASE-GATE默认适合独立开发者、solo完全无门禁适合 Game Jam 与原型冲刺。8. 阶段 7解决工作流对每个标记为 Needs Review 或 Likely Superseded 的 ADR逐个征询用户意见不批量决策每个 ADR 可能有不同处置ADR-NNNN ([title]) — [status]. What would you like to do? Options:Mark Superseded (Ill write a new ADR) — updates ADR status line toSuperseded by: [pending]Update in place (minor revision) — opens the ADR for editing; note what to reviseKeep as-is (the change doesnt actually affect this decision)Skip for now (revisit later)对标记为Superseded的 ADR更新其 Status 字段为Superseded by ADR-[next number] (pending — see change-impact-[date]-[system].md)询问用户May I update the status in [ADR filename]?仓库佐证Superseded by ADR-[next number]的编号语义与 architecture-decision SKILL 阶段 2扫描docs/architecture/确定下一个 ADR 编号一致ADR 模板中## Status节.claude/docs/templates/architecture-decision-record.md的合法值即为[Proposed | Accepted | Deprecated | Superseded by ADR-XXXX]。同时注意非破坏性原则见第 10 节协作协议绝不删除 ADR 内容只追加 Superseded by 注记这与 TR 注册表ID 永久、绝不删除的哲学同源。9. 阶段 8更新可追溯性索引若docs/architecture/architecture-traceability.md存在将被变更的 GDD 需求追加到 Superseded Requirements 表## Superseded Requirements | Date | GDD | Requirement | Changed To | ADRs Affected | Resolution | |------|-----|-------------|------------|---------------|------------| | [date] | [gdd] | [old requirement text] | [new requirement text] | ADR-NNNN | [Superseded/Updated/Valid] |随后询问May I update the traceability index?仓库佐证该表与 architecture-review SKILL 阶段 8 中索引文件的## Superseded Requirements区块Requirements whose GDD was changed after the ADR was written完全对应——propagate-design-change负责向该表写入新条目而architecture-review负责在后续全量审查中消费这些条目其第 5b 阶段Design Revision Flags会把 GDD 中与已验证引擎行为/已接受 ADR 冲突的假设标记为待修订。两者一写一读构成可追溯性闭环。10. 阶段 9–10落盘变更影响文档与后续行动10.1 输出变更影响文档阶段 9询问May I write the change impact report todocs/architecture/change-impact-[date]-[system-slug].md?文档包含四部分内容阶段 3 的变更摘要阶段 5 的完整影响分析阶段 7 做出的解决决策需要新写或更新的 ADR 清单。裁决规则用户批准写入 → Verdict:COMPLETE— change impact report saved用户拒绝 → Verdict:BLOCKED— user declined write。10.2 后续行动建议阶段 10根据解决决策给出闭环建议被标记 Superseded 的 ADRRun/architecture-decision [title]to write the replacement ADR. Then re-run/propagate-design-changeto verify coverage.先写替代 ADR再重跑传播验证覆盖需就地更新的 ADR列出每个 ADR 需要更新的具体字段若大量 ADR 受影响Run/architecture-reviewafter all ADRs are updated to verify the full traceability matrix is still coherent.全部更新后跑架构审查验证完整可追溯矩阵仍然自洽。仓库佐证此处的先/architecture-decision再/architecture-review顺序与 architecture-decision SKILL 阶段 6 的固定提示一致——其要求在全新会话中运行/architecture-review以确保审查代理独立于撰写上下文避免作者偏见。此外/architecture-review的 Phase 2 会预加载 docs/architecture/tr-registry.yaml 以复用既有 TR-ID、防止跨轮次重编号这保证了后续传播分析引用的需求 ID 稳定。11. 协作协议协作规范该技能以五条协作纪律收尾它们与仓库整体Collaborative Design Principle一脉相承Read silently—— 先静默计算完整影响再呈现任何内容不边读边播报Show the full report first—— 先让用户看到影响全貌再询问行动对应阶段 6Ask per-ADR—— 逐个询问而非批量决策对应阶段 7Ask before writing—— 修改任何文件前必须先确认贯穿阶段 7/8/9 的多次 May I... 询问Non-destructive—— 绝不删除 ADR 内容只追加 Superseded by 注记。对比可见这套协议与 architecture-review SKILL 的协作协议Read silently / Show the matrix / Dont guess / Ask before writing / Non-blocking高度同构是仓库中审查型技能的通用行为模式。12. 在整体工作流中的位置与实战建议12.1 技能协同关系图/architecture-decision → 撰写 ADR含 GDD Requirements Addressed 表 ↓ /architecture-review → 全量审查建立可追溯矩阵 Superseded Requirements 索引 ↓ GDD 被修订 ↓ /propagate-design-change本文技能技术总监执行 ├─ 阶段 5逐 ADR 三态分类 ├─ 阶段 6bTD-CHANGE-IMPACT 导演门禁full 模式 ├─ 阶段 7逐 ADR 处置Superseded / 就地更新 / 保留 / 暂缓 ├─ 阶段 8追加 Superseded Requirements 条目 └─ 阶段 9-10落盘影响文档 建议重跑 /architecture-decision 与 /architecture-review【免费下载链接】Claude-Code-Game-StudiosTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.项目地址: https://gitcode.com/GitHub_Trending/cl/Claude-Code-Game-Studios创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考