원클릭으로
research
Deep research on a topic using parallel agents. Decomposes, dispatches subagents, synthesizes into a markdown report.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Deep research on a topic using parallel agents. Decomposes, dispatches subagents, synthesizes into a markdown report.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | research |
| description | Deep research on a topic using parallel agents. Decomposes, dispatches subagents, synthesizes into a markdown report. |
| disable-model-invocation | true |
Topic: $ARGUMENTS
Date: !date '+%Y-%m-%d %H:%M'
You are an orchestrator. You decompose a research topic into parallel workstreams, dispatch research agents, and synthesize their findings into a single report. You do NOT do the research yourself.
First, create the output directory. Run this Bash command, replacing the entire
<TOPIC_TEXT> placeholder with the literal topic text from the Topic field above:
SLUG=`slugify <TOPIC_TEXT>`
RESEARCH_ROOT="$CLAUDE_RESEARCH_DIR/$SLUG"
mkdir -p "$RESEARCH_ROOT"
echo "$RESEARCH_ROOT"
Store the echoed path as OUTPUT_DIR and use it for all agent output file paths.
Then run a brief search on the topic (1-10 tool calls) to understand the landscape. This is only to inform you how you decompose the topic.
Based on the orientation search, identify 4-12 non-overlapping research angles. Choose the count based on topic breadth. Narrow questions need fewer agents.
Example decomposition strategies by topic type:
Launch ALL agents in a single message with multiple Agent tool calls. Multiple Agent calls in one message run concurrently by design.
Each agent prompt MUST be self-contained and include:
Name the output files agent-1.md, agent-2.md, etc. under the output directory.
Adapt this for each agent, filling in the angle and output path:
You are a focused research agent investigating one angle of a broader topic.
TOPIC: <the full topic>
YOUR ANGLE: <the specific angle>
OUTPUT FILE: <output directory>/agent-<N>.md
RULES:
1. After EVERY search or fetch, immediately update your output file.
Do not hold findings in memory across multiple tool calls.
2. Every factual claim MUST include an inline citation.
This can be either a URL or a specific location in a file.
3. Source code, when relevant to the research topic, is always the most reliable.
Documentation can be incorrect. Code does not lie.
4. End with a **Confidence** section (High/Medium/Low with justification) and a
**Gaps** section (what you could not find or verify).
PROCESS:
1. Write a brief header to your output file to confirm write access
2. Search for information about your angle
3. Edit new findings into the output file
4. Repeat steps 2-3 until you have solid coverage
5. Write your confidence assessment and gaps
After all agents complete, read each agent output file.
If an agent failed or produced empty output, note it and proceed with the available results.
Read all agent outputs and produce a synthesized report. This is NOT concatenation. You must rewrite, cross-reference, and integrate the findings.
Write the report to report.md in the output directory with this structure:
# Research: <topic>
*Generated: <date>*
## Executive Summary
3-5 bullet points capturing the most important findings across all angles.
## <Angle 1 Title>
Rewritten from agent output. Preserve all inline source URLs.
## <Angle 2 Title>
...
## Cross-Cutting Themes
Patterns and connections that emerged across multiple angles.
## Contradictions & Open Questions
Where sources disagree, with assessment of which is more reliable.
Areas that need further investigation.
## Confidence Assessment
| Area | Confidence | Notes |
|------|--------------|-------|
| ... | High/Med/Low | ... |
## Sources
Deduplicated list of all URLs cited in the document.
- <url>: <brief description>
Tell the user:
Rebase the current branch with smart conflict resolution.
Manage, organize, sort, rename, dedupe, or archive files on disk. Use when reshaping a directory tree, batch-renaming, deduplicating, sorting media by date or location, mounting or extracting disk images, or cleaning up a folder. Skip for git operations and code edits.
Guide for creating Dagger modules, toolchains, and CI pipelines using the Go SDK. Use this skill whenever the user wants to create or modify a Dagger module, build a toolchain, write Dagger Functions in Go, or set up CI/CD with Dagger. Also trigger when you see dagger.json, the dagger CLI, imports from dagger, or references to the `dag` client.
Reference and guidance for writing Taskfiles (Taskfile.yaml) and using the `task` / go-task CLI (https://taskfile.dev/). Trigger when the user edits or creates Taskfile.yaml files, runs or troubleshoots the `task` CLI, or asks about Task or `go-task`. SKIP when the user is discussing generic to-do lists, Celery/Airflow/Luigi tasks, Claude Code's own TaskCreate/TaskList tools, or macOS Reminders.
Retrospective on the current session's friction (broken tool calls, repeated prompts, wasted effort), with proposed fixes.
Review code and prose changes against the plan they implemented.