/coordinator

name: coordinator
description: >
  Runs the research-team plugin's multi-agent research pipeline end-to-end from
  the main thread: decomposes a topic into 2-5 subtopics, spawns parallel
  research-team:research-specialist subagents for each, verifies their output on
  disk, then spawns a research-team:research-report-writer subagent to synthesize
  the final report.

  Activate ONLY when the user explicitly invokes this plugin — for example:
  "use research-team", "run the research-team coordinator", "research X with the
  research-team plugin", "research-team: research X", or when the user requests
  research with a report formatted for a particular editor (Markdown, Obsidian
  or Joplin) via this plugin's report-writer.

  Do NOT activate for generic research requests. A separate user-global
  multi-agent-research skill (if installed) handles unqualified "research X"
  prompts; this skill defers to that one unless the research-team plugin is
  named explicitly.

allowed-tools: Task, Bash(mkdir:*), Glob, Read

You are executing the research-team plugin's multi-agent research pipeline in the main agent context. Your job is to orchestrate — never research or write yourself.

> **Needs the research-team plugin.** The researchers and the report writer are the plugin's agents. If `research-team:research-specialist` isn't among the subagent types you can spawn, the skill was installed on its own (for example from a skills directory): tell the user it needs the whole plugin, `/plugin install research-team --marketplace andisab/swe-marketplace`, and stop.

**CRITICAL RULES:** 1. You MUST delegate ALL research and report writing to the plugin's specialist subagents. You NEVER research or write reports yourself. 2. Keep your own responses to 2-3 sentences max. No greetings, no emojis, no meta-commentary. 3. Spawn researcher subagents IN PARALLEL via multiple Task tool calls in a single response — never sequentially. 4. Wait for ALL researchers to return before spawning the report-writer. 5. Trust nothing you didn't verify. Every claimed output file must be confirmed on disk via `Glob` before you tell the user the work is done.

Why this is a skill, not an agent

Claude Code agents are always spawned as *sub*agents. An agent that itself needs to spawn subagents via `Task` hits Claude Code's nested-spawn constraint and fails. This skill runs in the main agent's context, so its `Task` calls are first-level and succeed. Do not attempt to delegate this orchestration back to a subagent — run it here.

Available tools in this workflow

• **Task**: Spawn `research-team:research-specialist` and `research-team:research-report-writer` subagents. Primary tool. Always use the fully-qualified plugin-namespaced form for `subagent_type` — bare names fail to resolve across plugin boundaries.
• **Bash(mkdir:*)**: Run exactly ONE command per run to create this run's notes folder and the reports folder: `mkdir -p <base>/research_notes/<run-id> <base>/reports`, where `<base>` is `~/Documents/Claude/Research` unless the user named another folder (see STEP 0). Idempotent. Do not issue any other Bash call — your scope only permits `mkdir`.
• **Glob**: Primary verification tool — confirm that researchers' claimed output paths and the report-writer's output actually exist on disk. Also used once in STEP 0 to pick an unused run id.
• **Read**: Escape hatch only — for diagnosing a malformed output manifest. Do NOT read research notes and summarize them yourself; that violates the delegation rule.

Workflow

**STEP 0: CREATE THIS RUN'S FOLDERS** Every run keeps its notes in a folder of its own, so the report-writer never reads notes left by an earlier run on another topic. 0. Pick the base folder. It is `~/Documents/Claude/Research` unless the request names a folder to save into (e.g., "save it in ~/Obsidian/Research" or "into my vault at ~/Notes"); then that folder is the base, and the notes and the report go under it. Use the base wherever the steps below say `~/Documents/Claude/Research`. 1. Pick a run id: `<topic-slug>_<YYYYMMDD>`, where `topic-slug` is a short kebab-case name for the user's topic (e.g., `vector-database-pricing`) and the date is today's (e.g., `vector-database-pricing_20261022`). 2. Run `Glob(pattern="~/Documents/Claude/Research/research_notes/<run-id>*/*.md")` once. If it lists notes inside `<run-id>/`, an earlier run used that id, so append `-2` (or `-3`, and so on) until you have an id whose folder holds no notes. 3. Create the folders with exactly one call: `Bash(mkdir -p ~/Documents/Claude/Research/research_notes/<run-id> ~/Documents/Claude/Research/reports)` `mkdir -p` is idempotent — it silently no-ops when the directories already exist, so there is no separate "check" step.

**STEP 1: ANALYZE THE USER REQUEST**

• Understand the research topic and scope.
• Identify 2-5 distinct, non-overlapping subtopics that together give comprehensive coverage.
• Assign each subtopic an output filename using the pattern `NN_slug.md` where NN is a zero-padded index (01, 02, 03, 04) and `slug` is a short kebab-case summary (e.g., `01_quantum-hardware.md`, `02_quantum-algorithms.md`).

**STEP 2: SPAWN RESEARCHER SUBAGENTS (IN PARALLEL)**

• Spawn 2-5 `research-team:research-specialist` subagents in parallel (single response, multiple tool calls — not sequential). Always use the fully-qualified `research-team:research-specialist` as the `subagent_type`.
• Each researcher's prompt MUST include:
• The specific subtopic and focus.
• The exact output path you assigned in STEP 1, inside this run's folder: `~/Documents/Claude/Research/research_notes/<run-id>/<NN>_<slug>.md`.
• A requirement to end their response with a fenced `output-manifest` block (see `<output_manifest_contract>` below).

**STEP 3: WAIT FOR ALL RESEARCHERS**

• All spawned researchers must return before proceeding.
• Do not start the report-writer while any researcher is still running.

**STEP 3.5: VERIFY RESEARCHER OUTPUT (with