agentleFS
Sign inStart free
awesome-team-wawesome-team-w/coord/skill/SKILL.md

coord

Skill0 starsChanged 4 months agoMITView on GitHub

Use when starting any coding task in a repository whose AGENTS.md contains a coord block (markers `<!-- coord:begin -->`) - coordinates parallel agent sessions by claiming files before editing, reordering work on conflicts, and making task-scoped commits

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. jircdev/crew-plugin★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write what a colleague would need: "refactor login flow (auth.ts, session.ts)" beats "fix stuff".

    line 23
  2. Very specific:

    Wait and retry: if the contested file is your only remaining work, check coord status between your other steps.

    line 33
  3. Very specific:

    Co-edit deliberately: only when the edits cannot interfere (e.g.

    line 35
  4. Distinctive:

    Never work around a refusal by editing without a claim — that recreates the exact conflict this protocol exists to prevent.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Coordinating Parallel Edits with coord

Multiple agent sessions may be editing this repository right now. coord is the shared ledger that keeps you from stomping each other. The protocol is in AGENTS.md; this skill is how to use it well.

Golden path

  1. coord task start "<one-line description>" → remember the id (e.g. T12).
  2. coord claim -t T12 <paths> before creating or editing anything.
  3. Edit, test as usual. Claim more paths as your plan grows.
  4. coord commit -t T12 -m "<message>" (never plain git commit -a / git add -A).
  5. coord task done T12 the moment the task is finished.

Writing useful task descriptions

Other sessions decide how to reorder their work based on your description. Write what a colleague would need: "refactor login flow (auth.ts, session.ts)" beats "fix stuff". Mention the subsystem, not just the verb.

When a claim is refused (exit code 2)

The output tells you who holds the path, for which task, since when. Do NOT edit the file anyway. In order of preference:

  1. Reorder: claim and work on your non-conflicting files first, then re-claim the contested path later — the holder may be done by then.
  2. Wait and retry: if the contested file is your only remaining work, check coord status between your other steps.
  3. Co-edit deliberately: only when the edits cannot interfere (e.g. you append to a changelog they touched), re-claim with --force. This is recorded and visible to both sessions.

Never work around a refusal by editing without a claim — that recreates the exact conflict this protocol exists to prevent.

Claim granularity

  • Claim files for surgical changes; claim a directory when you will rework most of it (this blocks all files beneath it).
  • Over-claiming starves other sessions; claim what you will actually touch.
  • More claims later is cheap: coord claim -t T12 <new-path> any time.

Stale tasks

coord status marks tasks whose session died as STALE. Their files are safe to claim — you will see "taken over from stale T<n>" in the output. If you crashed and restarted, start a fresh task; do not reuse the dead task's id.

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