research

# research workflow Multi-source research workflow shipped with harnessed v2.0 (Stage ① Discuss); `workflow.yaml` schema bumped to `harnessed.workflow.v3` in Phase v3.0-3.4 W1.1 (T3.4.W1.1 — D-09 L0 Discipline Substrate + D-05 tools_available cross-validate); phases content (01-fan-out + 02-synth) verbatim reused from v2 SHIPPED unchanged. ## Phases (2) | # | Phase | Upstream | Capability | Model | Description | |---|-------|----------|-----------|-------|-------------| | 01 | `01-fan-out` | web-search | (route-by-subtask) | sonnet | 3 source fan-out (Tavily MCP / Exa MCP / ctx7 CLI per bundled web-search + context7 routing) | | 02 | `02-synth` | gsd | `gsd-discuss-phase` | opus | GSD discuss-phase aggregate + dedup + reconcile | ## Capability refs Sister `workflows/capabilities.yaml` entries: - `tavily-mcp` (impl: mcp-server, default 关键词) - `exa-mcp` (impl: mcp-server, 描述式 / 学术) - `ctx7` (impl: cli-tool, 库 API 文档) - `gsd-discuss-phase` (synth aggregate) ## Invocation - Slash command: `/research <topic>` (after `harnessed setup`) ## Routing rules (bundled web-search routing — `workflows/judgments/web-search-routing.yaml`) - 描述式查询 ("找一篇对比 X 和 Y 的博客") → Exa MCP - 学术 / 论文 → Exa MCP - 库 / API 文档 → ctx7 CLI - 关键词 / 时效内容 → Tavily MCP (默认) - 抓整站 / 站点结构 → Tavily crawl/map ## How to invoke !`harnessed checkpoint intent research` > The banner above (when present) means this invocation is REGISTERED with the engine (an intent marker) — not yet compliant: the steps below (promp...