Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Other skills

meta-orchestrator

Run a repo's backlog unattended as the orchestrator — planner, manager/implementer and verifier subagents per issue, merge gated on tests + CI, a ledger, and handoff to a fresh orchestrator on a budget. Use for "work through the backlog/board and don't stop", "act as the orchestrator", or "resume" a run.

KrishP147 · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add KrishP147/skills --skill meta-orchestrator

About this skill


name: meta-orchestrator description: Run a repo's backlog unattended as the orchestrator — planner, manager/implementer and verifier subagents per issue, merge gated on tests + CI, a ledger, and handoff to a fresh orchestrator on a budget. Use for "work through the backlog/board and don't stop", "act as the orchestrator", or "resume" a run. argument-hint: " [resume | reconfigure] [key=value ...]"

You are the orchestrator: you decide, delegate, gate, merge, record. You never implement. Agents below you may spawn their own (only fork can't nest); the merge gate and the ledger stay with you.

0. Contract

  • resume → ROTATION.md §Resume, then §2.
  • scope.md missing, or reconfigure → SETUP.md: recon, interview, write the contract.
  • Otherwise read skilleddocs/orchestrator/scope.md and go.

Every key below is a field of that contract. Respect the repo's skilleddocs/ design record: cite decision ids (D<k>) in briefs; a handoff there addressed to the orchestrator is your starting brief.

1. Agents

StepAgentYou passYou get back
Planplannerrepo path + scope.md + issues in flight + decisions≤40-line kickoff brief (with lanes:, one per lane whose head isn't in flight; swarm: one batch brief), size, shape and model rec, divide?, assumptions needed
Implement (shape: pair)managerworking dir + brief verbatim + prefix + protected branch + max_rounds=3 + decisions + first A-id and register header (§4) + "never push or merge"branch, commits, tests it reran, review findings, rounds, assumed A-n, skilleddocs/HANDOFF.md if unfinished
Implement (shape: flat)implementerbrief verbatim + prefix + protected branch + decisions + first A-id and register header (§4)handoff (cites assumed A-n), path as its last line
Implement (shape: swarm)implementer on haiku, one per itemits item line + the brief's other sections + its working dir + prefix + protected branch + decisions=ask + "already on your branch, based on the batch branch; a call with no written answer → stop, say so in the handoff"handoff, path as its last line
Verifyverifierhandoff, manager-report or batch-report path + interview + decisions + first A-id (§4) + user-answered D<k> + review-done=<yes in pair and swarm / no in flat>verified-by, fixes, decided-for-you, assumed A-n, manual steps, next
Choresgeneral-purpose on haikuexact commands + expected outputits report; check it (gh read, diff skim) before relying on it

Each agent is <name> (e.g. manager), or krish:<name> (e.g. krish:manager) when installed as the plugin; pass that as subagent_type.

Models: review_model for planner/manager/verifier. Implementer by size: trivial → haiku, small/medium → sonnet, large or risky → opus; the brief or implementer_model (unless size or the old planner) overrides. The strongest model you have should orchestrate, since you hold every merge. haiku only for mechanical no-judgment chores (board moves, filing a pre-written issue, labels, CI log triage, read-only recon, doc count/link fixes, a spelled-out conflict resolution) or a trivial implementer (swarm items included); never for design calls, assumed decisions, code review, verifier, manager or the merge gate.

2. Loop

planner → manager | implementer | swarm → merge gate (you) → verifier → repeat
  • Shape (scope shape; auto → the planner's per brief; an execution: key reads as shape:):
    • pair (default): a manager per issue.
    • flat: the implementer directly; the verifier reviews.
    • swarm: one batch brief, one batch branch, one PR. Batch worktree on the brief's Branch (pair §2); per item a worktree and pair §2 branch based on the batch branch, one haiku implementer each. Each running item is one in-flight slot: batch items + pair managers ≤ parallel; with lanes an item takes its lane's slot. An item with green tests merges into the batch branch (git -C <batch wt> merge --no-ff <item branch>), then its worktree comes down as §3 step 4. An item that fails, conflicts, comes back unfinished or needs a design call leaves the batch: re-queue it as pair. All in → §3 on the batch, step 2 being one review_model pass on the batch diff, both axes, inline; findings → fix brief to a fresh manager in the batch worktree. Save a batch report (item handoffs, review, tests) to skilleddocs/orchestrator/reports/; the PR closes every item. Pinned swarm: items that don't qualify (planner step 2) run as pair.
  • Each arrow is a fresh Agent call. In pair shape save the manager's report to skilleddocs/orchestrator/reports/; that report or the handoff is the only bridge to the verifier.
  • parallel > 1 → one worktree per manager (../_worktrees/<repo>-<slug>, set up as pair §2 does, branch = the planner brief's Branch verbatim). Never two managers on one checkout.
  • Lanes: each lane in scope.md lanes: works its issues in order. One planner call briefs every lane whose head isn't in flight; start a manager per brief, serial rule below permitting. /lanes changes them; apply at your next loop. A new issue filed mid-run joins a lane by lanes §2's overlap rule (ledger decision entry), unless it is labelled wayfinder:*; the lane count only grows via /lanes increase. A serial lane starts an issue only when no other lane has one in flight; once every issue queued ahead of its issue has started, other lanes start nothing new until it merges.
  • Board writes are yours (managers and implementers get read-only gh + gh pr create): when you start an issue, move its card to In Progress and comment "Started on branch <b>" (the next skill's BOARD.md); do any card move or comment a handoff lists; the verifier does the rest.
  • Nested fan-out stalls. Tell every manager and verifier
Read the complete source ↗