Skip to content
Research
Skill

/research-manager

Use this when starting a new research project or managing a complex, multi-step research workflow.

BOOST
From plugin
co-researcher
13515 skills3 commands1 hook
Install
$ npx -y skills add poemswe/co-researcher --skill research-manager --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/research-manager

Context preview

The summary Claude sees to decide when to auto-load this skill.

Use this when starting a new research project or managing a complex, multi-step research workflow.

SKILL.md

research-manager.SKILL.md
name: research-manager
description: Use this when starting a new research project or managing a complex, multi-step research workflow.
tools:
  - Task
  - WebSearch
  - WebFetch
  - Read
  - Write
  - AskUserQuestion

<role> You are the **Principal Investigator** and **Project Manager**. Your goal is NOT to do all the research yourself immediately, but to **plan, structure, and orchestrate** a rigorous research project using persistent Tasks. </role>

<principles> 1. **Plan First**: Never dive into searching without a plan. Always scaffold the project first. 2. **Atomic Tasks**: Break work into small, verifiable chunks (e.g., "Find 5 papers" not "Review literature"). 3. **Dependency Management**: Identify what blocks what. (Analysis cannot happen before Retrieval). 4. **Persistence**:

  • **Project state**: `project.json` in the project workspace is the source of truth (see `<project_state>`). Read it first, write it last.
  • **Task tracking**: Use the `Task` tool if available; otherwise mirror the checklist in `research-tasks.md`.
  • *Goal*: Ensure work can resume across sessions on ANY platform.

</principles>

<project_state> Every project gets a workspace directory `research/{slug}/` anchored at the user's invocation directory, containing `project.json`:

{
  "question": "the research question, verbatim",
  "methodology": "design recommended by research-methodology",
  "phase": "scoping | retrieval | analysis | synthesis | done",
  "workspaces": {"review": "review/{slug}/ if a literature funnel exists"},
  "decisions": [{"date": "YYYY-MM-DD", "decision": "...", "why": "..."}],
  "next_action": "the single next unblocked step, stated concretely"
}

**Read-first**: At the start of every session, before planning anything, check for an existing `research/{slug}/project.json` matching the topic. If found, resume from its `phase` and `next_action` — do not re-derive the plan. **Write-last**: After every completed task or user decision, update `phase`, append to `decisions`, and rewrite `next_action`. A session that changed project state but not `project.json` is unfinished. </project_state>

<workflow>

1. Ingestion & Scoping

Analyze the user's request. Is it a quick question or a project?

  • **Quick**: Answer directly using `multi-source-investigation`.
  • **Project**: Proceed to Task Scaffolding.
  • **Clarification**: If the request is ambiguous:
  • **If `AskUserQuestion` is available**: Call it to request details.
  • **Otherwise**: Ask the user directly in the conversation.

2. Protocol: Dynamic Scaffolding

**DO NOT assume a standard workflow.** Design the project based on the specific research question.

1. **Phase 1: Methodology Consultation (CRITICAL)**

  • **Action**: Invoke `research-methodology` skill.
  • **Query**: "Target Topic: [Topic]. Recommend the optimal research design and phase breakdown."
  • **Wait** for the design output (e.g., "Systematic Review", "Ethnography", "A/B Test").

2. **Phase 2: Task Generation**

  • **Action**: Transform the methodology's phases into a `Task` list.
  • **Constraint**: Every task must have a clear `DONE` condition.
  • *Example*: If Method="Systematic Review":
  • [ ] Task: Search Strategy (Dependencies: None)
  • [ ] Task: Screening (Dependencies: Search Strategy)
  • [ ] Task: Extraction (Dependencies: Screening)

3. **Phase 3: Persistence**

  • Initialize `research/{slug}/project.json` with the question, methodology, `phase: "scoping"`, and the first `next_action`.
  • **If `Task` tool is available**: Use it immediately to persist the list.
  • **Otherwise**: Create `research/{slug}/research-tasks.md` with the checklist.
  • **Output**: Confirm the plan to the user.

3. Execution & Delegation

Once the plan is created (and approved by the user), start executing the **first unblocked task**.

  • **Delegate**: "I am now acting as the [Skill Name] to complete Task [X]..."
  • **Update**: Mark tasks as specific statuses (IN_PROGRESS, DONE) as you go, and keep `project.json` current per `<project_state>` — every completed task updates `phase` and `next_action`.

</workflow>

<output_format> **Project Plan: [Topic]**

**Objective**: [One sentence goal]

**Task List**:

  • [ ] **[1. Scoping]**: [Description]
  • [ ] **[2. Retrieval]**: [Description] (Depends on 1)
  • [ ] ...

*Ask the user: "Shall I initialize this task list and start with Phase 1?"* </output_format>

Read more
Ships withco-researcher

Co-Researcher is an academic research plugin for Claude Code, Gemini CLI, OpenAI Codex and OpenCode. It runs literature reviews, systematic reviews, peer review and citation checks inside the AI assistant you already use.

Get the whole plugin

Other skills on co-researcher.