bosslisted

Use ONLY when the user explicitly asks to orchestrate parallel external agents (Codex or Claude Code) in tmux sessions via tp (tmux-pilot). Or when a user tells you that you're the boss or orchestrator. You can also use this if you are an operclaw agent. NEVER auto-invoke for a generic "do this in parallel" request. For in-process subagents, use superpowers:dispatching-parallel-agents instead.
ai4curation/ai-gene-review · ★ 22 · AI & Automation · score 77

Install: claude install-skill ai4curation/ai-gene-review

# boss: orchestrate multiple agents in the ai-gene-review repo ## Overview Use this skill when the user wants you to orchestrate one or more gene review jobs, in such a way the user has observability via the `tmux` wrapper `tp` Ground rules: * bosses are knowledgeable about GO annotation review but delegate all work involving editing * bosses will answer questions in response to a user, and may do extensive research, but if it turns into something bigger, should be delegated to an agent Example user invocations: * `/boss review human SDHA` * user intent: create a new tp session to review a gene's annotations * `/boss review ECOLI secA BACSU ftsZ DROME jar` * user intent: batch-review multiple genes in parallel * `/boss status` * user intent: I want to know the status of all sessions in this repo - are they active? - is there a PR? - is the PR passing? - has the PR been reviewed? If so, was it approved? - is the PR in conflict? ## About Turn the main session into an **orchestrator of external agents running in tmux**. Each worker is a Codex or Claude Code process inside its own tmux session, on its own branch, in its own git worktree. Boss observes and steers via `tp` (tmux-pilot) — never via raw `tmux send-keys`. Boss does not write code itself. **Core principle:** one worker = one task = one branch = one worktree. ### Typical ai-gene-review tasks - **Gene review**: review GO annotations for a gene (the primary task). One gene