agentleFS
BlakeHastingsBlakeHastings/claude-code-artifacts/orchestrated-delivery/SKILL.md

orchestrated-delivery

Skill1 starsChanged 5 months agoNo licenceView on GitHub

Run a project as an orchestrator driving implementation subagents against a GitHub issue backlog: break work into issues, brief agents that work in isolated worktrees, review what comes back, and merge through a path that mechanically refuses red checks. Use when asked to "orchestrate", "act as an orchestrator", "manage agents", "keep working while I'm away", "break this down into GitHub issues", or when taking over a repo that already has docs/process/orchestrating.md. Also use when setting this workflow up in a new repo, when a subagent's PR needs reviewing before merge, when several agents must run in parallel without colliding, or when deciding what to escalate to the human owner instead of guessing. Covers brief anatomy, verification that proves rather than accepts, merge discipline without branch protection, and how the loop revises itself.

3 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

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

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