| name | advise-research |
| description | When planning, flag uncertain assumptions and supply a ready-to-run web-research prompt to confirm them. |
| user-invokable | false |
Advise Research If Unsure
When planning, track every assumption, factual claim, API/behavior, or library detail you are NOT 100% certain about. If any exist:
- In the plan file: Add a brief section titled "## Uncertain Assumptions" that lists ONLY those uncertainties and states that the user was advised to run web research to confirm them before implementation. Do NOT put the research prompt itself in the plan file.
- In your chat summary: At the very END of your summary to the user (after everything else), supply the ready-to-run research prompt so they can trigger web research.
If you are confident about everything, state that no research is needed and omit both the section and the prompt.
Research Prompt Structure
Structure the research prompt (delivered in chat, not the plan) as follows:
- ROLE definition for the research analyst
- CONTEXT describing the domain and audience
- CENTRAL QUESTION
- 4-6 targeted SUB-QUESTIONS derived from your specific uncertainties
- SOURCE GUIDANCE (authoritative sources, date-checking, separate required/recommended/opinion)
- SCOPE boundaries
- OUTPUT format:
- A short H1 document title (fewer than 10 words, no colons or extra statements) — this is the title of the research document, not "Executive Summary"
- "Executive Summary" as an H2 section heading beneath the title
- Tiered findings, trade-off evaluation, glossary, and source list as subsequent sections
- CITATIONS: Do NOT include inline source URLs or citations in the body of the report. Attach all references as a single consolidated list at the END of the report only
- DEPTH level with a source count target of at least 50 authoritative sources
After Generating
Advise the user to run that prompt through Google AI Studio (search grounding enabled), Claude, or their research agent of choice, and to feed the findings back before implementation.