Plan Research
Uses Planner. Investigate a problem space by gathering evidence from the codebase, documentation, and external sources. Produce a structured research summary with cited sources.
Prerequisites: Clear research question or problem statement
Phase 1: Scope the Investigation
Define Research Boundaries
- State the research question clearly
- Identify what you need to learn and why
- Define what is in-scope and out-of-scope
- List known starting points (files, docs, APIs, prior ADRs)
Output
## Context Anchors
- **Issue:** #<number> - <title>
- **Phase:** 1 — Scope
## Research Question
<Clear statement of what needs to be investigated>
## Scope
**In:** <what to investigate>
**Out:** <what to exclude>
## Starting Points
- <file, doc, or source 1>
- <file, doc, or source 2>
## Next Step
Begin evidence gathering.
**Approval Required:** No
Phase 2: Gather Evidence
Internal Sources
- Search the codebase for relevant patterns, implementations, and conventions
- Read existing ADRs, architecture docs, and design notes
- Review git history for context on past decisions
- Quantify where possible (line counts, file counts, dependency counts)
External Sources
- Use
web/fetch to read official documentation, changelogs, or specifications
- Use
web/githubRepo to inspect upstream repositories for README, examples, or release notes
- Do NOT rely solely on training knowledge for version-specific behavior, API signatures, or configuration options — verify against the source
- Cite every external source with a URL or repository reference
Evidence Standards
- Every claim must link to a specific file, line, URL, or commit
- Distinguish verified facts from inferences
- Note contradictions between sources
- Record what you searched for and didn't find (negative evidence)
Output
## Context Anchors
- **Issue:** #<number> - <title>
- **Phase:** 2 — Gather Evidence
## Findings
### <Topic 1>
<Finding with source citation>
**Source:** <file path, URL, or commit>
### <Topic 2>
<Finding with source citation>
**Source:** <file path, URL, or commit>
## Negative Evidence
- Searched for <X>, not found in <scope>
## Next Step
Synthesize findings into a research summary.
**Approval Required:** No
Phase 3: Synthesize
Produce Research Summary
- Combine findings into a coherent picture
- Identify patterns, gaps, and contradictions
- State implications for the original research question
- List open questions that remain unanswered
Output
## Context Anchors
- **Issue:** #<number> - <title>
- **Phase:** 3 — Synthesize
## Research Summary
<Coherent synthesis of findings>
## Key Insights
1. <insight 1>
2. <insight 2>
3. <insight 3>
## Open Questions
- <question that remains unanswered>
## Sources
| Source | Type | Key Finding |
| ------ | ------------------- | ----------------- |
| <ref> | <internal/external> | <what it told us> |
## Next Step
Research complete. Findings available for design, planning, or decision-making.
**Approval Required:** Yes
⛔ CHECKPOINT
STOP. Do not proceed until human confirms the research summary is accurate and sufficient.
Error Handling
| Error |
Recovery |
| Research question too broad |
Narrow scope, break into sub-questions |
| External source unavailable |
Note the gap, try alternative sources |
| Contradictory evidence |
Document both sides, flag for human judgment |
| Insufficient evidence |
State what's missing, recommend additional investigation |
1---2name: plan-research-33description: Research a problem space with evidence gathering and source validation4---5
6# Plan Research
7
8Uses **Planner**. Investigate a problem space by gathering evidence from the codebase, documentation, and external sources. Produce a structured research summary with cited sources.
9
10**Prerequisites:** Clear research question or problem statement
11
12---
13
14## Phase 1: Scope the Investigation
15
16### Define Research Boundaries
17
181. State the research question clearly
192. Identify what you need to learn and why
203. Define what is in-scope and out-of-scope
214. List known starting points (files, docs, APIs, prior ADRs)
22
23### Output
24
25```markdown
26## Context Anchors
27
28- **Issue:** #<number> - <title>
29- **Phase:** 1 — Scope
30
31## Research Question
32
33<Clear statement of what needs to be investigated>
34
35## Scope
36
37**In:** <what to investigate>
38**Out:** <what to exclude>
39
40## Starting Points
41
42- <file, doc, or source 1>
43- <file, doc, or source 2>
44
45## Next Step
46
47Begin evidence gathering.
48
49**Approval Required:** No
50```
51
52---
53
54## Phase 2: Gather Evidence
55
56### Internal Sources
57
581. Search the codebase for relevant patterns, implementations, and conventions
592. Read existing ADRs, architecture docs, and design notes
603. Review git history for context on past decisions
614. Quantify where possible (line counts, file counts, dependency counts)
62
63### External Sources
64
651. Use `web/fetch` to read official documentation, changelogs, or specifications
662. Use `web/githubRepo` to inspect upstream repositories for README, examples, or release notes
673. Do NOT rely solely on training knowledge for version-specific behavior, API signatures, or configuration options — verify against the source
684. Cite every external source with a URL or repository reference
69
70### Evidence Standards
71
72- Every claim must link to a specific file, line, URL, or commit
73- Distinguish verified facts from inferences
74- Note contradictions between sources
75- Record what you searched for and didn't find (negative evidence)
76
77### Output
78
79```markdown
80## Context Anchors
81
82- **Issue:** #<number> - <title>
83- **Phase:** 2 — Gather Evidence
84
85## Findings
86
87### <Topic 1>
88
89<Finding with source citation>
90
91**Source:** <file path, URL, or commit>
92
93### <Topic 2>
94
95<Finding with source citation>
96
97**Source:** <file path, URL, or commit>
98
99## Negative Evidence
100
101- Searched for <X>, not found in <scope>
102
103## Next Step
104
105Synthesize findings into a research summary.
106
107**Approval Required:** No
108```
109
110---
111
112## Phase 3: Synthesize
113
114### Produce Research Summary
115
1161. Combine findings into a coherent picture
1172. Identify patterns, gaps, and contradictions
1183. State implications for the original research question
1194. List open questions that remain unanswered
120
121### Output
122
123```markdown
124## Context Anchors
125
126- **Issue:** #<number> - <title>
127- **Phase:** 3 — Synthesize
128
129## Research Summary
130
131<Coherent synthesis of findings>
132
133## Key Insights
134
1351. <insight 1>
1362. <insight 2>
1373. <insight 3>
138
139## Open Questions
140
141- <question that remains unanswered>
142
143## Sources
144
145| Source | Type | Key Finding |
146| ------ | ------------------- | ----------------- |
147| <ref> | <internal/external> | <what it told us> |
148
149## Next Step
150
151Research complete. Findings available for design, planning, or decision-making.
152
153**Approval Required:** Yes
154```
155
156### ⛔ CHECKPOINT
157
158**STOP.** Do not proceed until human confirms the research summary is accurate and sufficient.
159
160---
161
162## Error Handling
163
164| Error | Recovery |
165| --------------------------- | -------------------------------------------------------- |
166| Research question too broad | Narrow scope, break into sub-questions |
167| External source unavailable | Note the gap, try alternative sources |
168| Contradictory evidence | Document both sides, flag for human judgment |
169| Insufficient evidence | State what's missing, recommend additional investigation |