deep-research
Deep Research
You produce a 5-minute brief on a topic that's actually useful — not a Wikipedia summary, not a slop of search results. The brief tells the user what they need to know, where the open questions are, and what they should think about the topic.
Before you start
Get just enough to scope properly:
- Topic — what specifically?
- Why now — what's prompting the research? (Meeting, decision, content piece, just curious?)
- Depth — quick (10 min of effort) or deep (30+)?
- Format preference — straight brief, comparison table, decision-oriented?
- What you already know — so the brief doesn't waste space repeating it
If the user just dropped a topic with no context, default to: ~15 minutes of research, decision-neutral brief, assume baseline familiarity.
Plan the research
Before searching, identify what kinds of sources you actually need:
More from thecraighewitt/skills
ralph
Autonomous PRD implementation loop — turns GitHub issues into shipped code using TDD, code review gates, and Docker sandbox isolation. The execution engine for the grill-me → write-a-prd → prd-to-issues → ralph pipeline.
43shape
Use when you have a rough product idea and want a complete PRD without sitting through an interactive grilling. Claude walks the full decision tree (edge cases, modules, schema, testing, security), self-answers with software-engineering best practices, streams the Q&A live so you can override, and writes the PRD locally with an option to push as a GitHub issue.
40linkedin-outreach
When the user wants to write LinkedIn connection requests, InMails, DM sequences, build a social selling strategy, or use Sales Navigator for prospecting. Also use when the user says 'LinkedIn message,' 'connection request,' 'InMail template,' 'social selling,' 'LinkedIn outreach,' 'social selling strategy,' 'LinkedIn prospecting,' 'Sales Navigator,' 'LinkedIn DM,' 'LinkedIn video message,' 'LinkedIn lead list.' For email outreach, see cold-email. For multi-channel sequences, see outbound-sequence. For profile research, see lead-research.
21forecast
When the user wants to forecast sales revenue, build a commit/upside/best-case forecast, calculate weighted pipeline, predict whether they'll hit their number, or run a forecast call. Trigger phrases: 'will we hit quota,' 'forecast this quarter,' 'weighted pipeline,' 'build a sales forecast,' 'commit number,' 'are we going to hit the number,' 'revenue projection,' 'what's our gap,' 'pipeline math,' 'deal review,' 'forecast call.' For pipeline data that feeds the forecast, see pipeline-review. For comp plans tied to quota, see sales-comp.
18discovery-call
When the user wants to plan a discovery call, build discovery questions, qualify a lead, or prep for a first call with a prospect. Also use when the user says 'prep for a discovery call,' 'write discovery questions,' 'help me qualify this deal,' 'qualify a lead,' 'first call with a prospect,' 'initial meeting.' For deep buyer research before the call, see buyer-persona. For post-call analysis, see call-debrief.
18referral-intro
When the user wants to ask for a warm introduction, build a referral program, or systematize their referral channel. Also use when the user says 'get me an intro,' 'ask for a referral,' 'write a forwardable email,' 'warm introduction,' 'partner referral,' 'reference request,' 'intro email,' 'leverage my network,' 'referral program,' 'ask for an intro at dinner,' or 'track referrals in CRM.' For cold outreach without a warm path, see cold-email or linkedin-outreach. For sequencing referral asks into a cadence, see outbound-sequence. For running the meeting after a referral intro is made, see discovery-call.
18