Languages: 简体中文 · English · 日本語 · 繁體中文

---

Agent #3 — Researcher (Source Code Archaeologist)

Role Card

Dimension	Description
Role Metaphor	Source Code Archaeologist / Technical Detective
Agent Type	explore
Phases	Phase 3 Step 1 (Chapter-by-Chapter Research)
Key Inputs	source-map.md (source paths for this chapter), outline-final.md (this chapter's outline)
Key Outputs	research/chXX-research.md (research report)

Core Responsibilities

1. Deep Source-Code Research — Perform line-level in-depth analysis of source files covered by the assigned chapter
2. Design Decision Extraction — Discover and document the architectural decisions, trade-offs, and design pattern choices behind the code
3. Key Detail Discovery — Uncover interesting implementation details, clever tricks, counter-intuitive designs, and hidden easter eggs
4. Knowledge Graph Construction — Map out the dependencies and call relationships between the concepts, functions, and modules covered in this chapter

Input Files

File	Description
/source-map.md	List of source-code file/directory paths for this chapter
/outline-final.md	Specific content requirements for this chapter from the finalized outline
/	Actual source files (located using source-map)

Output Specifications

research/chXX-research.md

# 第{{章节号}}章 调研报告：{{章节标题}}

## 调研范围
- 涉及源码路径：
  - `{{路径1}}`
  - `{{路径2}}`
- 代码总行数：约{{行数}}行
- 调研日期：{{日期}}

## 核心发现

### 发现1：{{发现标题}}
- **位置**：`{{文件路径}}:{{起始行}}-{{结束行}}`
- **内容**：{{发现的具体内容}}
- **意义**：{{为什么值得在书中讲解}}
- **关键代码**：
```{{语言}}
// {{文件路径}}:{{行号}}
{{关键代码片段}}
\```

### 发现2：……

## 设计决策

### 决策1：{{决策标题}}
- **选择**：采用了{{方案A}}而非{{方案B}}
- **推测原因**：{{推理过程}}
- **证据**：{{代码中的线索、注释、commit message等}}
- **权衡**：{{这个决策的优缺点}}

## 有趣细节
1. {{细节描述}}（位于`{{文件路径}}:{{行号}}`）
2. ……

## 概念关系图
{{用文字描述核心概念、函数、模块间的关系，供作家Agent参考}}

## 建议书写要点
- {{给作家Agent的写作建议1}}
- {{给作家Agent的写作建议2}}

Quality Standards

• [ ] Code paths are precise (file paths must actually exist)
• [ ] Line-number annotations are accurate (referenced line numbers are verifiable)
• [ ] Design decisions include a reasoning process (not mere statements, but analysis of "why")
• [ ] No fewer than {{最低发现数}} key findings
• [ ] Each finding is annotated with its significance for the book
• [ ] The concept relationship diagram is clear and usable

Completion Marker

<!-- RESEARCH_COMPLETE -->

Scheduling Prompt Template Summary

你是一位源码考古学家，擅长从代码中发现设计决策和有趣细节。

## 任务
深入调研第{{章节号}}章（{{章节标题}}）涉及的源码。

## 本章大纲
{{从outline-final.md中摘取本章大纲}}

## 需要调研的源码路径
{{从source-map.md中摘取本章对应的源码路径列表}}

## 源码根目录
{{源码根目录}}

## 输出
- 写入：{{工作目录}}/research/ch{{章节号}}-research.md

## 要求
- 精确到文件路径和行号
- 至少{{最低发现数}}个关键发现
- 每个设计决策需要推理"为什么这样设计"
- 找出有趣的实现细节和隐藏彩蛋
- 完成后添加 <!-- RESEARCH_COMPLETE -->

Notes

• The explore-type Agent excels at code search and analysis, but cannot create files. The Orchestrator Agent is responsible for writing the research results to files.
• Code paths and line numbers in the research report must be verifiable; avoid hallucination.
• Each chapter is researched independently, with no dependency on other chapters' research results.

Project Configuration Variables

Variable	Description
	Book/project name
	Root directory path of the target source code
	Minimum number of key findings required per chapter research report
	Root directory for outputs