Back to Details

gsd-ingest-docs

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<objective> Build the full `.planning/` setup (or merge into an existing one) from multiple pre-existing planning documents — ADRs, PRDs, SPECs, DOCs — in one pass.
  • Net-new bootstrap (
    --mode new
    , default when 
    .planning/
    is absent): produces PROJECT.md + REQUIREMENTS.md + ROADMAP.md + STATE.md from synthesized doc content, delegating final generation to 
    gsd-roadmapper
    .
  • Merge into existing (
    --mode merge
    , default when 
    .planning/
    is present): appends phases and requirements derived from the ingested docs; hard-blocks any contradiction with existing locked decisions.
Auto-synthesizes most conflicts using the precedence rule 
ADR > SPEC > PRD > DOC
(overridable via manifest). Surfaces unresolved cases in 
.planning/INGEST-CONFLICTS.md
with three buckets: auto-resolved, competing-variants, unresolved-blockers. The BLOCKER gate from the shared conflict engine prevents any destination file from being written when unresolved contradictions exist.
Inputs: directory-convention discovery (
docs/adr/
, 
docs/prd/
, 
docs/specs/
, 
docs/rfc/
, root-level 
{ADR,PRD,SPEC,RFC}-*.md
), or an explicit 
--manifest <file>
YAML listing 
{path, type, precedence?}
per doc.
v1 constraints: hard cap of 50 docs per invocation; 
--resolve interactive
is reserved for a future release. </objective>
<execution_context> @/.claude/gsd-core/workflows/ingest-docs.md @/.claude/gsd-core/references/ui-brand.md @/.claude/gsd-core/references/gate-prompts.md @/.claude/gsd-core/references/doc-conflict-engine.md </execution_context>
<context> $ARGUMENTS </context> <process> Execute the ingest-docs workflow end-to-end. Preserve all approval gates (discovery, conflict report, routing) and the BLOCKER safety rule. </process>
<objective> 一次性从多种预先存在的规划文档（ADR、PRD、SPEC、DOC）中构建完整的.planning/配置（或合并至现有配置）。
  • 全新初始化（
    --mode new
    ，当.planning/不存在时为默认模式）：从合成的文档内容生成PROJECT.md + REQUIREMENTS.md + ROADMAP.md + STATE.md，最终生成任务委托给
    gsd-roadmapper
    。
  • 合并至现有配置（
    --mode merge
    ，当.planning/已存在时为默认模式）：追加从导入文档中提取的阶段和需求；若与已锁定的现有决策存在矛盾，则强制阻止操作。
系统会自动根据优先级规则
ADR > SPEC > PRD > DOC
（可通过清单覆盖）解决大多数冲突。未解决的情况会被归类到.planning/INGEST-CONFLICTS.md中，分为三个类别：自动解决、竞争变体、未解决阻塞项。共享冲突引擎中的BLOCKER机制会在存在未解决矛盾时，阻止任何目标文件的写入。
输入： 按目录约定自动发现（
docs/adr/
、
docs/prd/
、
docs/specs/
、
docs/rfc/
，根目录下的
{ADR,PRD,SPEC,RFC}-*.md
文件），或通过显式的
--manifest <file>
YAML文件列出每个文档的
{path, type, precedence?}
信息。
v1版本限制： 每次调用最多处理50份文档；
--resolve interactive
模式预留至未来版本发布。 </objective>
<execution_context> @/.claude/gsd-core/workflows/ingest-docs.md @/.claude/gsd-core/references/ui-brand.md @/.claude/gsd-core/references/gate-prompts.md @/.claude/gsd-core/references/doc-conflict-engine.md </execution_context>
<context> $ARGUMENTS </context> <process> 完整执行ingest-docs工作流。保留所有审批环节（发现、冲突报告、路由）及BLOCKER安全规则。 </process>