agentleFS
Sign inStart free
BenjaminGBenjaminG/ai-skills/skills/orchestrate/SKILL.md

orchestrate

Skill4 starsChanged 5 months agoNo licenceView on GitHub

Run a dependency-ordered list of Linear tickets through Herdr. One tab, one worktree, one agent per layer, committed and checked before the next layer starts, PRs opened at the end. Use when asked to orchestrate, run, or dérouler a stack of tickets, or given a parent ticket whose sub-issues carry a build order.

  • Commits and pushes

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 139 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

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

  • Other versions155 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 155

    1. Significant-Gravitas/AutoGPT★ 188ksame name
    2. rohitg00/pro-workflow★ 2.9ksame name
    3. apmantza/pi-lens★ 508same name
    4. boshu2/agentops★ 452same name
    5. quantumaikr/quant.cpp★ 403same name
    6. Noizefield/audio-plugin-coder★ 334same name
    7. kagenti/kagenti★ 302same name
    8. varun29ankuS/shodh-memory★ 294same name
    9. provencher/codex-skills★ 271same name
    10. first-fluke/fullstack-starter★ 225same name

    145 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use define-requirements, orchestrate-plan 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.
    • sson0-erSkill

      define-requirements

      Work with the user, one question at a time, to complete the requirements document (docs/claudex/<slug>/01-requirements.md). Run by the orchestrator (parent). Stays out of design and implementation.

      Also in 3 projects that use this

    • EternallLightSkill

      orchestrate-plan

      Use when executing a locked, reviewed PLAN.md by delegating the implementation to visible worker agents in Orca, herdr, or cmux ONE PHASE at a time — splitting the plan into context-window-sized phases, giving every phase a pristine worker context, and (when the plan touches INDEPENDENT repos) running one worker per repo IN PARALLEL. Triggers on "run the plan with a worker", "execute the plan in the other pane", "split the plan into phases and build it with workers", "build the backend and frontend in parallel panes". Not for edits you can finish inline; outside Orca, herdr, or cmux use tgc-skills:orchestrate.

      Also in 3 projects that use this

    • sson0-erSkill

      record-evidence

      How to record external facts (docs, command output, codebase findings) as evidence and design choices as decisions. Used by the researcher, designer and reviewer agents.

      Also in 3 projects that use this

    • PinkneyJiangSkill

      improve-architecture

      扫描代码库中的架构摩擦点，识别浅模块并挖掘深模块演进机会。生成可视化交互式 HTML 诊断报告，并在用户确认后闭环实施深度重构。

      Also in 4 projects that use this

    • mukcoSkill

      principles

      General software engineering principles — DRY, SOLID, YAGNI, KISS, naming, code smells, and refactoring. Language-agnostic. Use alongside language-specific skills.

      Also in 3 projects that use this

    • kjnezSkill

      ticket

      Work on a JIRA/Linear ticket end-to-end: read ticket details, explore codebase, create a branch, implement with TDD, run quality checks, update ticket status, and create a PR. Use when the user provides a ticket ID to implement. Triggers on requests like "/ticket PROJ-123", "work on this ticket", "implement PROJ-123".

      Also in 3 projects that use this

  • In this repository37 other files it gives its agents.

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