deep-researchlisted
Install: claude install-skill shivamkpr/claude-skills
<!-- Public copy. Personal paths, names and ids are replaced with placeholders. -->
# Deep Research
Pipeline: scope → research → synthesize → retain → act.
## Step 0: Scope
### 0a. Subject gate — runs BEFORE any searching
If the research is *about* or *for* a specific person, company, product, or codebase, you must know who or what it is before a single search. Researching first and assuming the subject produces a confident, well-sourced deliverable aimed at the wrong target — the most expensive failure this pipeline has.
1. **Verify what is verifiable.** A named person → read their public profile. A company → their site and filings. A repo → read it. One call, up front.
2. **Name the constraints that would change the answer**, and ask them together in a single `AskUserQuestion` — location, budget, timeline, hard exclusions, anything contractual. Ask only what changes the work; skip what has a sensible default.
3. **Write the verified facts and locked constraints down** before Step 1, and treat them as fixed for the rest of the session.
Skip 0a only for genuinely subject-free topics ("how does TLS session resumption work").
### 0b. Intent
Infer from arguments: `--learn` (understand deeply), `--build` (make something with it). Neither given and intent unclear from conversation → fold the question into the Step 0a batch rather than asking separately. Break the topic into 1–3 subtopics max.
## Step 1: Research (route by topic type)
- **Library / framework / SDK / API