Back to Details

discover

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Discovery Workflow Skill

Discovery Workflow 技能

A workflow type for tasks whose deliverable is a document, not code. It carries no verification gates (nothing to test), so the verification ladder does not apply.
一种面向交付物为文档而非代码的任务的工作流类型。它没有验证关卡（无需测试），因此验证阶梯不适用。

When to Use

适用场景

  • Competitive analyses and market research
  • Architecture comparisons and ADR scaffolding
  • Literature reviews and vendor evaluations
  • Design research that does NOT feed into implementation planning
  • 竞品分析与市场研究
  • 架构对比与ADR框架搭建
  • 文献综述与供应商评估
  • 不用于实施规划的设计研究

When NOT to Use

不适用场景

  • If the deliverable includes code changes → use 
    /exarchos:oneshot
    or 
    /exarchos:ideate
  • If you need TDD enforcement → use any other workflow type
  • If the research feeds directly into implementation → use 
    /exarchos:ideate
    (which authors the Design & Rationale section of the unified 
    docs/specs/
    artifact)
  • 若交付物包含代码变更 → 使用
    /exarchos:oneshot
    或
    /exarchos:ideate
  • 若需要强制执行TDD → 使用其他任意工作流类型
  • 若研究成果直接用于实施 → 使用
    /exarchos:ideate
    （该工作流负责撰写统一
    docs/specs/
    工件中的“设计与原理”章节）

Discover bridge (the deep-rung escalation)

发现桥（深度层级升级）

At the 
deep
planning rung, 
/exarchos:ideate
can escalate to this workflow as a first-class, event-linked research pre-pass instead of a manual "go start a new workflow" handoff. The bridge is opt-in (author-confirmed, never auto-run): the affordance is surfaced on 
next_actions
, and the 
discover_bridge
orchestrate action — invoked with 
confirm: true
— stitches this discovery run to the originating spec by a deterministic 
correlationId
(recorded as a 
state.patched
link event on the feature stream). When you run a discovery escalated this way, cite the report path in the spec's 
## Design & Rationale
→ Exploration section, and 
init
this workflow with the bridge's 
correlationId
so provenance spans both documents.
在
deep
规划层级，
/exarchos:ideate
可以升级为该工作流，作为一等的、事件关联的研究前置环节，而非手动“启动新工作流”的交接方式。该桥接为可选启用（需作者确认，绝不会自动运行）：相关功能会在
next_actions
中显示，调用
discover_bridge
编排操作时传入
confirm: true
，会通过确定性的
correlationId
将本次发现运行与源规范关联（记录为功能流上的
state.patched
链接事件）。当你通过这种方式升级运行发现工作流时，需在规范的
## 设计与原理
→探索章节中引用报告路径，并使用桥接的
correlationId
来
init
该工作流，从而确保两个文档的溯源关系。

Phases

阶段

Phase 1: Gathering (initial)

阶段1：收集（初始阶段）

Collect sources, references, and raw material for the deliverable.
  1. Define the research question or deliverable scope
  2. Identify and collect sources (URLs, documents, code references)
  3. Record sources in workflow state:
typescript
exarchos:exarchos_workflow({
  action: "update", featureId: "<id>",
  updates: { "artifacts.sources": ["<source1>", "<source2>", "..."] }
})
  1. Create an outline of the deliverable
Transition: When 
artifacts.sources
is a non-empty array → 
synthesizing
为交付物收集来源、参考资料和原始素材。
  1. 定义研究问题或交付物范围
  2. 识别并收集来源（URL、文档、代码参考）
  3. 在工作流状态中记录来源：
typescript
exarchos:exarchos_workflow({
  action: "update", featureId: "<id>",
  updates: { "artifacts.sources": ["<source1>", "<source2>", "..."] }
})
  1. 创建交付物的大纲
阶段转换： 当
artifacts.sources
为非空数组时 → 进入
synthesizing
（合成）阶段

Phase 2: Synthesizing

阶段2：合成

Draft the deliverable document from gathered sources.
  1. Write the document based on gathered sources and outline
  2. Commit the document to the repo (typically under 
    docs/research/
    or 
    docs/designs/
    )
  3. Record the report path:
typescript
exarchos:exarchos_workflow({
  action: "update", featureId: "<id>",
  updates: { "artifacts.report": "<path-to-document>" }
})
Transition: When 
artifacts.report
is set → 
completed
根据收集到的来源起草交付物文档。
  1. 根据收集到的来源和大纲撰写文档
  2. 将文档提交到代码仓库（通常放在
    docs/research/
    或
    docs/designs/
    目录下）
  3. 记录报告路径：
typescript
exarchos:exarchos_workflow({
  action: "update", featureId: "<id>",
  updates: { "artifacts.report": "<path-to-document>" }
})
阶段转换： 当
artifacts.report
已设置时 → 进入
completed
（完成）阶段

Optional: Escalation to Implementation

可选：升级至实施阶段

If discovery surfaces an implementation need:
  1. Note the finding in the report
  2. After completing the discovery workflow, start a new workflow:
    bash
    ideate <implementation-topic>
    Reference the discovery report as design input.
若发现工作流揭示了实施需求：
  1. 在报告中记录该发现
  2. 完成发现工作流后，启动新工作流：
    bash
    ideate <implementation-topic>
    将发现报告作为设计输入进行引用。

Event Emissions

事件发射

Optionally emit events at key moments for observability:
typescript
exarchos:exarchos_event({
  action: "append", stream: "<featureId>",
  event: { type: "discovery.sources_collected", data: { sourceCount: N } }
})
typescript
exarchos:exarchos_event({
  action: "append", stream: "<featureId>",
  event: { type: "discovery.report_committed", data: { path: "<report-path>" } }
})
可在关键节点发射事件以实现可观测性：
typescript
exarchos:exarchos_event({
  action: "append", stream: "<featureId>",
  event: { type: "discovery.sources_collected", data: { sourceCount: N } }
})
typescript
exarchos:exarchos_event({
  action: "append", stream: "<featureId>",
  event: { type: "discovery.report_committed", data: { path: "<report-path>" } }
})