gsd-docs-update

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

<objective> Generate and update up to 9 documentation files for the current project. Each doc type is written by a gsd-doc-writer subagent that explores the codebase directly — no hallucinated paths, phantom endpoints, or stale signatures.

Flag handling rule:

The optional flags documented below are available behaviors, not implied active behaviors
A flag is active only when its literal token appears in
```
$ARGUMENTS
```
If a documented flag is absent from
```
$ARGUMENTS
```
, treat it as inactive
```
--force
```
: skip preservation prompts, regenerate all docs regardless of existing content or GSD markers
```
--verify-only
```
: check existing docs for accuracy against codebase, no generation (full verification requires Phase 4 verifier)
If
```
--force
```
and
```
--verify-only
```
both appear in
```
$ARGUMENTS
```
,
```
--force
```
takes precedence </objective>

<execution_context> @~/.claude/gsd-core/workflows/docs-update.md </execution_context>

<context> Arguments: $ARGUMENTS

Available optional flags (documentation only — not automatically active):

```
--force
```
— Regenerate all docs. Overwrites hand-written and GSD docs alike. No preservation prompts.
```
--verify-only
```
— Check existing docs for accuracy against the codebase. No files are written. Reports VERIFY marker count. Full codebase fact-checking requires the gsd-doc-verifier agent (Phase 4).

Active flags must be derived from
$ARGUMENTS
:

```
--force
```
is active only if the literal
```
--force
```
token is present in
```
$ARGUMENTS
```
```
--verify-only
```
is active only if the literal
```
--verify-only
```
token is present in
```
$ARGUMENTS
```
If neither token appears, run the standard full-phase generation flow
Do not infer that a flag is active just because it is documented in this prompt </context>

<process> Execute end-to-end. Preserve all workflow gates (preservation_check, flag handling, wave execution, monorepo dispatch, commit, reporting). </process>

<objective> 为当前项目生成并更新最多9份文档文件。每种文档类型由gsd-doc-writer子代理编写，该代理会直接探索代码库——不会出现虚构路径、虚假端点或过时签名。

标志处理规则:

下文记录的可选标志是可用行为，并非默认激活的行为
只有当
```
$ARGUMENTS
```
中包含标志的字面令牌时，该标志才处于激活状态
如果
```
$ARGUMENTS
```
中缺少某一已记录的标志，则视为未激活
```
--force
```
: 跳过保留提示，无论现有内容或GSD标记如何，重新生成所有文档
```
--verify-only
```
: 检查现有文档与代码库的一致性，不进行生成（完整校验需要Phase 4验证器）
如果
```
$ARGUMENTS
```
中同时包含
```
--force
```
和
```
--verify-only
```
，则
```
--force
```
优先 </objective>

<execution_context> @~/.claude/gsd-core/workflows/docs-update.md </execution_context>

<context> 参数: $ARGUMENTS

可用可选标志（仅作文档记录——不会自动激活）:

```
--force
```
— 重新生成所有文档。覆盖手写文档和GSD文档。无保留提示。
```
--verify-only
```
— 检查现有文档与代码库的一致性。不写入任何文件。报告VERIFY标记数量。完整的代码库事实校验需要gsd-doc-verifier代理（Phase 4）。

激活标志必须从
$ARGUMENTS
中推导:

```
--force
```
处于激活状态当且仅当
```
$ARGUMENTS
```
中存在字面令牌
```
--force
```
```
--verify-only
```
处于激活状态当且仅当
```
$ARGUMENTS
```
中存在字面令牌
```
--verify-only
```
如果两个令牌都不存在，则运行标准的全阶段生成流程
请勿仅因本提示中记录了某一标志就推断该标志处于激活状态 </context>

<process> 端到端执行。保留所有工作流关卡（preservation_check、标志处理、批次执行、单体仓库调度、提交、报告）。 </process>