agentleFS
Sign inStart free
int2t05int2t05/engineering-skills/skills/04-develop/multi-agent-orchestration/SKILL.md

multi-agent-orchestration

Skill3 starsChanged 28 days agoMITView on GitHub

Execute authorized agent work with explicit ownership and integration checks. Triggers on "parallel agents", "并行 agent".

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use tdd-workflow.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • lodetomasiSkill

    tdd-workflow

    Test-Driven Development workflow with red-green-refactor pattern and best practices

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

Multi-Agent Orchestration

When to use

  • Execute authorized agent work with explicit ownership and integration checks.

Not for: breakdown for decomposition; implement for single-agent work.

Steps

  1. Confirm delegation is authorized and supported; use it only when isolation or concurrency earns the overhead.
  2. Separate dependencies and independent tasks; assign file and state ownership so writers do not collide.
  3. Provide goals, inputs, decisions, boundaries and verification targets; describe actual shared context and filesystem capabilities.
  4. Inspect returned diffs and rerun checks before integration; reconcile assumptions and verify the whole result.

Verify

  • Ownership and dependencies are explicit; integration is checked independently of agent claims.

References

  • engineering-principles.md — shared decision boundaries, scope and verification.
  • references/dispatch-patterns.md — when to fan out vs sequence, context-construction templates, review-checkpoint patterns, common failure modes (race conditions, context-starved subagents, unverified seams).

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free