Files
msd-core/docs/zh-CN
Tom Boucher 4483300253 fix(#2072): thread resolved model into routed-agent spawns (assumptions-analyzer, code-reviewer, code-fixer)
model_overrides / models.<phaseType> were silently inert for gsd-assumptions-analyzer,
gsd-code-reviewer, and gsd-code-fixer on Claude Code: resolveModelInternal honors them,
but the workflows spawned these agents with no model= param, so the resolved value
never reached the Agent tool and the agents inherited the session model — no warning.

Fix — thread each agent's resolved model at every spawn site (the established
plan-phase pattern; the architecture-consistent Claude mechanism, since 13 other
agents already thread their model):
- discuss-phase-assumptions.md: `resolve-model gsd-assumptions-analyzer --raw`
  → ANALYZER_MODEL, threaded.
- code-review.md + code-review-fix.md (re-review): `resolve-model gsd-code-reviewer --raw`
  → REVIEWER_MODEL, threaded.
- code-review-fix.md (both fixer spawns): `resolve-model gsd-code-fixer --raw`
  → FIXER_MODEL, threaded (same silently-inert bug, same file — folded in per review).
- quick.md review step: was reusing `{executor_model}` for gsd-code-reviewer (so the
  reviewer's own override was ignored); init.quick now resolves `reviewer_model`
  (gsd-code-reviewer) and the spawn threads it.

resolve-model --raw returns the bare model string (resolve-execution --raw would
return effort — wrong). The resolver maps these agents to phaseType discuss /
verification / execution, so models.<phaseType> apply too.

Scope: the three agents reachable from the two issue-named workflows + quick.md. The
wider systemic class (other agents in UNTOUCHED workflows with the same pattern) stays
documented on the issue for a maintainer-scoped structural decision (thread-at-source
vs embed-at-install like #2256), not widened here.

Docs: the stale "discuss — reserved, no subagent today" model-profile tables now list
gsd-assumptions-analyzer and the verification row includes gsd-code-reviewer, across
the English docs, the shipped gsd-core/references/model-profiles.md reference, and the
ja-JP / zh-CN / ko-KR / pt-BR locale mirrors.

Tests:
- tests/model-resolver.test.cjs: #2072 acceptance — model_overrides and
  models.discuss/verification/execution resolve for all three agents.
- tests/model-routing-spawn-threading.test.cjs: every spawn of the three agents threads
  a resolved model (fails pre-fix); a header-precise parity guard fails the suite if a
  new un-threaded spawn of any of them regresses.
All 16 golden-install-parity fixtures + the workflow size baseline regenerated for the
changed shipped files (4 workflows + the reference doc); bin/lib is excluded from parity.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-07 21:22:48 -04:00
..

GSD Core 文档

文档按四个象限组织:教程通过实践帮助你学习,操作指南解决具体任务,参考文档提供权威信息,概念说明探讨设计理念与决策。

语言版本:English · Português (pt-BR) · 日本語 · 简体中文


Tutorials


How-to guides


Reference

  • 命令 — 每个命令的标志和示例
  • 配置 — 完整配置模式、模型配置文件、Git 分支策略
  • CLI 工具 — gsd-tools.cjs 用于工作流和代理的编程式 API
  • 功能特性 — 完整功能索引
  • 清单 — 已安装的技能与界面映射
  • STATE.md 模式 — .planning/STATE.md 的逐字段参考
  • CONTEXT.md 模式 — .planning/phases/<N>/CONTEXT.md 的逐字段参考
  • PLAN.md 模式 — .planning/phases/<N>/PLAN.md 的逐字段参考
  • 规划产物 — 所有 .planning/ 文件及其作用

Explanation

  • 上下文工程 — 上下文腐化如何形成,以及 GSD Core 如何防止它
  • 阶段循环 — 讨论 → 规划 → 执行 → 验证 → 交付循环的设计原理
  • 多代理编排 — 子代理的生成、范围界定和协调方式
  • 安全模型 — 信任边界、权限和安全自动化
  • 架构 — 系统架构、代理模型和数据流
  • 讨论模式 — /gsd-discuss-phase 的假设模式与访谈模式
  • 上下文监控 — 上下文窗口监控钩子架构
  • Issue 驱动编排 — 使用现有原语从追踪器 issue 驱动 GSD 的方案