generic-deep-research

name	generic-deep-research
description	Template for thorough open-ended research reports. Loaded by the Researcher agent — not user-invocable.
user-invocable	false

Template: Generic Deep Research

Purpose

Use this template when the user wants to understand a topic thoroughly. This is the catch-all for any research request that doesn't fit a more specific template. It covers: deep dives, surveys, explanations, investigations, and exploratory research.

Output Structure

Your report MUST follow this exact structure. Every section is required. Do not skip or reorder sections.

# <Research Topic>

## Executive Summary

Brief overview of the key findings in 3-5 sentences. A busy reader should be able to read only this section and understand the main takeaways.

## Background & Context

Why this topic matters. What prompted the research. Any relevant history or context that frames the findings.

## Findings

### <Subtopic 1>

Detailed findings on the first major aspect of the topic.

### <Subtopic 2>

Detailed findings on the next aspect.

### <Subtopic N>

(Continue with as many subtopics as needed. Organize by theme, chronology, or logical grouping — choose whichever structure best serves comprehension.)

## Analysis

Cross-cutting observations, patterns, and implications that span multiple findings. This is where you synthesize — connect the dots between findings, identify trends, and draw out what the findings mean in context.

## Open Questions & Gaps

- What couldn't be determined from available sources.
- Areas where confidence is low and why.
- Suggested follow-up research that would fill gaps.

## Sources

1. [Source Name](URL) — Brief description of what this source contributed.
2. [Source Name](URL) — Brief description.
(Number all sources. Include URLs where available.)

Analytical Lens

• Breadth first, then depth. Start by mapping the full landscape of the topic, then go deep on the most important threads.
• Prioritize accuracy and nuance over brevity. Don't oversimplify. If something is complicated, explain the complexity.
• Distinguish fact from analysis. In the Findings sections, present what you found. In the Analysis section, present what you think it means.
• Name your sources inline. Don't just list sources at the end — reference them as you present findings: "According to Source, ..."

Quality Checklist

Before delivering the report, verify:

• Executive Summary captures the key takeaways without requiring the reader to read further
• Background section provides enough context for someone unfamiliar with the topic
• Findings are organized in a logical structure (not just dumped sequentially)
• Each finding cites at least one source
• Analysis section adds insight beyond restating findings
• Open Questions section is honest about what you don't know
• All sources are listed with URLs
• The report would be useful to a senior technical leader making decisions based on it

Grimoire Publishing

• Sub-path: research-agent-deep/deep-research/
• Type tag: type/deep-research
• source_agent: researcher

When publishing to the Grimoire, do not include YAML frontmatter in the file. The CLI manages frontmatter via create-file-metadata. Include descriptive topic tags alongside the type tag.

Gathering Strategy

1. Start with 2-3 broad WebSearch queries to map the topic landscape.
2. Identify the most authoritative/relevant results and WebFetch them for detailed reading.
3. Check local files (Read/Glob/Grep) if the topic relates to the current project or codebase.
4. If the first round reveals subtopics or angles you hadn't considered, run additional searches.
5. Aim for at least 5 substantive sources before drafting. More is better for complex topics.