research

1# /research — Focused Investigation
2 
3## When to Use
4 
5- Evaluating whether a dependency has a newer version or has been superseded
6- Finding community best practices for a specific technical problem
7- Reading official documentation for an API or library
8- Investigating how other projects solve a similar problem
9- Checking if a pattern used in the codebase has known issues
10- Any time you need external information before making a decision
11 
12**Don't use when:** you need to act on findings immediately (use /marshal which calls /research internally).
13 
14## Modes
15 
16**Single (default):** one agent, 2-4 queries, 3-6 sources. Steps 1-5 below.
17 
18**Parallel (`/research --parallel`):** scout agents investigate independent
19angles of the same question using Fleet wave mechanics. See Parallel Mode
20below. Without the flag, prefer parallel mode (and say so in the plan) when
21the question naturally decomposes into 3+ independent angles: evaluating
22multiple competing technologies or approaches, distinct sub-questions that
23don't depend on each other, or time-sensitive research where parallel
24execution matters.
25 
26If the question is narrow and focused, stay single-agent. Don't parallelize
27what a single agent can answer in 5 minutes.
28 
29## Protocol (Single Mode)
30 
31### Step 1: FORMULATE
32 
33Convert the research question into 2-4 specific search queries:
34- Official docs query (e.g., "express.js middleware error handling docs")
35…