agentleFS
Ivan-propioIvan-propio/claude-skills/dispatching-parallel-agents/SKILL.md

dispatching-parallel-agents

Skill0 starsChanged 8 months agoNo licenceView on GitHub

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

195 other projects use a version of this, 125 of them edited; 36 of 125 edited versions we compared changed its rules; 8 new projects in the last 4 weeks, against 14 the 4 before.

How people change it

36 of 125 edited versions changed its rules, and some changes recur.

Of the 125 edited versions we compared: 56 keep every rule, 33 are an older text, 36 made changes of their own.

Not in older versions

  1. All investigations completed concurrentlymissing from 33 of 33
  2. All fixes integrated successfullymissing from 33 of 33
  3. Run full suite - Verify all fixes work togethermissing from 2 of 33
  4. Integration: All fixes independent, no conflicts, full suite greenmissing from 1 of 33

Rules people drop

  1. All fixes integrated successfullydropped by 30 of 36
  2. All investigations completed concurrentlydropped by 29 of 36
  3. Verify fixes don't conflictdropped by 14 of 36
  4. Self-contained - All context needed to understand the problemdropped by 13 of 36
  5. Run full suite - Verify all fixes work togetherdropped by 13 of 36
  6. Integration: All fixes independent, no conflicts, full suite greendropped by 11 of 36
  7. When you have multiple unrelated failures (different test files, different subsystems, different bugs), investigating them sequentially wastes time. Each investigation is independent and can happen in parallel.dropped by 10 of 36
  8. Constraints: Don't change other codedropped by 9 of 36

Rules people add

  1. A rule we can't quote: its licence doesn't allow itadded by 3 of 36
  2. A rule we can't quote: its licence doesn't allow itadded by 2 of 36
  3. A rule we can't quote: its licence doesn't allow itadded by 2 of 36
  4. A rule we can't quote: its licence doesn't allow itadded by 2 of 36
  5. A rule we can't quote: its licence doesn't allow itadded by 2 of 36
  6. A rule we can't quote: its licence doesn't allow itadded by 2 of 36
  7. A rule we can't quote: its licence doesn't allow itadded by 2 of 36
  8. When you have multiple independent problems, dispatch one agent per problem domain and let them work concurrently. Each agent gets isolated context — never your session's history. This preserves your context for coordination. </purpose>added by 2 of 36

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Cooling: 8 new projects took it in the last 4 weeks, 0.6× the 4 weeks before.

Week of Sep 20: 2 new projectsWeek of Sep 27: 4 new projectsWeek of Oct 4: 5 new projectsWeek of Oct 11: 3 new projectsWeek of Oct 18: 1 new projectWeek of Oct 25: 3 new projectsWeek of Nov 1: 3 new projectsWeek of Nov 8: 1 new project
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions and 10 more.

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.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • obraSkill

    diagnosing-superpowers

    Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

    Also in 19 projects that use this

  • kntismSkill

    condition-based-waiting

    Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses

    Also in 3 projects that use this

  • xfstudioSkill

    context-driven-development

    Use this skill when working with Conductor's context-driven

    Also in 3 projects that use this

  • EvezArtSkill

    analytics-dashboard

    User behavior tracking and analytics dashboards

    Also in 3 projects that use this

  • +3 more from Leodorareluctant259

The file

We split this skill into the rules it gives an agent

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

  • 8

    Common

    Most of the 141 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 141 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.