research-prompt

Converts vague research requests into scoped, sourceable briefs before dispatching research subagents.

Updated Nov 1, 2024
One-click install
npx skills add https://github.com/mlorentedev/dotfiles --skill research-prompt-mlorentedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-prompt
Source: https://github.com/mlorentedev/dotfiles/tree/main/harness/skills/research-prompt
Command: npx skills add https://github.com/mlorentedev/dotfiles --skill research-prompt-mlorentedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague research requests like "look into X" force research agents to guess scope, sources, and completion criteria, producing unfocused reports that waste long-running agent runs. This Skill sharpens the ask into a tight, sourceable brief before any subagent is dispatched. ## Core Features & Use Cases - Five-slot brief structure: Fills question, scope boundary, sources, output shape, and done-criteria before dispatching any research work. - Subagent routing guidance: Directs the brief to the right agent type — research for citation-heavy external work, explore for codebase lookups, task for command-output checks. - Artifact placement rules: Decides where the resulting report lives (project docs vs. cross-project research vault) before the agent starts, preventing orphan reports. - Use Case: Before asking a research agent "which observability stack should we use", run this Skill to produce a brief specifying the cardinality constraints, candidate tools, sources to check, and what a sufficient answer looks like. ## Quick Start Ask the assistant to turn your rough research question into a research brief before launching a research subagent.

Frequently Asked Questions about research-prompt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a good research brief for an AI agent?

A good research brief fills five slots: a falsifiable one-sentence question, an explicit scope boundary, named sources to check first, the desired output shape, and done-criteria defining sufficiency. Write it as a short paragraph or five-line list, not a form.

When should I sharpen a research question before dispatching an agent?

Sharpen the ask when the request is one sentence and open-ended, or before any long-running deep-research session where wrong scope wastes the full run. Skip it for quick factual lookups answerable in one or two fetches.

What is the difference between research, explore, and task subagents?

Use research for external citation-heavy work, explore for fast internal codebase lookups, and task for command-output-style checks. The brief should be included verbatim in the subagent prompt since subagent prompts are stateless.

Why do research agents produce unfocused reports?

Unfocused reports come from under-specified requests where the agent must guess scope, sources, and what done means. Accepting "also look into whatever seems relevant" as a scope boundary is the most common cause of silent scope creep.

Where should research artifacts be stored?

Project-bound research goes in that repository's docs directory or a pre-repo research folder; cross-project tooling or methodology research goes in a shared research vault. Decide placement before dispatching, not after the report lands.