research-web

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
User request: $ARGUMENTS
Comprehensive multi-wave web research. Strategically selects sources, evaluates credibility, cross-references findings, and synthesizes actionable recommendations.
Research log:
/tmp/research-web-{YYYYMMDD-HHMMSS}-{topic-kebab-case}.md
- external memory for all findings.
用户请求: $ARGUMENTS
多阶段综合性网页研究。策略性选择来源、评估可信度、交叉验证研究结果并整合可落地的建议。
研究日志:
/tmp/research-web-{YYYYMMDD-HHMMSS}-{topic-kebab-case}.md
- 存储所有研究结果的外部记忆文件。

Phase 1: Research Planning

第一阶段:研究规划

1.1 Parse Request

1.1 解析请求

Extract from
$ARGUMENTS
:
  • Primary question: What are we trying to learn?
  • Context: Why do we need this? What decision does it inform?
  • Constraints: Version requirements, platform limitations, etc.
If vague or empty: Ask user to clarify the specific question.
$ARGUMENTS
中提取:
  • 核心问题: 我们需要了解什么?
  • 背景: 为什么需要这些信息?将为哪些决策提供依据?
  • 约束条件: 版本要求、平台限制等。
若请求模糊或为空: 请用户明确具体问题。

1.2 Create Research Log

1.2 创建研究日志

Path:
/tmp/research-web-{YYYYMMDD-HHMMSS}-{topic-kebab-case}.md
markdown
undefined
路径:
/tmp/research-web-{YYYYMMDD-HHMMSS}-{topic-kebab-case}.md
markdown
undefined

Web Research: {topic}

网页研究: {topic}

Started: {timestamp}
开始时间: {timestamp}

Research Question

研究问题

{Primary question}
{核心问题}

Context

背景

{Why needed, what decision it informs}
{需求原因及决策依据}

Initial Hypotheses

初始假设

(populated in 1.3)
(在1.3部分填充)

Wave Results

各阶段研究结果

(populated during research)
(研究过程中填充)

Source Registry

来源登记

(populated during research)
(研究过程中填充)

Conflicts

冲突记录

(populated when sources disagree)
(出现来源分歧时填充)

Synthesis

结果整合

(populated in Phase 4)
undefined
(在第四阶段填充)
undefined

1.3 Form Initial Hypotheses

1.3 提出初始假设

Before searching, document what you expect to find:
markdown
undefined
在搜索前,记录预期发现:
markdown
undefined

Initial Hypotheses

初始假设

H1: {Expected answer}

H1: {预期结论}

  • Confidence: Low | Medium | High
  • Would falsify: {what would prove this wrong}
  • 置信度: 低 | 中 | 高
  • 证伪条件: {可证明该假设错误的情况}

H2: {Alternative possibility}

H2: {其他可能性}

  • Confidence: Low | Medium | High
  • Would falsify: {what would prove this wrong}

**Why hypotheses first**: Prevents confirmation bias. Search for evidence both supporting AND refuting.
  • 置信度: 低 | 中 | 高
  • 证伪条件: {可证明该假设错误的情况}

**先提出假设的原因**: 避免确认偏差。搜索时同时寻找支持和反驳假设的证据。

1.4 Create Todo List

1.4 创建待办清单

- [ ] Wave 1: Official documentation
- [ ] Wave 2: Community resources
- [ ] Wave 3: Advanced/specialized sources
- [ ] Cross-reference and resolve conflicts
- [ ] Synthesize findings
- [ ] 第一阶段:官方文档
- [ ] 第二阶段:社区资源
- [ ] 第三阶段:专业进阶来源
- [ ] 交叉验证并解决冲突
- [ ] 整合研究结果

Phase 2: Strategic Wave Research

第二阶段:分阶段策略研究

Wave Selection Strategy

阶段选择策略

WaveSource TypePurposeWhen to Use
1Official docs, GitHub reposCanonical behavior, API specsAlways start here
2Stack Overflow, tutorials, blogsPractical examples, common issuesAfter official gaps identified
3Academic papers, expert blogs, niche forumsEdge cases, advanced techniquesWhen waves 1-2 insufficient
阶段来源类型目的使用场景
1官方文档、GitHub仓库标准行为、API规范始终从这里开始
2Stack Overflow、教程、技术博客实践案例、常见问题在官方文档存在信息缺口时使用
3学术论文、专家博客、小众论坛边缘案例、进阶技术当前两个阶段信息不足时使用

