agentleFS
kele-devkele-dev/Claude-Orchestrator-Skill/skills/team/SKILL.md

team

Skill10 starsChanged 2 days agoMITView on GitHub

Parallel multi-lane execution under the orchestrator cost rules. The main session plans and splits the work into file-disjoint lanes, haiku-coder lanes run in parallel, the main session verifies, and only failed lanes loop through fixes, with hard caps. Only runs when the user types /orchestrator:team.

49 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use community-led-growth, ph-community-outreach 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.
  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • xfstudioSkill

    micro-saas-launcher

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.

    Also in 5 projects that use this

  • mastepanoskiSkill

    ux-audit-rethink

    Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.

    Also in 5 projects that use this

  • ibahgatSkill

    ralplan

    Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.

    Also in 8 projects that use this

  • ncklrsSkill

    seo-content-strategist

    Expert SEO content strategy for SaaS and B2B sites. Use when doing keyword research, planning content clusters, creating pillar pages, optimizing on-page SEO, fixing technical SEO issues, building links, refreshing content, implementing programmatic SEO, mapping search intent, optimizing for SERP features, or measuring content performance. Use for SEO audits, content gap analysis, and organic growth strategy.

    Also in 5 projects that use this

  • +6 more from nicepkg

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 35 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read only the files you need.

    line 27
  2. Very specific:

    If the work cannot be split into at least 2 independent lanes, say so in one line and use the normal orchestrator:on flow.

    line 31
  3. Distinctive:

    Before launching, snapshot git status --porcelain as the baseline (shared and isolate paths).

    line 35
  4. Distinctive:

    Wait for the completion notifications.

    line 41

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

Team mode: parallel lanes, token-capped

Task: $ARGUMENTS

Team mode is orchestrator:on with parallel execution (the main session never edits). Shared mode rules (caps, fix rounds, raises, commit=batch, report, lessons): read modes.md in the orchestrator:on skill folder. Unit = lane, group = wave.

Budget (defaults; the user may override them in the arguments, e.g. lanes=2)

  • Max parallel lanes per wave: 3, raised to 4 only at plan time and only if the work has 4 or more truly independent, file-disjoint parts. Hard ceiling: 4.
  • Max fix rounds per lane: 2, raised automatically up to 4 (see modes.md).
  • lanes=1 means no parallelism: use the normal orchestrator:on flow.
  • opus-reviewer: at most once, on the final combined diff, and only for large work (>5 tasks, or touches schema/auth/security). Not Opus-class: the orchestrator:on reviewer rules (PRD before the first delegation, final diff) apply whatever the size.
  • --dry-run: stop after stage 1, show the lane plan and the planned number of delegations, and wait for the user's go.
  • commit=batch scope: per wave, after it is verified.
  • isolate=worktree (opt-in): launch each lane with isolation: "worktree". Before wave 1 check that worktree.baseRef is "head" in settings, there are no uncommitted tracked changes outside docs/prd/ (lanes branch from HEAD), and commit=batch is on (later waves branch from committed earlier waves); otherwise warn in one line and use the shared tree (note the caveat if the project needs installed deps a fresh worktree lacks).
  • Wave order under isolate=worktree, in this sequence: baseline -> launch lanes (brief: report your worktree path, the output of pwd, in NOTES) -> per lane verify INSIDE its worktree (git -C <wt> status --porcelain shows only owned files; run its check with cwd = the worktree) -> fix rounds for failed lanes reuse the same worktree: re-delegate WITHOUT isolation, brief says "work only in <wt path>" -> TYPE: APPLY for each PASS lane, run from the main tree root -> union check vs baseline and full suite in the main tree -> COMMIT if commit=batch -> next wave. Take each lane's worktree path from its report.
  • Checkpoint timing: after each wave when more waves remain.
  • budget=<N>k (optional): token budget over all delegations; rules in modes.md (Budget).

1. PLAN (main session)

  • Read only the files you need.
  • Split the work into lanes. Each lane has: id, goal, owned files, PRD excerpt, acceptance test, verification command.
  • Owned files are exclusive: no file appears in two lanes.
  • Lanes in one wave must be independent: no lane needs another lane's output. Dependent work goes into a later wave. Waves run one after another; lanes inside a wave run in parallel.
  • If the work cannot be split into at least 2 independent lanes, say so in one line and use the normal orchestrator:on flow. Do not force parallelism.
  • Show the lane table (lane, owned files, executor) in one short block, then continue without waiting (unless --dry-run).

2. EXEC (parallel)

  • Before launching, snapshot git status --porcelain as the baseline (shared and isolate paths).
  • Launch all lanes of the current wave in ONE message: one Agent call per lane, with run_in_background: true.
  • Executor: haiku-coder by default; sonnet-dev only for a lane that cannot be made atomic (orchestrator:on step 3).
  • Each brief is self-contained, because subagents start without this conversation: owned files, the lane's PRD excerpt, the verification command, "touch only these files; if you need another file, stop and report", and the report format STATUS/FILES/VERIFICATION/NOTES.
  • The lane verification command covers only the lane's owned files (syntax check, that file's unit tests): no full suite and no git write commands inside lanes. The main session runs the full suite only after the whole wave finished.
  • Tell every lane to return only the summary line of its verification output, never full logs.
  • Wait for the completion notifications. Do not poll.

3. VERIFY (main session)

  • After the wave (isolate: after APPLY): compare git status --porcelain with the baseline and flag only files changed since it that no lane owns (earlier user edits, the PRD and .claude/worktrees/ are never flagged). Such a file is a violation: ask the lanes' reports (FILES) which lane did it and handle it per the "changed a file outside its owned list" rule below.
  • Per lane: check its own files only (git diff -- <owned files>) and run its verification command yourself. Other verify rules: modes.md.
  • isolate=worktree: follow the wave order in Budget; per-lane checks run inside the lane worktree, and TYPE: APPLY (owned files, worktree path from the lane's report) comes before the union check.

4. FIX loop

  • Re-run only the failed lanes (modes.md: fix loop).
  • Lanes cooperate through the main session, never by messaging each other:
    • A lane reports that it needs a file owned by another lane: let the owner lane finish, then give the requesting lane a follow-up task in the next wave with that file added to its owned list.
    • A lane changed a file outside its owned list: read both lanes' changes to that file. Compatible (different parts, nothing overwritten): keep both and note it in the report. Conflicting: delegate one merge task to sonnet-dev with both diffs and both lanes' PRD excerpts, owning only that file. Never auto-revert.
  • Fix cap reached and not raised: mark the lane BLOCKED, let the other lanes finish, and do not start later waves that depend on it.

5. REPORT

Per modes.md: report. Unit = lane; status PASS / BLOCKED.

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.