From deep-research
Deep Research mode — iterative multi-source research producing comprehensive Obsidian reports with citations. Official-docs-first methodology. Triggers: '/deep-research [topic]'
How this skill is triggered — by the user, by Claude, or both
Slash command
/deep-research:deep-research TOPIC or RESEARCH QUESTIONTOPIC or RESEARCH QUESTIONThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You orchestrate a two-phase deep research pipeline. Phase 1 happens here (main thread). Phase 2 is delegated to the `deep-research` agent.
You orchestrate a two-phase deep research pipeline. Phase 1 happens here (main thread). Phase 2 is delegated to the deep-research agent.
The user's raw topic is: $ARGUMENTS
Your job is to turn this raw topic into a precise, well-scoped research brief using prompt-generator methodology. Follow these steps:
Silently determine:
Use AskUserQuestion to ask 1-3 questions. Choose from these dimensions based on what's genuinely unclear — skip any that are obvious from context:
Skip clarification entirely only if the topic is already narrow, unambiguous, and the audience is obvious.
From the user's answers, write a structured research brief:
<research_brief>
<topic>The original topic, cleaned up</topic>
<official_docs>Known official documentation sources, or "none identified" if the topic lacks vendor docs</official_docs>
<scope>Exactly what to research — boundaries, inclusions, exclusions</scope>
<audience>Who this is for and what they need</audience>
<depth>Target source count and iteration budget</depth>
<output>What the final deliverable looks like</output>
<key_questions>
1. Specific question the research must answer
2. Another specific question
3. ...
</key_questions>
</research_brief>
Show the brief to the user. Ask: "Does this capture what you need, or should I adjust the scope?"
Map the user's depth preference to iteration count:
Once the brief is confirmed, spawn the deep-research agent using the Agent tool with:
deep-research<research_brief> XML block from Step 3, plus the iteration budgetbypassPermissions (research agent needs unrestricted tool access for web searches)The agent handles everything from here: iteration, state tracking, and Obsidian output.
When the agent returns, summarize:
Then clean up temporary files: .deep-research-state.md
npx claudepluginhub jl-cmd/claude-deep-research --plugin deep-researchProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.