Research Branch Exploration
Requirements
- branch_name: Name of the branch to explore (e.g., "Fundamentals", "Players")
- parent_context: Key findings from prior rounds that inform this search
- search_queries: 2-4 specific search queries to execute
- depth_target: surface | moderate | deep
1
VALIDATE INPUTS
Check that all requirements are provided:
- branch_name
- parent_context (can be empty for round 1)
- search_queries (at least 2)
- depth_target
If any are missing, log the error and exit early.
2
FOCUSED BRANCH EXPLORATION
Execute the provided search queries using @tool/websearch.
For each search result:
- Extract key facts relevant to the branch topic
- Note the source URL and publication date
- Assess source quality (authoritative, recent, relevant)
- Flag any contradictions with parent_context findings
Aim for:
- surface depth: 2-3 key facts per query
- moderate depth: 4-5 key facts per query, cross-referenced
- deep: 6+ key facts, actively seek contradicting viewpoints
3
WRITE FINDINGS
Write structured findings to Branch Findings using branch_name as the filename:
{
"branch": "branch_name from requirements",
"queries_executed": ["query1", "query2"],
"findings": [
{
"fact": "Statement extracted from source",
"source": "https://...",
"confidence": "high|medium|low",
"date": "source date if available"
}
],
"conflicts": [
{
"claim_a": "Statement from source A",
"claim_b": "Contradicting statement from source B",
"assessment": "Which seems more reliable and why"
}
],
"suggested_followups": [
"Specific question raised by these findings?"
],
"summary": "2-3 sentence synthesis of this branch's key findings"
}Use the branch_name from requirements as the filename (lowercase, hyphens for spaces).
4
Confirm completion: 'Finished exploring {branch_name}. Findings saved.'
To run this task you must have the following required information:
> - branch_name: Name of the branch to explore (e.g., "Fundamentals", "Players")
- parent_context: Key findings from prior rounds that inform this search
- search_queries: 2-4 specific search queries to execute
- depth_target: surface | moderate | deep
If you don't have all of this information, exit here and respond asking for any extra information you require, and instructions to run this task again with ALL required information.
---
You MUST use a todo list to complete these steps in order. Never move on to one step if you haven't completed the previous step. If you have multiple read steps in a row, read them all at once (in parallel).
Add all steps to your todo list now and begin executing.
## Steps
1. VALIDATE INPUTS
Check that all requirements are provided:
- branch_name
- parent_context (can be empty for round 1)
- search_queries (at least 2)
- depth_target
If any are missing, log the error and exit early.
2. FOCUSED BRANCH EXPLORATION
Execute the provided search queries using @tool/websearch.
For each search result:
1. Extract key facts relevant to the branch topic
2. Note the source URL and publication date
3. Assess source quality (authoritative, recent, relevant)
4. Flag any contradictions with parent_context findings
Aim for:
- surface depth: 2-3 key facts per query
- moderate depth: 4-5 key facts per query, cross-referenced
- deep: 6+ key facts, actively seek contradicting viewpoints
3. WRITE FINDINGS
Write structured findings to `./documents/tmp/branch-findings/*.json` using branch_name as the filename:
```json
{
"branch": "branch_name from requirements",
"queries_executed": ["query1", "query2"],
"findings": [
{
"fact": "Statement extracted from source",
"source": "https://...",
"confidence": "high|medium|low",
"date": "source date if available"
}
],
"conflicts": [
{
"claim_a": "Statement from source A",
"claim_b": "Contradicting statement from source B",
"assessment": "Which seems more reliable and why"
}
],
"suggested_followups": [
"Specific question raised by these findings?"
],
"summary": "2-3 sentence synthesis of this branch's key findings"
}
```
Use the branch_name from requirements as the filename (lowercase, hyphens for spaces).
4. Confirm completion: 'Finished exploring {branch_name}. Findings saved.'