Index of every page on this site: llms.txt
All skills
masihmoafi avatar

/multi-agent

@c0a5d13
by Masih Moafimasihmoafi/skills10 stars
Run it yourself

Split work across agents without losing control, with one worktree and prompt file per task and a coordinator who integrates. Use when dispatching more than one agent or writing a brief for another agent.

  • 1 file
  • 2.8 KB
  • Updated 3 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/masihmoafi/skills/multi-agent

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈54 tokens for metadata: the name and description. ≈658 when used: this file.

Description uses 2.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈218 characters, or 2.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Multi-agent dispatch

Run agents in parallel only on independent tasks: two agents editing one interface produce two plausible diffs that cannot both be right. The unit is one task, one branch, one worktree, one prompt file, one acceptance check. Read-only reviewers may share a tree if writes are forbidden.

Roles

  • Coordinator: owns the task list, architecture, order, integration and the verification label. Creates and removes worktrees and picks each task's model. Never lets a worker redefine the product.
  • Worker: does one bounded task in its own worktree and returns changed files, checks run, evidence and risks. Touches nothing outside its scope.
  • User: decides product behavior and accepts the result.

Setup

Use the worktree location and base the project names; do not assume the default branch holds the work the task needs. git worktree add "$path" -b "$branch" "$base". Put the prompt in WORKER_PROMPT.md at that worktree's root, marked "Do not commit it". Remove the worktree only after its branch is integrated or abandoned.

The prompt contract

A missing or contradictory field is a reason to challenge the task, not to start.

Task ID:
Desired user-visible behavior:   what a person sees, not an implementation
Why it is needed:
Allowed files:                   a real list, plus a rule for the ragged edge
Forbidden scope:                 the specific temptations (adjacent refactors, coordinator files, publishing)
Dependencies already verified:
Acceptance test:                 numbered; each item can fail
Required checks:                 build flags, disk limits, commands never to run, what runs on CI
Return: summary, changed files, verification, risks, commit hash.

Put every binding constraint in the prompt: what cannot be verified here and the ceiling of what CI can prove; disk-heavy build flags; "report, do not patch" for observation tasks. When a null result is legitimate, say so ("if the only lever costs more than it buys, report that and close"), so the worker does not ship churn.

Before dispatching

Serialize two tasks when their allowed files intersect, when they touch a shared runtime, protocol or permission contract still being reshaped, when they would exhaust one disk or CPU, or when they install to the same path or app home.

Verification and integration

Label each result user-verified (the only "done"), agent-verified, or unverifiable here (name what would be needed); the ranking is in the spec skill. Integrate one branch at a time and rerun the acceptance test on the merged tree.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at c0a5d13. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 3 weeks ago

README badge

README badge for masihmoafi/skills/multi-agent