2.1 Wave 1: Official Sources

2.1 第一阶段:官方来源

Priority sources:
  1. Official documentation sites
  2. GitHub repositories (README, docs/, wiki)
  3. Official API references
  4. Release notes and changelogs
Search queries:
  • {topic} official documentation
  • {topic} github
  • {technology} {feature} docs
Document each source:
markdown
undefined
优先来源:
  1. 官方文档站点
  2. GitHub仓库(README、docs/目录、wiki)
  3. 官方API参考文档
  4. 发布说明和更新日志
搜索关键词:
  • {topic} official documentation
  • {topic} github
  • {technology} {feature} docs
记录每个来源:
markdown
undefined

Source: {title}

来源: {标题}

URL: {url} Type: Official Documentation | GitHub | API Reference Date: {publication/update date} Credibility: High (official)
Key findings:
  • {Finding 1}
  • {Finding 2}
Evidence:
"{Relevant quote}"
Supports/Refutes: H1, H2
undefined
URL: {url} 类型: 官方文档 | GitHub | API参考 日期: {发布/更新日期} 可信度: 高(官方)
关键发现:
  • {发现1}
  • {发现2}
证据:
"{相关引用内容}"
支持/反驳: H1, H2
undefined

2.2 Wave 2: Community Resources

2.2 第二阶段:社区资源

Priority sources:
  1. Stack Overflow (recent, accepted answers)
  2. Technical blogs (reputable authors)
  3. Tutorial sites
  4. Discussion forums
Search queries:
  • {topic} example
  • {topic} tutorial
  • {topic} best practices
  • {technology} {error message}
    (if troubleshooting)
Credibility indicators:
  • High: Accepted answer, author is maintainer/contributor, multiple upvotes
  • Medium: Popular answer, detailed explanation, includes code
  • Low: Old answer, no engagement, no sources
优先来源:
  1. Stack Overflow(近期、已采纳的回答)
  2. 技术博客(知名作者)
  3. 教程站点
  4. 讨论论坛
搜索关键词:
  • {topic} example
  • {topic} tutorial
  • {topic} best practices
  • {technology} {error message}
    (用于故障排查时)
可信度指标:
  • 高:已采纳回答、作者是维护者/贡献者、多个点赞
  • 中:热门回答、详细解释、包含代码
  • 低:老旧回答、无互动、无引用来源

2.3 Wave 3: Advanced Sources

2.3 第三阶段:专业进阶来源

Only proceed if waves 1-2 leave gaps.
Sources:
  • Academic papers (for algorithms, protocols)
  • Expert technical blogs
  • Conference talks
  • Specialized forums/communities
  • Source code analysis
Search queries:
  • {topic} paper
  • {topic} deep dive
  • {topic} internals
仅当前两个阶段无法填补信息缺口时使用。
来源:
  • 学术论文(用于算法、协议研究)
  • 专家技术博客
  • 会议演讲资料
  • 专业论坛/社区
  • 源代码分析
搜索关键词:
  • {topic} paper
  • {topic} deep dive
  • {topic} internals

Phase 3: Research Loop

第三阶段:研究循环

Memento Loop

记忆循环

For each wave:
  1. Mark wave todo
    in_progress
  2. Execute searches
  3. Evaluate and document each source
  4. Write findings immediately to research log
  5. Update hypothesis status
  6. Mark wave todo
    completed
  7. Decide: proceed to next wave or sufficient?
NEVER proceed without writing findings — research log is external memory.
每个阶段执行以下步骤:
  1. 将待办事项标记为
    in_progress
  2. 执行搜索
  3. 评估并记录每个来源
  4. 立即将发现写入研究日志
  5. 更新假设状态
  6. 将待办事项标记为
    completed
  7. 决策:进入下一阶段或停止研究
绝对不要跳过记录发现的步骤 — 研究日志是外部记忆载体。

3.1 Source Credibility Evaluation

3.1 来源可信度评估

For each source, assess:
FactorHighMediumLow
AuthorityOfficial, maintainerExpert, educatorAnonymous, unknown
Recency<6 months<2 years>2 years
VerificationMultiple sources agreeSome corroborationSingle source
DepthShows understandingPractical focusSurface level
对每个来源,从以下维度评估:
评估项
权威性官方、维护者专家、教育者匿名、未知作者
时效性<6个月<2年>2年
验证性多个来源一致部分来源佐证单一来源
深度体现底层理解侧重实践表面信息

