review-orchestrator

Coordinate literature review workflows across search, planning, and writing subagents.

38|3|Updated May 7, 2026
One-click install
npx skills add https://github.com/Chanw-research/claude-code-paper-writing --skill review-orchestrator-chanw-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-orchestrator
Source: https://github.com/Chanw-research/claude-code-paper-writing/tree/main/skills/literature-review/review-orchestrator
Command: npx skills add https://github.com/Chanw-research/claude-code-paper-writing --skill review-orchestrator-chanw-research

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinate long-running literature review workflows across the search, planning, and writing subagents. This skill acts as the controller for three subagents: openalex-ajg-insights for collection, management-review-planner for framework design, and management-review-writer for drafting, keeping the workflow file-based and transparent.

Core Features & Use Cases

  • Orchestrates multi-agent literature workflows by routing tasks to the appropriate subagent and maintaining a unified plan.
  • Enforces explicit user approval before drafting and archives approved plans with timestamped history.
  • Preserves framework when new literature is added and supports auditable workflow governance across plan, draft, and review stages.

Quick Start

Provide a draft review plan and obtain explicit user approval before drafting.

Frequently Asked Questions about review-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate a multi-agent literature review workflow?

A multi-agent literature review is coordinated by a central controller that routes tasks to search, planning, and writing subagents while maintaining a file-based governance workflow. This orchestrator manages task routing and preserves the approved framework.

How do I enforce plan approval before drafting a literature review?

To enforce plan approval before drafting, the workflow requires explicit user approval of the review framework and archives timestamped snapshots of approved plans under a dedicated history directory. Drafting only begins after this gatekeeping step is passed.

What is the best way to maintain audit history for literature review plans?

The best way to maintain audit history for literature reviews is to archive timestamped snapshots of approved plans within a dedicated history directory. This preserves the file-based governance and ensures an auditable trail across plan, draft, and review stages.

Can I preserve my approved review framework when adding new literature?

Yes, you can preserve your approved review framework when adding new literature. The orchestration workflow ensures the existing plan is maintained and routes new collection tasks to the search subagent without disrupting the approved drafting structure.

Does multi-agent literature orchestration work with OpenAlex for reference management?

Yes, multi-agent literature orchestration works with OpenAlex by routing collection and reference management tasks to a dedicated search subagent. This integration supports the gathering of literature needed for the planning and writing phases.

What are the limitations of file-based workflow governance for literature reviews?

A limitation of file-based workflow governance for literature reviews is its reliance on explicit plan approval and manual gatekeeping before drafting. Users must manage archived plan snapshots and ensure the controller correctly routes tasks across all three subagents.