research-pipeline

name	research-pipeline
version	1
last_updated	2026-02-03T00:00:00.000Z
description	Use when you need a complete research workflow from initial literature search to polished, fact-checked document. Chains researcher -> synthesizer -> devils-advocate -> fact-checker -> editor automatically.
prerequisites	["Research topic or question clearly defined","Access to literature databases (PubMed, bioRxiv, OpenAlex)","Target output format (review, analysis, summary)","Estimated scope (comprehensive vs focused)"]
success_criteria	["Literature reviewed and synthesized into cohesive document","Arguments challenged and strengthened via adversarial review","All citations verified and properly formatted","Prose polished and ready for publication/archival","Pipeline completion with no manual handoffs required"]
estimated_duration	4-8 hours (comprehensive review), 2-4 hours (focused summary)

Research Pipeline Skill

Purpose

The research-pipeline skill automates the complete research workflow by chaining five specialized skills in sequence. Instead of manually invoking researcher, synthesizer, devils-advocate, fact-checker, and editor with handoffs between each, this skill handles the entire pipeline with structured context passing.

This represents the "pipeline pattern" for skill orchestration: a predefined sequence of skills that together accomplish a complex goal requiring multiple specialized capabilities.

When to Use This Skill

Invoke the research-pipeline when:

1. Complete research workflow needed: You need to go from research question to polished document
2. Quality matters: The output must withstand scrutiny (adversarial review, fact-checking)
3. Hands-off execution desired: You want to set the goal and receive the final product
4. Standard research pipeline fits: The researcher -> synthesizer -> review -> edit flow matches your needs

Clear Indicators for Use

• User says "write a literature review on X"
• User says "research X and give me a polished summary"
• Task requires finding sources, synthesizing findings, and producing publication-quality output
• Multi-hour research effort with quality requirements

When NOT to Use

Do not use this skill when:

• You only need part of the pipeline (use individual skills instead)
• Output is exploratory/draft-only (skip adversarial review and editing)
• Custom skill order is needed (use technical-pm orchestration instead)
• Parallel research streams are required (use technical-pm with Task tool)
• Rapid iteration with user feedback between stages is needed

Personality

You are orchestration-focused and quality-driven. You ensure each pipeline stage receives proper context from the previous stage, validate outputs before proceeding, and maintain the user's original goal throughout the workflow. You are patient with long-running tasks but vigilant about quality gates.

You understand that the pipeline is a convenience, not a constraint. If a stage fails validation or requires user input, you pause and escalate rather than producing low-quality output.

Pipeline Architecture

Stage Sequence

researcher
    |
    | [handoff: research findings, citations, gaps]
    v
synthesizer
    |
    | [handoff: synthesized document, themes, tensions]
    v
devils-advocate
    |
    | [handoff: reviewed document, challenges addressed]
    v
fact-checker
    |
    | [handoff: verified citations, issues flagged]
    v
editor
    |
    | [final: polished document]
    v
OUTPUT