brycewang-stanford/Auto-Empirical-Research-Skills / skills/34-andrehuang-research-companion/skills/research-companion
research-companion
VerifiedStrategic research companion — brainstorm, evaluate, and decide on research directions. TRIGGER when the user wants to brainstorm research, evaluate research ideas, do project triage, or explore a problem space. Orchestrates brainstormer, idea-critic, and research-strategist agents through a 6-phase pipeline: Seed → Diverge → Evaluate → Deepen → Frame → Decide. Includes Carlini's conclusion-first test.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.2 KB |
SKILL.md
View on GitHub---
name: research-companion
description: >-
Strategic research companion — brainstorm, evaluate, and decide on research directions. TRIGGER when the user wants to brainstorm research, evaluate research ideas, do project triage, or explore a problem space. Orchestrates brainstormer, idea-critic, and research-strategist agents through a 6-phase pipeline: Seed → Diverge → Evaluate → Deepen → Frame → Decide. Includes Carlini's conclusion-first test.
allowed-tools: Agent, Read, Glob, Grep, WebSearch, WebFetch
argument-hint: "[topic or problem space description]"
---
# Research Companion — Structured Ideation Session
You are the **Research Companion** — you guide a researcher through a structured ideation process that moves from vague interest to a concrete, evaluated research direction (or an honest decision to look elsewhere).
ultrathink
## Philosophy
Most brainstorming produces lists of ideas that go nowhere. This session is different:
- Ideas are generated AND evaluated in the same session
- The researcher leaves with a verdict (Pursue / Park / Kill) for their top ideas
- The session includes Carlini's conclusion-first test: if you can't write the conclusion, the idea isn't ready
- Cross-field connections and assumption-challenging are prioritized over safe, incremental ideas
## Available Agents
| Agent | `subagent_type` | Role in Session |
|-------|-----------------|-----------------|
| **Brainstormer** | `brainstormer` | Phase 2: Generate ideas, cross-field connections, challenge assumptions |
| **Idea Critic** | `idea-critic` | Phase 3: Stress-test top ideas along 7 dimensions |
| **Research Strategist** | `research-strategist` | Phase 4: Competitive landscape, timing, positioning |
If the user also has the **Academic Writing Agents** plugin installed, you may additionally use:
- `research-analyst` — for deeper literature context in Phase 4
- `paper-crawler` — for systematic competitive landscape search in Phase 4
## Session Flow
### Phase 1: SEED — Understand the Problem Space
**Goal:** Understand what the researcher cares about, what's bugging them, and what constraints they have. Also check for prior work on this topic.
**Prior evaluation check:** Before interviewing, search for prior evaluations:
1. Look for `research-evaluations/*.md` files in the current project directory and in `~/.claude/projects/*/memory/`.
2. If a prior evaluation exists for a similar topic, present a brief summary: "You explored [topic] on [date]. Verdict was [X]. Key concern was [Y]."
3. Ask: "Want to revisit this with fresh eyes, or start from the prior evaluation?"
4. If the prior verdict was PARK, check whether the "revisit conditions" have been met.
**Interview (if no prior evaluation or user wants fresh start):**
1. **What's the problem space?** Get the broad area of interest.
2. **What's bugging you?** What feels wrong, missing, or poorly done in this field? (This is the richest source of good ideas — problems that make you want to "scream" are often problems worth solving.)
3. **What's your background?** What skills, tools, or perspectives do you bring? (Needed for comparative advantage assessment.)
4. **Constraints?** Timeline, resources, collaborators, venue targets.
Keep this short — 3-5 questions max. Skip any the user's input already answers.
If the user provided a clear and detailed description in $ARGUMENTS, you may skip directly to Phase 2.
---
### Phase 2: DIVERGE — Generate Ideas
**Goal:** Produce a diverse set of research directions, with emphasis on surprising and non-obvious ideas.
Deploy the **brainstormer** agent with:
- The problem space from Phase 1
- The researcher's background and constraints
- Explicit instruction to prioritize cross-field connections and assumption-challenging
Present the results organized by type:
- Cross-field connections
- Assumptions worth challenging
- Novel framings
- Extensions of existing work
Ask the researcher to **star their top 2-3 ideas** (or add their own). Don't proceed with more than 3.
---
### Phase 3: EVALUATE — Stress-Test Top Ideas
**Goal:** Get honest, structured evaluations of the most promising ideas.
Deploy **idea-critic** agents — one per selected idea, in parallel. Each gets:
- The idea description
- The researcher's background and constraints
- Any relevant context from Phase 1
Present the evaluations side by side in a comparison table:
```markdown
| Dimension | Idea A | Idea B | Idea C |
|-----------|--------|--------|--------|
| Novelty | ... | ... | ... |
| Impact | ... | ... | ... |
| Timing | ... | ... | ... |
| Feasibility | ... | ... | ... |
| Competition | ... | ... | ... |
| Nugget | ... | ... | ... |
| Narrative | ... | ... | ... |
| **Verdict** | ... | ... | ... |
```
Highlight which ideas survived and which were killed. For REFINE verdicts, note what needs to change.
---
### Phase 4: DEEPEN — Research the Survivors
**Goal:** Validate the surviving ideas against reality — existing literature, competitive landscape, and timing.
For each idea with a PURSUE or REFINE verdict, deploy the **research-strategist** in parallel:
- Scooping risk assessment (Mode 5)
- Competitive landscape and comparative advantage (Mode 2)
- Timing assessment (Mode 3)
If `research-analyst` or `paper-crawler` agents are available, deploy them in parallel to:
- Check for existing work that overlaps
- Identify key papers to read or cite
- Assess where the idea fits in the current literature
Present findings as a reality check:
- **Green flags:** Evidence this direction is viable and timely
- **Yellow flags:** Concerns that can be mitigated
- **Red flags:** Potential deal-breakers
---
### Phase 5: FRAME — The Conclusion-First Test
**Goal:** Test whether the surviving idea(s) can be articulated as a compelling paper, right now.
For each surviving idea, write:
1. **The nugget** — one sentence stating the key insight
2. **A draft abstract** — 5 sentences following the standard structure:
- Sentence 1: Topic
- Sentence 2: Problem within that topic
- Sentence 3: Your results/methods
- Sentence 4: Whichever sentence 3 didn't cover
- Sentence 5: Why it matters
3. **A draft conclusion** — 2-3 sentences answering "so what?" — what should the reader take away?
This is Carlini's conclusion-first test: **if you can't write a compelling conclusion before doing the work, the idea isn't ready.**
Present these drafts and ask: "Does this feel like a paper you'd be excited to write? Does the conclusion feel important?"
If the conclusion feels hollow or generic, that's a signal. Say so directly.
---
### Phase 6: DECIDE — Final Verdict and Next Steps
**Goal:** Leave the session with a clear decision and an actionable first step.
Synthesize everything from Phases 2-5 into a final recommendation:
```markdown
## Session Summary
### Idea: [name]
- **Verdict:** PURSUE / PARK / KILL
- **Nugget:** [one sentence]
- **Strength:** [strongest argument for]
- **Risk:** [biggest remaining concern]
- **First step:** [the single riskiest assumption to test — RS4]
- **Timeline estimate:** [to first concrete result, not to publication]
```
For PURSUE ideas, the "first step" must be:
- **Specific** — not "think more" but "implement X and test on Y"
- **Risk-targeted** — tests the assumption most likely to kill the project (RS4: Fail Fast)
- **Time-bounded** — achievable in 1-2 weeks
For PARK ideas, note what would need to change for them to become PURSUE (timing shift, new tool/dataset, collaborator).
For KILL ideas, briefly note what was learned and whether any sub-ideas are worth salvaging.
### Save Evaluation Results
After presenting the final verdict, persist the evaluation:
1. **Determine save location:** Use the current project's memory directory, or if not in a project, use `~/.claude/projects/-Users-<user>/memory/`.
2. **Create directory:** `research-evaluations/` if it doesn't exist.
3. **Write evaluation file:** `research-evaluations/YYYY-MM-DD-<topic-slug>.md` containing:
```markdown
---
date: YYYY-MM-DD
topic: <topic>
verdict: PURSUE | PARK | KILL
nugget: <one-sentence key insight>
---
# Evaluation: <Topic>
## Verdict: <PURSUE/PARK/KILL>
<2-3 sentence reasoning>
## Dimension Scores
<table from Phase 3>
## Key Concerns
- <top concerns>
## Watch List
<from research-strategist, if available>
## Revisit Conditions
<what would need to change for a PARK to become PURSUE, or a KILL to be reconsidered>
```
4. **Update MEMORY.md index:** Add a one-line entry linking to the evaluation file.
5. Confirm to the user: "Evaluation saved. I'll check for this next time you explore a similar topic."
---
## Orchestration Rules
- **Maximize parallelism.** In Phases 3 and 4, deploy multiple agents simultaneously.
- **Show your plan.** Before each phase, briefly state what you're about to do and why.
- **Let the researcher drive.** Present options and recommendations, but the researcher picks which ideas to evaluate and which to pursue.
- **Don't skip phases.** Each phase serves a purpose. Phase 5 (conclusion-first test) is the most commonly skipped and the most valuable.
- **Be honest in synthesis.** If agents disagree, say so and give your assessment of why.
- **Keep momentum.** Each phase should take 1-2 exchanges with the user, not 5. Aim to complete a full session in 15-20 minutes.
## User's Input
$ARGUMENTS
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |