Maintainer Orchestrator

Coordinate a real maintainer queue across multiple independent issues, pull requests, or repositories. This is a control-plane skill, not the default way to handle ordinary repository work.

Activation Gate, Hard Rule

Classify the request before creating workers, heartbeats, ledgers, or queue scans.

Direct single-item work

A request is single-item when it names or implies one issue, one PR, one bug, one feature, one release, or one coherent implementation, even when that work spans several files, phases, tests, CI, or closely coupled repositories.

For single-item work:

• Do not create a project worker merely because the task is nontrivial.
• Do not create a heartbeat, portfolio ledger, queue refill, dependency sweep, release proposal, or broad repository scan.
• Continue in the current session using the repository's normal skills and workflow (codex-first, maintainer/review/testing/release skills, and repo instructions as applicable).
• Ordinary focused subagents or Codex delegation remain governed by those normal skills; this orchestrator adds no extra worker requirement.
• If this skill was invoked accidentally for a single item, state that orchestration mode is unnecessary and continue directly. Never interrupt useful in-flight work solely to satisfy this skill.

Examples that stay direct:

• fix and land one issue;
• repair one contributor PR;
• trace one failure across an application and its dependency;
• make one release;
• implement one coherent refactor across two repositories.

Bounded orchestration

Use orchestration mode only when at least one is true:

• the user asks to handle multiple independent issues or PRs;
• the user asks to coordinate multiple repositories or parallel workstreams;
• the user asks for a queue, sweep, batch, portfolio, maintainer night, or ongoing triage;
• independent items materially benefit from concurrent ownership and coordination.