multi-model-orchestrator

Coordinate multi-agent workflows using a centralized handoff document.

258|26|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/majiayu000/spellbook --skill multi-model-orchestrator-majiayu000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-model-orchestrator
Source: https://github.com/majiayu000/spellbook/tree/main/skills/multi-model-orchestrator
Command: npx skills add https://github.com/majiayu000/spellbook --skill multi-model-orchestrator-majiayu000

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinating complex tasks across multiple AI agents requires a single source of truth, structured handoffs, and end-to-end traceability. This skill provides a lightweight framework to decompose goals, assign subtasks with explicit dependencies, track execution, and synthesize outcomes into actionable next steps.

Core Features & Use Cases

  • Single handoff document as the source of truth for cross-agent workflows (Claude, Opus, Haiku, Codex, Claude Code).
  • Parallel decomposition and execution with explicit dependencies to maximize throughput.
  • Execution tracking and evidence-based synthesis to capture decisions, blockers, and learnings.
  • Templates and references to accelerate multi-agent projects (handoff-template.yaml and references/ examples).
  • Real-world workflows demonstrated by examples like add-auth-to-api in the references.

Quick Start

Copy the handoff template to .claude/handoffs/my-task.yaml, fill in your goal and subtasks, and prompt Fable/Claude to decompose and execute.

Frequently Asked Questions about multi-model-orchestrator

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

FAQPage Schema
How do I coordinate complex tasks across multiple AI agents like Claude, Opus, and Haiku?

Multi-agent orchestration coordinates complex tasks across multiple AI agents like Claude, Opus, and Haiku using a centralized handoff document. This single source of truth manages goal decomposition, parallel execution, and end-to-end traceability across cross-agent workflows.

What is the best way to track execution and dependencies in a multi-agent workflow?

Execution tracking in a multi-agent workflow uses a structured handoff schema to capture decisions, blockers, and learnings. It assigns subtasks with explicit dependencies and synthesizes outcomes into actionable next steps using evidence-based feedback fusion.

Can I use a single handoff document for parallel task decomposition across Claude Code and Codex?

Yes, a single handoff document supports parallel task decomposition across Claude Code and Codex. It serves as the centralized source of truth, allowing you to maximize throughput by executing subtasks in parallel while maintaining end-to-end traceability.

How do I start a multi-agent project using a handoff template?

To start a multi-agent project, copy the handoff-template.yaml file to your local `.claude/handoffs/` directory. Fill in your project goal and subtasks, then prompt your AI agent to decompose and execute the structured workflow.

What schema structure is required for a centralized agent handoff document?

A centralized agent handoff document requires a structured schema containing metadata, the primary goal, subtasks, execution rounds, and a final synthesis. This format ensures structured handoffs and end-to-end traceability across cross-agent workflows.

When should I not use a centralized handoff document for AI agent coordination?

A centralized handoff document is not suited for single-agent tasks or workflows lacking complex cross-agent dependencies. It is designed specifically for parallel decomposition, execution tracking, and feedback fusion across multiple AI agents.