orchestrate

Monitor Claude worker agents and coordinate implement, review, and merge stages.

5|1|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/ncukondo/reference-manager --skill orchestrate-ncukondo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrate
Source: https://github.com/ncukondo/reference-manager/tree/main/.claude/skills/orchestrate
Command: npx skills add https://github.com/ncukondo/reference-manager --skill orchestrate-ncukondo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates monitoring and state-driven transitions of Claude worker agents, reducing manual coordination and ensuring consistent progression through the implement, review, and merge lifecycle.

Core Features & Use Cases

  • Detects agent state changes and logs event files to /tmp/claude-orchestrator/events/.
  • Surfaces concise status updates in the main pane and exposes commands to inspect current orchestration state.
  • Delegates action decisions to the main agent rather than performing kill/spawn/merge/fix actions, enabling predictable workflow control. Use cases include coordinating workers spawned with /implement and maintaining alignment across implement, review, and merge stages.

Quick Start

Start the orchestrator with ./scripts/orchestrate.sh to run in the foreground, or with ./scripts/orchestrate.sh --background after spawning workers to run autonomously.

Frequently Asked Questions about orchestrate

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

FAQPage Schema
How do I automate monitoring and state-driven transitions for Claude worker agents?

Automate monitoring and state-driven transitions for Claude worker agents by running an orchestrator that detects agent state changes and logs event files to coordinate progress across implement, review, and merge stages.

Can I run worker orchestration in the background after spawning workers?

You can run worker orchestration in the background by executing the orchestration script with the --background flag after spawning workers with the implement command, allowing it to operate autonomously.

What is the best way to coordinate multiple Claude agents across implement, review, and merge stages?

The best way to coordinate multiple Claude agents across implement, review, and merge stages is to use an orchestrator that reads agent state changes and surfaces concise status updates in the main pane.

Does the orchestrator automatically kill, spawn, or merge Claude worker agents?

The orchestrator does not automatically kill, spawn, merge, or fix workers; it delegates action decisions to the main agent to ensure predictable workflow control and consistent progression.

How do I inspect the current orchestration state of my worker agents?

Inspect the current orchestration state of your worker agents by using exposed commands to view concise status updates and reading event files logged to the temporary orchestrator events directory.

Why should I use state-driven orchestration instead of manually coordinating worker agents?

State-driven orchestration reduces manual coordination by automatically detecting agent state changes and logging event files, ensuring consistent progression through the implement, review, and merge lifecycle.