agentleFS
The-Vibe-CompanyThe-Vibe-Company/quivr/.agents/skills/coordinate-fleet/SKILL.md

coordinate-fleet

Skill40k starsChanged 40 days agoMITView on GitHub

Coordinating the Quivr V2 agent fleet. Use when designated coordinator, or asked to launch workers on tickets, merge green pull requests, keep Linear and the demo in sync, or resume the fleet in a new (local or cloud) session.

1 other project uses a version of this.

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 6 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the The-Vibe-Company/quivr repository that our weekly crawl found: only 7 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about The-Vibe-Company/quivr

The biggest 5 of 7 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 7

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every finding that survives a session goes to Linear or to the repository, never only to a local note: the next coordinator may be a cloud …

    line 30
  2. Distinctive:

    When the owner changes a process rule, update this skill in the same session.

    line 31

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

The coordinator turns the owner's intent into merged pull requests. Workers each own one ticket; the coordinator picks what runs, answers their decisions, merges, deploys and reports. AGENTS.md and docs/agents/fleet-workflow.md define the protocol; this skill is the coordinator's practice on top of it.

Standing authority. The owner delegates reversible technical decisions, plan approval and merging to the coordinator, and does not want permission prompts: act, then report. Escalate only product decisions, irreversible or outward-facing actions, and anything that spends money.

Loop

  1. Read the fleet state from Linear, never from memory: the specs under THE-531, their sub-issues, state, Agent phase / Agent runtime labels, blocked-by relations, and the latest Agent status: comments. List open pull requests with gh pr list. Done when you can name every ticket in flight, every ticket ready to start (all blockers Done) and every pull request waiting for you.
  2. Launch one worker per ready ticket that does not collide with work in flight. Brief each with WORKER-BRIEF.md plus a ticket paragraph: the merged blockers and their hand-back notes, the decisions you already made for it, and which parallel workers touch neighbouring code. Run workers in the background with worktree isolation (isolation: "worktree" on the Agent tool; without it every worker edits the coordinator's checkout), on the strongest available model. When several workers build one feature (for example one UI tab), name one owner for the shared files and have it publish the shared API early. Done when every launched ticket is In Progress with a claim comment.
  3. Answer worker questions the same turn. Decide reversible choices yourself, pick the option that keeps behaviour observable and the engine generic, and record the decision and its reason on the ticket. When two workers need the same shared resource (Plugin API minor version, migration timestamp, generated files), set the rule once and tell both.
  4. Merge a ready pull request with MERGE.md. Done when the PR is merged, the ticket is Done with its agent labels removed, and every in-flight worker affected by what landed has been told.
  5. Check what the merge changed in production-like environments: the Railway demo and the docs site deploy from main. Follow OPERATIONS.md. Done when the deploy succeeded and a smoke check passed, or a follow-up ticket exists for what failed.
  6. Turn findings into tickets. A gap a worker reports, a bug seen in the demo, an alias to remove later: create the ticket under the right spec with an ## In short section (template in docs/agents/issue-tracker.md), blocked-by relations, and launch it if it is ready. Done when no finding lives only in a chat transcript.
  7. Report to the owner in their language, briefly: what merged, what is running, what you decided for them, and the one thing they must do (if any), with its exact place (a URL, a setting). Numbers and outcomes, no process narration.

Rules of thumb

  • Merge only after the worker's hand-back; a green PR can still get one more rebased push.
  • Parallel workers on one ticket area collide: stagger them, or give each a disjoint area and tell them the boundary.
  • Every finding that survives a session goes to Linear or to the repository, never only to a local note: the next coordinator may be a cloud session with none of your context.
  • When the owner changes a process rule, update this skill in the same session.

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.