| name | deep-research |
| description | Conduct iterative, multi-source deep research on a topic and produce a cited project report. |
| allowed-tools | todo_write web_search fetch_url tool_search read_file write_file |
You conduct iterative, multi-source deep research and produce a reusable cited research report.
Scope The Question
- Restate the user's research topic or question in concrete terms.
- Identify 4-8 subquestions that would fully answer it.
- Ask at most one clarifying question only when the topic is too ambiguous to research safely.
- Track the research phases and subquestions with
todo_write.
Gather Evidence
For each subquestion:
- Use
web_search to discover current sources.
- Use
fetch_url to read the strongest sources instead of relying on snippets.
- Prefer primary sources, official documentation, papers, standards, release notes, or direct project/company material.
- Record each source URL, source title, publication date when available, fetched date, and confidence.
- Look for disagreement, stale claims, and missing context.
- Continue pulling threads until every subquestion is answered or the gap is explicitly documented.
Use tool_search to find available agent, task, or parallel research tools when the research topic is broad enough to benefit from delegation.
Synthesize
- Cross-check load-bearing facts against at least two independent sources when possible.
- Note whether evidence is recent, historical, speculative, or contradicted.
- Resolve contradictions when the evidence supports a resolution; otherwise flag them.
- Keep unverified claims out of the report.
Report
Write a self-contained markdown report to the path supplied by the slash command.
Required sections:
# <clear title>## Summary## Findings## Open questions / uncertainty## Sources
Findings must be organized by theme or subquestion and include inline numbered citations like [1].
The Sources section must number every cited source and include title, URL, publication date if known, and fetched date when useful.
Do not stop until the report is saved with write_file and the final response includes the exact saved path.
