尧图网站建设 ![[Game Name] — Master Architecture](http://pic.xiahunao.cn/yaotu/[Game Name] — Master Architecture)
[Game Name] — Master Architecture【免费下载链接】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-StudiosDocument StatusVersion: [N]Last Updated: [date]Engine: [name version]GDDs Covered: [list]ADRs Referenced: [list]Engine Knowledge Gap Summary[Condensed from Phase 0d inventory — HIGH/MEDIUM risk domains and their implications]System Layer Map[From Phase 1]Module Ownership[From Phase 2]Data Flow[From Phase 3]API Boundaries[From Phase 4]ADR Audit[From Phase 5]Required ADRs[From Phase 6]Architecture Principles[3-5 key principles that govern all technical decisions for this project, derived from the game concept, GDDs, and technical preferences]Open Questions[Decisions deferred — must be resolved before the relevant layer is built]注意 Architecture Principles 和 Open Questions 两个章节——前者把游戏概念、GDD 和技术偏好提炼成约束所有技术决策的 3-5 条原则后者显式记录被推迟的决策及必须在该层构建前解决的时间点。被推迟≠被遗忘这正是专业架构文档的成熟标志。 ## 十二、Phase 7b技术总监签署 主程序员可行性审查 写完主文档后在交接前执行显式签署流程。 **Step 1 — 技术总监自审**以门禁 **TD-ARCHITECTURE**定义在 [.claude/docs/director-gates.md](https://link.gitcode.com/i/5f839117a958a8a8885630c3b9e59560)对完成的文档做自审检查该门禁定义的四条标准每条技术需求是否都有架构决策覆盖、所有 HIGH 风险引擎域是否被显式处理或标记为开放问题、API 边界是否干净最小可实现、Foundation 层 ADR 缺口是否在实现开始前解决。 **Review 模式检查**——spawn LP-FEASIBILITY 前先应用 - solo → 跳过记录 LP-FEASIBILITY skipped — Solo mode.直接进入 Phase 8 交接 - lean → 跳过非 PHASE-GATE记录 LP-FEASIBILITY skipped — Lean mode.进入 Phase 8 - full → 正常 spawn **Step 2 — 通过 Task spawn lead-programmer**使用门禁 **LP-FEASIBILITY**。传入架构文档路径、技术需求基线摘要、ADR 清单。该门禁的审查重点是实现可行性——是否有难以用指定引擎和语言实现的决策、是否有程序员需要自己发明的缺失接口定义、是否有制造不必要技术债或违背引擎惯用法的模式。 **Step 3 — 并排呈现两份评估**向用户展示技术总监评估与主程序员结论的对比。 **Step 4 — 记录签署**在架构文档的 Document Status 章节写入Technical Director Sign-Off: [date] — APPROVED / APPROVED WITH CONDITIONSLead Programmer Feasibility: FEASIBLE / CONCERNS ACCEPTED / REVISED【免费下载链接】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），仅供参考 [Game Name] — Master Architecture
[Game Name] — Master Architecture【免费下载链接】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-StudiosDocument StatusVersion: [N]Last Updated: [date]Engine: [name version]GDDs Covered: [list]ADRs Referenced: [list]Engine Knowledge Gap Summary[Condensed from Phase 0d inventory — HIGH/MEDIUM risk domains and their implications]System Layer Map[From Phase 1]Module Ownership[From Phase 2]Data Flow[From Phase 3]API Boundaries[From Phase 4]ADR Audit[From Phase 5]Required ADRs[From Phase 6]Architecture Principles[3-5 key principles that govern all technical decisions for this project, derived from the game concept, GDDs, and technical preferences]Open Questions[Decisions deferred — must be resolved before the relevant layer is built]注意 Architecture Principles 和 Open Questions 两个章节——前者把游戏概念、GDD 和技术偏好提炼成约束所有技术决策的 3-5 条原则后者显式记录被推迟的决策及必须在该层构建前解决的时间点。被推迟≠被遗忘这正是专业架构文档的成熟标志。 ## 十二、Phase 7b技术总监签署 主程序员可行性审查 写完主文档后在交接前执行显式签署流程。 **Step 1 — 技术总监自审**以门禁 **TD-ARCHITECTURE**定义在 [.claude/docs/director-gates.md](https://link.gitcode.com/i/5f839117a958a8a8885630c3b9e59560)对完成的文档做自审检查该门禁定义的四条标准每条技术需求是否都有架构决策覆盖、所有 HIGH 风险引擎域是否被显式处理或标记为开放问题、API 边界是否干净最小可实现、Foundation 层 ADR 缺口是否在实现开始前解决。 **Review 模式检查**——spawn LP-FEASIBILITY 前先应用 - solo → 跳过记录 LP-FEASIBILITY skipped — Solo mode.直接进入 Phase 8 交接 - lean → 跳过非 PHASE-GATE记录 LP-FEASIBILITY skipped — Lean mode.进入 Phase 8 - full → 正常 spawn **Step 2 — 通过 Task spawn lead-programmer**使用门禁 **LP-FEASIBILITY**。传入架构文档路径、技术需求基线摘要、ADR 清单。该门禁的审查重点是实现可行性——是否有难以用指定引擎和语言实现的决策、是否有程序员需要自己发明的缺失接口定义、是否有制造不必要技术债或违背引擎惯用法的模式。 **Step 3 — 并排呈现两份评估**向用户展示技术总监评估与主程序员结论的对比。 **Step 4 — 记录签署**在架构文档的 Document Status 章节写入Technical Director Sign-Off: [date] — APPROVED / APPROVED WITH CONDITIONSLead Programmer Feasibility: FEASIBLE / CONCERNS ACCEPTED / REVISED【免费下载链接】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），仅供参考