本文へ移動
cccskills
無料GitHub で公開

multi-model-orchestrator

Use when coordinating complex tasks across multiple AI agents with a centralized handoff document for planning, execution tracking, and feedback fusion.

インストール方法を見る

含まれるファイル(11)

  • SKILL.md5.9 KB
  • LICENSE1.0 KB
  • README.md7.8 KB
  • references/add-auth-to-api.yaml13.9 KB
  • references/advanced-sync.md972 B
  • references/best-practices.md1.6 KB
  • references/faq.md1.4 KB
  • references/handoff-structure.md2.1 KB
  • references/quick-start.md3.6 KB
  • references/workflow-patterns.md1.5 KB
  • templates/handoff-template.yaml3.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

multi-model-orchestrator

Decompose. Execute. Synthesize.

A lightweight skill for coordinating work across multiple AI agents (Claude, Opus, Haiku, Codex, or any agent) using a single handoff document as the source of truth.

Why This Skill

Complex work often requires:

  1. High-level planning — breaking down a big goal into concrete subtasks
  2. Parallel execution — different agents handling different task types simultaneously
  3. Feedback synthesis — collecting results and iterating intelligently
  4. Full traceability — understanding who did what, why, and what changed

This skill provides the structure and templates to do this cleanly.

Operating Contract

Direct actions: create or update one handoff document as the source of truth, decompose the goal into executor-ready subtasks, assign explicit dependencies, record execution results, and synthesize feedback into next steps.

Escalate before: starting execution when the goal, constraints, executor choice, writable scope, or done criteria are ambiguous.

Evidence-backed pushback: reject unverified completion claims, vague agent outputs, missing acceptance criteria, or parallel assignments that touch shared writable files without explicit ordering.

Feedback loop: after each execution round, update the handoff with result, evidence, blockers, and next action before assigning follow-up work.

When to Use

✅ Use when:

  • A single-agent conversation would be too long or unfocused
  • You want to parallelize work across multiple specialized agents
  • You need to decompose a vague goal into specific, executor-ready tasks
  • You want to track decisions, changes, and feedback in one place
  • You're exploring multiple approaches simultaneously (A/B/C branches)

❌ Don't use when:

  • The task is simple and one agent can handle it end-to-end
  • You don't need to track who did what
  • Execution is strictly sequential with no parallelization
  • The task is exploratory with no clear structure

Core Concepts

Handoff Document (Handoff)

A YAML file that serves as the single source of truth. It contains:

  • Goal — what are we trying to accomplish?
  • Subtasks — who does what, and what does success look like?
  • Context — code references, prior decisions, constraints
  • Execution Tracking — who executed, what was the result, what blockers?
  • Feedback — iterations, changes, and learnings

Agent Roles

You choose which agents execute which subtasks. Examples:

AgentBest For
Claude (or Fable)Planning, decomposition, architecture review, high-level strategy
OpusComplex reasoning, deep analysis, novel problem-solving
HaikuFast iteration, simple fixes, quick validation
CodexCode generation, refactoring, technical implementation
Claude CodeInteractive development, running code, verification

The Loop

1. Define Goal
    ↓
2. Fable/Claude decomposes into Handoff subtasks
    ↓
3. You assign subtasks to agents
    ↓
4. Agents execute in parallel or sequence
    ↓
5. You record results in Handoff
    ↓
6. Review, iterate, or complete

Quick Start

The full five-step walkthrough with copy-paste templates lives in references/quick-start.md. Summary:

  1. Create handoff — copy templates/handoff-template.yaml to .claude/handoffs/my-task.yaml.
  2. Decompose — ask Fable/Claude to break the goal into 3-5 subtasks; paste into subtasks.
  3. Execute — give each subtask's input to its assigned executor.
  4. Record — append the result to execution.rounds.
  5. Iterate or complete — update metadata.status toward complete.

Field-by-field reference: references/handoff-structure.md.

Complete Example

See references/add-auth-to-api.yaml for a real-world multi-agent execution walkthrough.

Using with Claude Code

  1. Save your handoff to .claude/handoffs/task.yaml
  2. Run: cat .claude/handoffs/task.yaml to load it in conversation
  3. Ask Claude to execute a subtask
  4. When done, update the handoff manually or using a script

For automation, see references/advanced-sync.md.

Using with Codex

Codex does not have handoff-specific subcommands. Use codex exec with a focused prompt that names the handoff file and the exact subtask:

codex exec "Read .claude/handoffs/task.yaml. Execute subtask task-1 only. Return the result, blockers, files changed, and verification evidence."

For decomposition:

codex exec "Read .claude/handoffs/task.yaml. Propose 3-5 YAML subtasks using goal.summary, goal.context, and goal.acceptance_criteria. Do not edit files."

Resources


Status: Production ready · License: MIT

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Audit and organize AI coding-agent instructions, including AGENTS.md, CLAUDE.md, skills, and agent definitions. Use when the user asks to diagnose conflicting instructions, excessive approval pauses, broad skill triggers, duplicate guidance, or broken instruction references, or to clean up that instruction set. Ordinary code review, Markdown editing, or application debugging alone does not trigger this workflow. Inspection stays read-only; apply changes when authorized.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2872026年10月8日 更新

Generate or update repository-specific AGENTS.md instruction files from real repo evidence. Use when asked to create, design, scaffold, split, or improve root or scoped AGENTS.md files for Codex/Claude/agent workflows, especially when a repo needs directory-specific rules, validation commands, generated-file boundaries, or a short agent onboarding router.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2872026年10月8日 更新

REST/GraphQL/gRPC API design best practices. Use when designing APIs, defining contracts, handling versioning. Covers OpenAPI 3.2, GraphQL Federation, gRPC streaming.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2872026年10月8日 更新

Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2872026年10月8日 更新

End-to-end app feature inventory and user-story testing workflow with a canonical tracker. Use when the user asks to audit every feature, derive expected behavior from code, test user journeys, or explicitly fix and retest documented UX or logistical defects.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2872026年10月8日 更新

Design architecture foundations before implementation. Use when asked to design or refactor architecture, choose Rust/Go crate, package, module, runtime, workflow, or service boundaries, compare mature project architecture, prevent stacked one-off PRs, audit migration debt in existing repos, or produce a spec before coding.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2872026年10月8日 更新

majiayu000 のスキルをすべて見る

このスキルの問題を報告する