/agent-orchestration
AI DevKit · Supervise multi-agent workflows over repeated passes: poll progress, unblock waiting agents, coordinate dependencies, relay outputs, resolve conflicts, and verify completion. Use only for ongoing multi-agent coordination, not one-off list/detail/send/start/kill
$ npx -y skills add codeaholicguy/ai-devkit --skill agent-orchestration --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/agent-orchestration
Context preview
The summary Claude sees to decide when to auto-load this skill.
AI DevKit · Supervise multi-agent workflows over repeated passes: poll progress, unblock waiting agents, coordinate dependencies, relay outputs, resolve conflicts, and verify completion. Use only for ongoing multi-agent coordination, not one-off list/detail/send/start/kill
SKILL.md
agent-orchestration.SKILL.mdname: agent-orchestration
description: "AI DevKit · Supervise multi-agent workflows over repeated passes: poll progress, unblock waiting agents, coordinate dependencies, relay outputs, resolve conflicts, and verify completion. Use only for ongoing multi-agent coordination, not one-off list/detail/send/start/kill actions."
Agent Orchestration
Use only for multi-agent supervision: coordinating dependencies, polling progress, unblocking waiting agents, relaying outputs, resolving conflicts, and verifying completion across agents. For one-off list/detail/send/start/kill work, use `$agent-management` or `$agent-communication`.
Use `$agent-management` for safe agent selection and lifecycle actions. Use `$agent-communication` for list/detail/send mechanics. Use `$verify` before accepting any agent's completion claim.
Rules
- Own the loop until assigned work is complete, blocked, or stopped.
- Run `agent list --json` before each pass; never assume names/statuses.
- Inspect waiting, idle, unknown, missing, or stale agents before acting.
- Send self-contained instructions and avoid duplicate follow-ups.
- Sequence agents that touch the same files; relay only relevant upstream output.
- Escalate only for repeated failures, unresolved conflicts, product/business decisions, or destructive/shared/production/security-sensitive actions.
Loop
If the goal or agent ownership is unclear, run one scan/detail pass. Ask the user once only if context is still insufficient.
1. Scan agents. 2. Assess agents needing attention with `detail --tail 10`. 3. Act: approve, clarify, correct, delegate, relay, verify, or escalate. 4. Report one brief status line. 5. Sleep 10-60s and repeat.
Completion
Finish when all assigned work is verified, blocked with a clear reason, or stopped by the user. Summarize per-agent outcomes, verification, unresolved issues, and next step.
Read more
name: agent-orchestration description: "AI DevKit · Supervise multi-agent workflows over repeated passes: poll progress, unblock waiting agents, coordinate dependencies, relay outputs, resolve conflicts, and verify completion. Use only for ongoing multi-agent coordination, not one-off list/detail/send/start/kill actions."
Agent Orchestration
Use only for multi-agent supervision: coordinating dependencies, polling progress, unblocking waiting agents, relaying outputs, resolving conflicts, and verifying completion across agents. For one-off list/detail/send/start/kill work, use `$agent-management` or `$agent-communication`.
Use `$agent-management` for safe agent selection and lifecycle actions. Use `$agent-communication` for list/detail/send mechanics. Use `$verify` before accepting any agent's completion claim.
Rules
- Own the loop until assigned work is complete, blocked, or stopped.
- Run `agent list --json` before each pass; never assume names/statuses.
- Inspect waiting, idle, unknown, missing, or stale agents before acting.
- Send self-contained instructions and avoid duplicate follow-ups.
- Sequence agents that touch the same files; relay only relevant upstream output.
- Escalate only for repeated failures, unresolved conflicts, product/business decisions, or destructive/shared/production/security-sensitive actions.
Loop
If the goal or agent ownership is unclear, run one scan/detail pass. Ask the user once only if context is still insufficient.
1. Scan agents. 2. Assess agents needing attention with `detail --tail 10`. 3. Act: approve, clarify, correct, delegate, relay, verify, or escalate. 4. Report one brief status line. 5. Sleep 10-60s and repeat.
Completion
Finish when all assigned work is verified, blocked with a clear reason, or stopped by the user. Summarize per-agent outcomes, verification, unresolved issues, and next step.
The control plane for AI coding agents. AI DevKit gives Claude Code, Codex CLI, Gemini CLI, opencode, Pi, Cursor, GitHub Copilot, Devin, and other coding agents one local-first operating layer: one config, one console, local memory retrieval, cross-agent
Repo: codeaholicguy/ai-devkit
Other skills on ai-devkit.
- /agent-communication
AI DevKit · Exchange information with active Codex, Claude Code, and other AI agents using ai-devkit agent list, detail, and send. Use when an agent needs to find another active agent, read its recent context, send it information, or request information back.
Open skill - /agent-management
AI DevKit · Manage running AI agents with ai-devkit agent commands. Use when an agent needs to identify itself, list agents, start workers, inspect agent detail, assign work, group agents, resume sessions, stop agents, or delegate work to other agents.
Open skill - /brainstorm
AI DevKit · Use when the user asks to brainstorm, ideate, generate ideas, expand options, challenge ideas, pressure-test ideas, compare concepts, narrow choices, name something, plan content angles, explore strategy, evaluate product ideas, technical approaches, experiments, or
Open skill - /changelog
AI DevKit · Update CHANGELOG.md Unreleased items from git commits since the latest release. Use when users ask to update changelog/release notes from recent commits, with one concise line per commit and commit/PR links.
Open skill - /dev-commit
AI DevKit · Safe git commit workflow for AI coding agents. Use when the user asks to commit, prepare a commit, stage changes, create a PR-ready checkpoint, or finish work with a conventional commit while avoiding unrelated user changes.
Open skill - /dev-design
AI DevKit · Design phase guidance for reviewing feature design against requirements. Use when the user wants to validate architecture, review design docs, resolve design trade-offs, or run dev-lifecycle phase 3.
Open skill

