Yotto3s Oneteam Agents Research

Research

Overview

A 3-phase workflow for answering research questions by searching the web and/or codebase, then synthesizing findings into a structured summary.

When to Use

• Caller needs information from the web (API docs, library usage, best practices)
• Caller needs to understand codebase patterns or conventions
• Caller needs to cross-reference external docs with local code
• Any question where the answer requires searching multiple sources

When NOT to Use

• The caller already has the information and just needs to act on it
• The question can be answered from a single known file (just Read it directly)

Phase Pipeline

Phase 1: Clarify

Before searching anything, understand what is being asked.

1. Restate the question. Write a single sentence capturing what the caller needs to know. If the question is ambiguous, state your interpretation explicitly.
2. Identify known context. What did the caller already provide? What can be assumed from the project context?
3. Choose search strategy:
   • Web-only: Question is about external tools, libraries, APIs, or general knowledge
   • Codebase-only: Question is about how the current project works
   • Both: Question requires cross-referencing external docs with local code
4. Formulate sub-queries. Decompose the question into 2-3 focused search queries. Each sub-query targets one specific aspect of the question.

Phase 2: Gather

Execute searches iteratively. Maximum 3 rounds — then report what you have.

Search strategies:

• Web: Start narrow with specific terms, broaden only if results are poor. Try different phrasings if first query underperforms. Prefer primary sources: official docs > authoritative blogs > AI-generated content. Triangulate important claims against 2+ independent sources.
• Codebase: Use Glob-then-Read (find files by pattern first, read only relevant ones). Use Grep for specific function names, patterns, or error strings. Start specific, broaden only if needed.

After each round, check: did this answer part of the question? Re-anchor to the original question to prevent drift. Identify remaining gaps to target in the next round. Track all sources (URLs, file paths with line numbers).

Stop gathering when:

• The question is fully answered, OR
• 3 search rounds are complete (report what you have with open questions)

Phase 3: Synthesize

Produce the Research Summary in exactly this format:

## Research Summary: [Topic]

**Question:** [Original question restated from Phase 1]

### Key Findings
- [Finding 1 — concise, actionable]
- [Finding 2]
- ...

### Sources
- [URL or file:line_number 1]
- [URL or file:line_number 2]

### Confidence
[HIGH / MEDIUM / LOW] — [one sentence justification]

### Open Questions
- [Anything unresolved or worth further investigation]

Confidence levels:

• HIGH: Multiple authoritative sources agree, or confirmed in official docs
• MEDIUM: Found in 1-2 sources, or sources partially conflict
• LOW: Limited sources, outdated information, or could not fully verify

Quick Reference

Common Mistakes

Constraints

• Never modify files or create artifacts. Research is read-only.
• Always synthesize. Never return raw search results or copy-paste from sources.
• Max 3 search rounds. Then report what you have — do not rabbit-hole.
• Always include sources and confidence level. No unsourced claims.
• Answer the question asked. Do not drift into tangential topics.
• Re-anchor after each search round. Compare findings against the original question.
• State ambiguity upfront. If the question is unclear, state your interpretation in Phase 1 before searching.
• In team mode, send the Research Summary via SendMessage to the requester.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.