parallel-deep-research

Exhaustive research with configurable depth, latency, and cost trade-offs for complex topics. Research topic: $ARGUMENTS ONLY use this skill when the user explicitly requests deep/exhaustive research. Deep research is 10-100x slower and more expensive than parallel-web-search. For normal "research X" requests, quick lookups, or fact-checking, use parallel-web-search instead. If this is a follow-up to a previous research or enrichment task where you know the interaction_id , add context chaining: By chaining interaction_id values across requests, each follow-up question automatically has the full context of prior turns — so you can drill deeper into a topic without restating what was already researched. Use --processor lite for follow-ups since the heavy research was already done in the initial turn and the follow-up just needs to build on that context. This returns instantly. Do NOT omit --no-wait — without it the command blocks for minutes and will time out.