3.2 Update Hypotheses

3.2 更新假设

As findings come in:
markdown
undefined
随着研究推进,更新假设状态:
markdown
undefined

H1: {hypothesis}

H1: {假设内容}

  • Status: CONFIRMED | REFUTED | UNCERTAIN
  • Confidence: Low | Medium | High
  • Evidence: {summary}
  • Sources: {list}
undefined
  • 状态: 已确认 | 已证伪 | 不确定
  • 置信度: 低 | 中 | 高
  • 证据: {摘要}
  • 来源: {列表}
undefined

3.3 Handle Conflicts

3.3 处理信息冲突

When sources disagree:
markdown
undefined
当来源信息出现分歧时:
markdown
undefined

Conflicts

冲突记录

{Topic of disagreement}

{分歧主题}

Position A: {claim}
  • Sources: {list}
  • Strength: {why credible}
Position B: {claim}
  • Sources: {list}
  • Strength: {why credible}
Resolution:
  • {Your assessment based on source authority, recency, consensus}
  • OR "Unresolved - present both options to user"

**Conflict resolution priority**:
1. Official docs > community
2. Recent > old
3. Multiple sources > single source
4. Code/specs > opinions
观点A: {主张内容}
  • 来源: {列表}
  • 可信度: {可信原因}
观点B: {主张内容}
  • 来源: {列表}
  • 可信度: {可信原因}
解决结果:
  • {基于来源权威性、时效性、共识性的评估}
  • 或“未解决 - 向用户呈现两种观点”

**冲突解决优先级**:
1. 官方文档 > 社区资源
2. 近期内容 > 老旧内容
3. 多来源 > 单一来源
4. 代码/规范 > 主观观点

3.4 Wave Completion Criteria

3.4 阶段完成标准

Stop wave when:
  • Primary question answered with high confidence
  • Multiple authoritative sources agree
  • Diminishing returns (same info repeating)
Proceed to next wave when:
  • Gaps remain in understanding
  • Only low-credibility sources found
  • Conflicting information needs resolution
停止当前阶段的条件:
  • 核心问题已得到高置信度的答案
  • 多个权威来源结论一致
  • 边际收益递减(重复出现相同信息)
进入下一阶段的条件:
  • 仍存在理解缺口
  • 仅找到低可信度来源
  • 存在需要解决的冲突信息

Phase 4: Synthesis

第四阶段:结果整合

4.1 Refresh Context

4.1 回顾背景

Read the full research log before synthesizing.
在整合前通读完整研究日志。

4.2 Cross-Reference Findings

4.2 交叉验证发现

Verify key claims appear in multiple independent sources:
markdown
undefined
验证关键结论是否在多个独立来源中出现:
markdown
undefined

Cross-Reference Matrix

交叉验证矩阵

FindingOfficialCommunityExpert
{Finding 1}✓ source✓ source-
{Finding 2}✓ source✓ source✓ source
{Finding 3}-✓ source-
undefined
结论官方来源社区资源专家来源
{结论1}✓ 来源✓ 来源-
{结论2}✓ 来源✓ 来源✓ 来源
{结论3}-✓ 来源-
undefined

4.3 Write Synthesis

4.3 撰写整合结果

markdown
undefined
markdown
undefined

Synthesis

结果整合

Answer to Primary Question

核心问题答案

{Direct answer} Confidence: High | Medium | Low Based on: {N} sources, {consensus level}
{直接回答} 置信度: 高 | 中 | 低 依据: {N}个来源,{共识程度}

Key Findings

关键发现

  1. {Finding with source citations}
  2. {Finding with source citations}
  3. {Finding with source citations}
  1. {带来源引用的结论}
  2. {带来源引用的结论}
  3. {带来源引用的结论}

Hypothesis Resolution

假设验证结果

  • H1: {CONFIRMED/REFUTED} — {evidence}
  • H2: {CONFIRMED/REFUTED} — {evidence}
  • H1: {已确认/已证伪} — {证据}
  • H2: {已确认/已证伪} — {证据}

Caveats and Limitations

