deep-research

# /deep-research — Multi-source research with archive Plans, executes, and synthesizes research from multiple sources. Archives the output so the corpus compounds. ## Step 1 — Frame the question Restate the research question in one tight sentence. If ambiguous, ask the user: - What's the decision this research will inform? - What's the minimum useful answer? (Saves over-researching.) - Any sources to prioritize or avoid? Output: `**Research question:** <one sentence>` ## Step 2 — Plan the sources Pick from this menu based on the question type. Note which sources you'll hit and why. | Source | When to use | Tool | |---|---|---| | Web search (Google) | Authoritative articles, docs, official statements | `WebSearch` | | `/last30days` | What people are *actually saying* right now — Reddit, X, YouTube, HN, web recency | `Skill({skill: "last30days", args: "<topic>"})` | | Specific URLs | When the user hands over starting URLs | `WebFetch` | | Browsable pages (auth-walled, JS-heavy) | Pricing pages, product tours, profiles | `agent-browser` via the `compound-engineering:agent-browser` skill | | Memory | Prior research / decisions / context the user already captured | grep `~/.claude/memory/` | | Notion | If the topic touches a known Notion workspace | Direct Notion API (key in `$NOTION_API_KEY`, see `reference_notion_api.md`) | | Research archive | Prior `/deep-research` runs that touched this topic | grep `${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/deep-research/archiv...