refactor(core): overhaul /research command for executive synthesis

Author: apiad

.gemini/commands/research.toml

@@ -1,26 +1,38 @@
-description = "Conduct structured research through planning, data gathering, and reporting phases."
+description = "Conduct extensible, structured research with iterative report updates and executive-level synthesis."
 
 prompt = """
-You are an expert researcher. Follow this robust 3-phase workflow to conduct exhaustive research on the following topic: {{args}}
+You are an expert researcher. Follow this robust 4-phase workflow to conduct exhaustive research on the following topic: {{args}}
 
-**Phase 1: Planning**
-1. Analyze the topic and break it down into high-level questions.
-   DO NOT ASSUME any premade answers such as specific technologies, methods, or sources. Instead, focus on the core questions that need to be answered to fully understand the topic.
-2. Formulate a comprehensive report structure (sections and subsections).
-3. Create a `research/<topic>/` directory to hold the gathered data.
-4. Present this plan to the user for approval.
+### Phase 1: Planning & Approval
+1. **Analyze Topic:** Identify the core research goal and break it down into a list of high-level research questions.
+2. **Sub-Questions:** For each research question, identify 3-5 specific research points (sub-questions) that must be addressed.
+3. **Approval:** Use `ask_user` to present the list of research questions and sub-questions to the user for approval or modification.
 
-**Phase 2: Data Gathering**
-1. Iteratively invoke the `researcher` subagent for each high-level question or specific topic area.
-2. The `researcher` will search the web, fetch relevant content, and write detailed Markdown summaries (including references) into the `research/<topic>/` folder.
-3. Review the files in `research/<topic>/` to ensure you have sufficient depth and breadth of information.
-4. If gaps exist, invoke the `researcher` again with more specific queries. Do not proceed until you have a critical mass of detailed sources.
+### Phase 2: Report Initialization
+1. **Initialize Directory:** Create a `research/<topic>/` sub-directory for all detailed research assets.
+2. **Create Skeleton:** Create a `research/<report-title>.md` file with the following outline:
+   - **Executive Summary:** (Placeholder: "To be completed after research.")
+   - **Research Questions:** (A section for each approved question, including its sub-points as a list.)
+   - **Conclusions:** (Placeholder: "To be completed after research.")
+   - **Recommendations:** (Placeholder: "To be completed after research.")
 
-**Phase 3: Reporting**
-1. Create a `/research/<report-title>.md` file containing just the section headers and a minimal one-line outline for what goes in each subsection.
-2. Iteratively invoke the `reporter` subagent for *each section or subsection* one step at a time.
-3. Instruct the `reporter` to read the sources in `research/<topic>/*.md` and expand that specific section in the report with full, lengthy, and detailed paragraphs.
-4. Continue this process until the entire report is complete.
+### Phase 3: Iterative Research & Report Update
+For each approved research question:
+1. **Invoke Researcher:** Invoke the `researcher` subagent for the specific research question, asking it to investigate all its sub-points.
+2. **Asset Creation:** The `researcher` will produce detailed Markdown summaries for that specific question into the `research/<topic>/` folder.
+3. **Update Main Report:** After each `researcher` run, update the corresponding section in `research/<report-title>.md` with:
+   - A high-level overview of the findings for that research question.
+   - Explicit links to the corresponding detailed research assets in `research/<topic>/`.
+   - Subsections for deep diving into specific findings.
 
-Do not stop until all phases are complete and the report is fully fleshed out.
+### Phase 4: Synthesis & Finalization
+Once all research questions have been investigated and the sections updated:
+1. **Conclusions:** Synthesize the overall findings into a "Conclusions" section in the main report.
+2. **Executive Summary:** Write a comprehensive, high-level "Executive Summary" at the *beginning* of the report, highlighting the most critical insights.
+3. **Recommendations:** Provide a set of actionable "Recommendations," including:
+   - What to do next.
+   - Potential follow-up research lines.
+4. **Final Suggestion:** Advise the user that the research is complete and they can now use the `/draft` command to turn this executive report into a fully fleshed-out article or white paper.
+
+Do not stop until all phases are complete and the executive report is fully synthesized.
 """