agentleFS
Sign inStart free
ChrikeChrike/coding-agent-skills/skills/agent-workflow/SKILL.md

agent-workflow

Skill1 starsChanged 3 months agoNo licenceView on GitHub

Use when the user explicitly asks to parallelize work, coordinate multiple agents, run parallel scouts, split work across independent owners, or coordinate multiple independent verifiers; first perform the orchestration fit check even when the correct result is to keep one owner. Also use when two or more genuinely independent subsystem or artifact slices, repeated per-item pipelines, orthogonal scout questions, or high-stakes candidate-and-review scopes require coordinated ownership and integration with material benefit over one owner. Own decomposition, assignment, evidence handoff, verification coordination, and integration. Do not use for one focused delegation or verifier, small independent tasks without an explicit orchestration request when coordination cost exceeds the benefit, coherent single-owner or shared-root work without an explicit orchestration request, capability-only parallelism, or work already owned by another orchestration layer.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-agent, agent-analyze-code-quality 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.

The file

Show its rules and text

We split this skill into the rules it gives an agent

39 rules. 0 are common, 38 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 38

    Distinctive

    This author's own choices. Worth a look.

  • 1

    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 16 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.

Check your setup, free