orchestrator-patterns

Manage stateful multi-agent pipelines with crash-safe orchestration helpers.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/leonardoacosta/central-claude --skill orchestrator-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator-patterns
Source: https://github.com/leonardoacosta/central-claude/tree/main/skills/orchestrator-patterns
Command: npx skills add https://github.com/leonardoacosta/central-claude --skill orchestrator-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, date, git, uuidgen, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Orchestrating many parallel AI agents and preserving progress across crashes is complex and error-prone; this Skill provides tested patterns and helpers to manage state, resume partial runs, and collect progressive results so long-running pipelines complete reliably.

Core Features & Use Cases

  • State management & crash resume: Canonical state file convention, atomic writes, phase- and node-level status, and resume detection by git SHA.
  • Agent dispatch & fan-out/fan-in: Helpers and reference patterns to start nodes before dispatch, spawn parallel agents, and update node-level outcomes without re-running completed work.
  • Progressive collection & synthesis: Stream incremental results as agent groups finish, deduplicate across batches, and run downstream synthesis early.
  • Telemetry, timing & notifications: Unified telemetry logging with rotation, per-phase timing reports, pipeline UUIDs, and optional TTS notifications for pipeline events.
  • Use cases: Implement robust commands like audit-all, apply-waves, and domain audit tasks that require parallel agents, fault tolerance, and end-to-end timing and logging.

Quick Start

Source the orchestrator helpers, derive a state file for your command, and run orch_check_resume to initialize or resume the pipeline.

Frequently Asked Questions about orchestrator-patterns

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

FAQPage Schema
How do I resume a parallel agent pipeline after a crash without re-running completed work?

Crash resume for parallel agent pipelines uses a canonical state file with git SHA node-level resume detection, skipping completed nodes and re-dispatching only failed or interrupted agents.

What is the best way to manage state persistence for multi-agent fan-out and fan-in operations?

State persistence for multi-agent fan-out is managed through atomic state writes, ensuring concurrent agent outcomes are recorded safely without corruption during progressive collection and synthesis.

Do I need jq and git to run crash-resilient multi-agent orchestration helpers?

Yes, crash-resilient multi-agent orchestration requires jq, git, date, and uuidgen, relying on standard GNU coreutils to handle state files, resume detection, and unified telemetry logging.

How does telemetry and timing work for stateful pipelines with parallel agents?

Telemetry for stateful pipelines provides unified logging with rotation, per-phase timing reports, and unique pipeline UUIDs, capturing dispatch timing and node-level outcomes across agent groups.

Can I stream incremental results from parallel agents as batches finish?

Progressive collection streams incremental results as agent groups finish, deduplicating across batches to enable downstream synthesis early without waiting for all nodes to complete.

When should I not use bash orchestration patterns for fault-tolerant agent dispatch?

Bash orchestration patterns for fault-tolerant agent dispatch may not suit pipelines requiring complex inter-agent messaging beyond state files, or environments lacking standard GNU coreutils and jq.