Research

---
name: research
description: "Deep research before planning. Launches parallel agents across docs, web, and codebase, then synthesizes findings into actionable context."
---

$ARGUMENTS

Research this thoroughly before any planning or implementation begins.

## How to research

### Step 1: Clarify before you research (MANDATORY — never skip)

Before reading a single file or launching any agent, use AskUserQuestion. Read the input and identify every place where you have 2+ plausible interpretations — scope, intent, constraints, approach, priority. Ask about those specifically.

**How to ask:** Present choices tailored to the actual input, not generic categories. The options should come directly from the ambiguities in what was asked. If you see three plausible ways to interpret what the user wants, list those three things and ask which is closest. Don't ask what you can already infer. Do ask anything that would materially change what you research or recommend. **For every option, include a plain-language ELI5 explanation of the tradeoff — never assume the user knows the underlying technical details.**

Good trigger conditions for asking:
- The input describes a symptom but not a root cause — ask what they think the cause is, with options
- The input proposes a solution — ask if the solution is required or just a starting hypothesis
- The scope is fuzzy — ask whether they want a targeted fix or a broader rethink, with examples of each
- Multiple approaches exist with real tradeoffs — ask which tradeoffs matter most to them
- The change could affect related systems — ask whether those are in scope
- Any constraint (time, backwards-compat, file/dependency, team conventions) is unstated — ask

Keep questions short. Use choices and options, not open prompts. "Which of these is closer?" beats "Can you describe your constraints?". An "other/none of these" escape hatch is always fine to include. **Each option must explain its tradeoff in simple terms a non-expert would immediately understand.**

Ask as many questions as the ambiguity warrants — but batch them into a single AskUserQuestion call so the user responds once.

**Do not launch any agents until you have the answers.**

### Step 2: Parse intent

With the answers in hand, read critically:
- What is the **core problem** — distinct from the proposed solution?
- Does any answer change the scope or approach from what was originally described?
- Are there remaining ambiguities? If yes, use AskUserQuestion again — don't bank on assumptions.
- Frame 2-4 specific research questions around the problem.