注意事项与局限性

  • {What we couldn't verify}
  • {Where information was sparse}
  • {Time-sensitivity concerns}
  • {无法验证的内容}
  • {信息稀缺的领域}
  • {时效性相关问题}

Recommendations

建议

  1. {Primary recommendation with rationale}
  2. {Alternative approach and when to use}
  3. {What to avoid and why}
  1. {核心建议及理由}
  2. {替代方案及适用场景}
  3. {需避免的情况及原因}

Sources by Authority

按权威性排序的来源

Official:
  • {Source with URL}
Community (High credibility):
  • {Source with URL}
Other:
  • {Source with URL}
undefined
官方来源:
  • {来源及URL}
高可信度社区来源:
  • {来源及URL}
其他来源:
  • {来源及URL}
undefined

4.4 Present Summary

4.4 呈现摘要

undefined
undefined

Research Complete

研究完成

Question: {Primary question} Confidence: High | Medium | Low Waves completed: {N} Sources consulted: {N}
问题: {核心问题} 置信度: 高 | 中 | 低 完成阶段: {N} 参考来源数量: {N}

Answer

答案

{Concise direct answer}
{简洁直接的回答}

Key Findings

关键发现

  • {Finding 1}
  • {Finding 2}
  • {Finding 3}
  • {发现1}
  • {发现2}
  • {发现3}

Recommendations

建议

  1. {What to do}
  2. {What to avoid}
  1. {行动建议}
  2. {需避免的事项}

Caveats

注意事项

  • {Key limitation}
  • {关键局限性}

Top Sources

核心来源

  • {Most authoritative source}
  • {Second source}
Full research log: /tmp/research-web-{...}.md
undefined
  • {最权威的来源}
  • {次要权威来源}
完整研究日志: /tmp/research-web-{...}.md
undefined

Guidelines

指导原则

DO

建议

  • Document hypotheses BEFORE searching
  • Record ALL sources, even unhelpful ones
  • Note publication dates
  • Cross-reference important claims
  • Acknowledge uncertainty
  • Update log after EACH source
  • 在搜索前记录假设
  • 记录所有来源,即使是无帮助的来源
  • 标注发布日期
  • 交叉验证重要结论
  • 承认信息不确定性
  • 每记录一个来源后更新日志

DON'T

禁忌

  • Trust single sources for important claims
  • Ignore publication dates
  • Present opinions as facts
  • Skip synthesis step
  • Make claims without citations
  • Cherry-pick confirming sources
  • 重要结论仅依赖单一来源
  • 忽略发布日期
  • 将主观观点作为事实呈现
  • 跳过结果整合步骤
  • 无引用来源的情况下提出主张
  • 只选择支持假设的来源

Source Authority Hierarchy

来源权威性层级

  1. Official docs — How things are supposed to work
  2. Source code — How things actually work
  3. GitHub issues — Real problems and workarounds
  4. Stack Overflow — Community solutions (CHECK DATES!)
  5. Technical blogs — Opinions and tutorials (verify claims)
  6. General articles — Background only
  1. 官方文档 — 定义产品应有的工作方式
  2. 源代码 — 反映产品实际的工作方式
  3. GitHub issues — 真实问题及解决方案
  4. Stack Overflow — 社区解决方案(务必检查日期!)
  5. 技术博客 — 观点及教程(需验证结论)
  6. 通用文章 — 仅用于背景了解

Time Sensitivity

时效性

DomainInformation Half-life
Web frameworks6-12 months
Languages1-2 years
CS fundamentals5+ years
Security3-6 months
Cloud services6-12 months
Always note when information might be outdated.
领域信息半衰期
Web框架6-12个月
编程语言1-2年
计算机科学基础5年以上
安全领域3-6个月
云服务6-12个月
始终标注可能过时的信息。

Edge Cases

边缘场景处理

CaseAction
No relevant sourcesNote in log, ask user for alternative terms
All sources outdatedNote prominently, recommend verifying with latest docs
Conflicting authoritative sourcesPresent both with evidence, let user decide
Topic too broadAsk user to narrow scope
Paywalled contentNote limitation, search for alternatives
场景处理方式
无相关来源在日志中记录,请求用户提供替代关键词
所有来源均过时显著标注,建议参考最新文档验证
权威来源存在冲突呈现双方观点及证据,由用户决策
主题过于宽泛请求用户缩小研究范围
内容需付费访问标注局限性,寻找替代来源