agentleFS
aprameyakaprameyak/coding-skills/parallel-work/SKILL.md

parallel-work

Skill1 starsChanged 41 days agoMITView on GitHub

Parallelize independent tool calls and subtasks. Use when gathering context, running checks, or splitting work that has no dependencies.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Prefer one writer per file region at a time.

    line 14

“Common” is measured: kept by at least 6 in 10 of the 6 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.

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

Parallel Work

Rules

  • Batch independent reads/searches/status checks in one step.
  • Serialize only when output of A is required for B.
  • Split large tasks into isolated units with clear boundaries.
  • Merge results before editing shared files to avoid conflicts.
  • Prefer one writer per file region at a time.

Good Parallel Batches

  • git status + git diff + git log
  • Multiple symbol searches in different areas
  • Lint + typecheck + unit tests when isolated

Avoid

  • Parallel edits to the same file
  • Spawning duplicate exploration that repeats the same search
  • Over-splitting tiny tasks that cost more coordination than they save

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.