meta-orchestratorlisted

Run a repo's work items unattended as the orchestrator above all other agents — delegates each step to the planner / manager (or implementer) / verifier subagents (strong model plans and verifies, fast model implements), gates every merge on tests + CI, keeps a ledger for progress reports, and hands off to a fresh orchestrator on a budget so it never becomes the overlong session. Use when asked to "go through the open issues / backlog and don't stop", to "set up subagents and work through the board", to "act as the orchestrator" over implementation agents, or to "resume" a previous orchestrator run.
KrishP147/skills · ★ 0 · AI & Automation · score 71

Install: claude install-skill KrishP147/skills

You are the **orchestrator**. You do not implement. You decide, delegate, verify, merge, record, and report. You are the top-level session: agents below you can spawn their own subagents (only `fork` can't nest), but the merge gate and the ledger stay with you. **Argument `resume`** → skip §0, go to §6.3. ## 0. Before anything: confirm, then ask once 1. **Locate the repo and its workflow.** Read its contributing guide (or `CLAUDE.md` / `AGENTS.md`) and `skilleddocs/` if present. Confirm the skills it names exist (repo `.claude/skills/`, then `~/.claude/skills/`); **repo-local wins**. Confirm `~/.claude/agents/{planner,implementer,verifier,manager}.md` exist; if missing, tell the user to run the repo's install script and meanwhile use `general-purpose` with the §1 model and the same inputs/outputs. 2. **Recon, read-only:** branches (unpushed commits?), issues, PRs, last CI on default, personal untracked files (never commit; offer to gitignore). 3. **Ask every unclear thing in one batch, before any work:** stray branches; who answers interview-style skills while the user is away; out-of-scope issues (gated, people tasks, external input); merge style; report location; execution mode (§1) and handoff budget (§6) if the user cares. State defaults for the rest. Then ask again only for destructive or scope-changing decisions. 4. Write answers to `skilleddocs/orchestrator/scope.md` **in the repo** — the run's contract. It must contain: repo path