multiagent-orchestration
Skill10 starsChanged todayMITView on GitHub
Role-based multi-agent coordination with isolated subagents and gated milestone checks
In this repository44 other files it gives its agents.
- llms-full.txtllms.txt
- llms.txtllms.txt
- ai-prompt-engineering-safety-reviewSkill
- ast-codemapSkill
- ast-grepSkill
- autoharnessSkill
- autonomous-backlog-driverSkill
- claude-kimi-mcp-normalizationSkill
- cli-self-updaterSkill
- code-frugalitySkill
- codemode-gatewaySkill
- codemode-typesSkill
- consequence-simulationSkill
- context-pruningSkill
- github-update-checkerSkill
- google-agents-cli-evalSkill
- google-agents-cli-scaffoldSkill
- history-searchSkill
- hook-gatingSkill
- hybrid-semantic-searchSkill
- kimi-code-agent-integrationSkill
- kimi-mcp-configurationSkill
- leann-vectorSkill
- log-summarizerSkill
- markdown-vagueSkill
- memory-reconciliationSkill
- mode-classificationSkill
- output-compressionSkill
- prompt-injectionSkill
- python-anti-patternsSkill
- regression-sentinelSkill
- restart-trackingSkill
- rollback-guardSkill
- rust-call-graphSkill
- secrets-managementSkill
- security-best-practicesSkill
- session-compactorSkill
- sqlite-memorySkill
- swarm-barrierSkill
- swarm-dagSkill
- autoharnessSkill
- code-reliability-checksSkill
- skill-threat-rulesSkill
- autoharnessSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use when dividing work among multiple specialized agent roles (e.g.
- Distinctive: line 18
Run subagents with independent context windows to prevent token exhaustion and distraction.
- Very specific: line 23
Never mark a subagent task complete without automated verification pass (autoharness verify).
- Distinctive: line 28
Run a multi-step task involving 2+ distinct roles.
- Very specific: line 31
Verify all role actions and artifacts are logged in .autoharness/swarm/ and searchable in memory.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
multiagent-orchestration
When to use
Use when dividing work among multiple specialized agent roles (e.g. Architect, Researcher, Worker/Coder, Verifier, Critic) to prevent single-context bloat and enforce independent review gates.
Steps
- Define specialized roles for subtasks:
researcher: reads codebase and external docs, generates specification or evidence.coder: implements modifications according to specification.verifier: executes tests and checks invariants.critic: independent evaluation without author bias.
- Isolate agent workspace context:
- Run subagents with independent context windows to prevent token exhaustion and distraction.
- Communicate between agents strictly via structured inputs/outputs (JSON artifacts or memory records).
- Connect subagents to shared Gateway memory:
- Index intermediate results in
.autoharness/memory.dbso subsequent agents can retrieve them using BM25 query.
- Index intermediate results in
- Enforce Hard Verification Gates:
- Never mark a subagent task complete without automated verification pass (
autoharness verify). - Escalate to arbitrator if a subtask fails verification multiple times.
- Never mark a subagent task complete without automated verification pass (
- Aggregate final results into an executive summary.
How to verify
- Run a multi-step task involving 2+ distinct roles.
- Confirm each role receives only necessary inputs, not the entire conversation history.
- Confirm that verification gate prevents invalid intermediate state from propagating to downstream workers.
- Verify all role actions and artifacts are logged in
.autoharness/swarm/and searchable in memory.
Facts found here
- Role specialization prevents context degradation in multi-step workflows (as demonstrated by ByteDance Deer-Flow and Ruflo).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

