Deep Research Agent Brief
Turn a vague question into a fully-specified research brief: sub-questions, source-quality rules, contradiction handling, and a defined 'enough'.
Research this thoroughly: [THE QUESTION] Why I'm asking + the decision it feeds: [THE CONTEXT: this sets depth and angle] Scope boundaries: [TIMEFRAME THAT MATTERS (e.g. "2024-present"), GEOGRAPHY, WHAT'S EXPLICITLY OUT OF SCOPE] Output: [REPORT LENGTH + FORMAT, e.g. "2-page brief with a comparison table"] Before searching, do two things: 1. **Decompose**: break the question into 3-6 sub-questions that together answer it. Show me the list. If my question is ambiguous in a way that changes the research (which market? which definition of X?), ask now: one clarifying round beats a report about the wrong thing. 2. **Plan the search**: for each sub-question: the search angle, and what kind of source would settle it. Research rules: - **Source hierarchy, enforced:** primary sources (official docs, standards bodies, original studies, company filings) > reputable secondary reporting > everything else. SEO listicles and vendor marketing pages are leads to primary sources, never citations themselves. Note the publication date on every source; flag anything stale for the timeframe I set. - **Broad, then narrow:** start with short broad queries to map the territory, then progressively specific ones. Vary search phrasings: one phrasing samples one slice of the web. - **Citation discipline:** every non-obvious claim in the report carries its source, and the source must actually say the thing, never attach a citation to a sentence it doesn't support. Distinguish plainly: [ESTABLISHED: multiple quality sources agree] / [SINGLE-SOURCE: one source, graded] / [INFERRED: my synthesis, reasoning shown]. - **Contradictions are findings:** when sources disagree, present both with dates and authority, and explain the likely reason (methodology, timeframe, incentive), never silently pick one. - **Stop rule: define "enough":** a sub-question is DONE when [N, default 2-3] independent quality sources agree, or when further searches return the same results. When done, stop. Do not keep searching for comfort. Cap total effort at roughly [BUDGET, e.g. "20 searches"]; if the budget exhausts with sub-questions open, report them as open rather than padding. Report structure: 1. Bottom line (the answer in 3-4 sentences, confidence stated). 2. Findings per sub-question, each with its evidence grade and citations. 3. Contradictions and uncertainties: what's genuinely unsettled. 4. What I'd research next with more budget, ranked. 5. Source list with one-line quality notes.
How to use
Deep-research tools expect fully-formed briefs and won't ask for missing context: that's why the decompose-and-confirm step comes first. The two failure modes this prevents, straight from the lab post-mortems: agents laundering SEO content into confident claims (the source hierarchy), and agents that never stop searching (the defined 'enough'). Works pasted into ChatGPT deep research, Claude with web search, or as the task brief for any research agent.
More agent prompts
You are a software engineering agent working in the [PRODUCT/TEAM] codebase ([LANGUAGE/STACK]). Your objective is to take an assigned task from description to verified, working code. You may read and modify anything in the repository; you do not push, merge, deploy, or alter CI configuration unless the task explicitly says to. # Operatin
Coding Agent System Prompt
Autonomous coding agent that matches repo conventions, proves work with passing tests before claiming done, and reports failures truthfully.
You are a debugging agent for the [PRODUCT] codebase. Your objective is to find the root cause of a reported bug, fix it with the smallest possible change, and prove the fix. You are not here to refactor, harden, or improve unrelated code: a debugging session that ends in a 40-file diff has failed even if the bug is gone. # Reproduce Bef
Debugging Agent System Prompt
Root-cause-first debugging agent: no fix until the bug is reproduced, minimal diffs only, and done means the repro dies while the test suite stays green.
You are a code migration agent. Your objective is to move the [PRODUCT] codebase from [SOURCE VERSION/FRAMEWORK] to [TARGET VERSION/FRAMEWORK] while preserving behavior exactly. You are a mechanical translator with judgment, not a redesigner: the product must work the same after every step you take. # The Prime Rule: Migration Changes On
Code Migration Agent System Prompt
Framework-upgrade agent that migrates in build-green slices, verifies every codemod, follows official guides over memory, and never mixes in behavior changes.