跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
浏览器与自动化

agents-swarm-orchestration

Coordinates multi-agent execution across subagents, teams, and workflows. Use when planning dependency-aware fan-out, verifier passes, runtime selection, or Loop Engineering.

vasilyu1983 · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add vasilyu1983/AI-Agents-public --skill agents-swarm-orchestration

技能说明


name: agents-swarm-orchestration description: "Coordinates multi-agent execution across subagents, teams, and workflows. Use when planning dependency-aware fan-out, verifier passes, runtime selection, or Loop Engineering." compatibility: Claude Code + Codex. Claude Code Agent tool (renamed from Task in v2.1.63) plus Codex subagents — runtime-specific dispatch. version: "1.5" last_validated: 2026-08-27

Swarm Orchestration

Advanced execution layer for multi-worker runs after agent or team selection.

Coordinate multiple workers without polluting the main thread. Use this skill after agents-subagents has already selected the right agent, member, team, or debate pattern. This skill is for choosing the orchestration surface, freezing task ownership before fan-out, and requiring structured outputs that the lead agent can validate and merge safely.

Terminology (Aug 2026)

"Swarm" is community vocabulary — it appears nowhere in Anthropic documentation. Use the official primitive names when writing configs, prompts, or docs; keep "swarm" only as informal shorthand for the whole category.

InformalOfficial primitiveStatus (Aug 2026)
"swarm of subagents"SubagentsGA. Background behavior is mode-dependent; background: true forces background but false is not a documented foreground pin. Recursive spawn currently defaults to three layers below the main session
"swarm with peer chat"Agent teamsExperimental, env-gated CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1. Behavior churns weekly — re-verify before relying
"scripted swarm"Dynamic workflowsShipped 2026-05. JS in .claude/workflows/; ≤1000 agents/run, 16 concurrent. The repeatable-orchestration artifact
"swarm across terminals"Cross-session messagingAug 2026, macOS/Linux. Sessions message each other without a team — lighter than teams for passing findings

Quick Reference

SituationDefault patternWhy
1-2 tasks or shared-file editsStay in the main conversationParallelism adds coordination overhead without payoff
Focused worker that only needs to report backClaude Code subagent or Codex workerIsolated context, simple coordination
Workers must talk to each otherClaude Code agent teamShared task list plus direct messaging
Read-heavy scans, tests, triage, summarizationParallel workersKeeps noisy intermediate output off the lead thread
One coordinator should retain user ownershipManager / agents-as-toolsLead keeps control of decisions and final answer
Specialist should take over the conversationHandoffOwnership moves to the specialist agent
Work of unknown extent — discovery is the taskLoop until K empty roundsA fixed task list cannot be enumerated up front
Loop Engineering: recurring discovery or evaluationLoop-until-dry or budget-bounded loopDefine convergence, termination, and state checkpoints
Many items, known stages, high intermediate volumeScripted workflow (Claude Code)Script holds control flow; lead context holds only the result

Navigation

  • references/loop-orchestration.md - Bounded iteration vs retry, loop-until-dry, convergence detection, termination predicates, dedup-target rule
  • ../ai-coding-agents-tasks/references/loop-and-graph-runtime-surfaces.md - Loop Engineering and Graph Engineering runtime comparison: task queues, cyclic graphs, and workflows
  • references/scripted-workflows.md - Script-held deterministic control flow (Claude Code Workflows): agent/parallel/pipeline, barrier-vs-pipeline, resume and caching
  • references/platform-patterns.md - Platform guidance for Claude Code subagents, Codex subagents, Codex multi-agents, and OpenAI Agents SDK
  • references/output-contracts.md - Task schema, worker report schema, and merge contract
  • references/operational-guardrails.md - Safety, stop conditions, observability, and verification gates
  • references/cost-discipline.md - Fan-out cost patterns, session lifecycle, loops/schedules audit, orchestration-layer config
  • references/orchestration-maintenance-runbook.md - How to audit, maintain, and refresh swarm discipline over time
  • references/runtime-smoke-tests.md - 3 shell-runnable checks for wave dispatch, per-worker budget breach, and wave-boundary checkpoints
  • references/execution-surfaces.md - Single thread, worker fan-out, agent team, manager, and handoff selection
  • references/noninteractive-and-blueprints.md - CI-safe dispatch patterns and deterministic-plus-agentic blueprint flows
  • references/recipe-wave-dispatch.md - Self-contained 3-worker shell example: copy, paste, run, verify
  • references/typical-scenarios.md - Scenario library: common jobs mapped to surface, pattern, worker shape, and the trap to avoid
  • agents-subagents - Subagent design, tool scoping, and interruption recovery
  • ../agents-hooks/SKILL.md - Hook guardrails and verification automation
  • ../agents-mcp/SKILL.md - MCP server scoping for workers
  • ../agents-skills/SKILL.md - Skill packaging for worker preloads
  • ../agents-memory/SKILL.md - Project memory for shared conventions
  • ../ai-coding-agents-permissions/SKILL.md - Approval routing, allow or
阅读完整来源 ↗