Recipes
Agent Orchestration
Turn the agent you're already talking to into a coordinator of other agents
Use when
the fan-out is mechanical: many similar slices, clear acceptance criteria, and results a coordinator can verify against tests. For work you want to review step by step, use the manual recipes above.
The superset:orchestrate skill lets one agent coordinate many. Ask the agent you're already talking to for parallel work, and it runs the whole job through the Superset CLI: an isolated workspace per worker, an agent launched in each, follow-ups sent over their terminals, results collected at the end.
The coordinator can be Claude Code or Codex; the workers can be any mix of agents Superset runs.
Install
The desktop app ships this skill automatically, so if you use Superset, your agents already have it. For standalone agents:
npx skills add superset-sh/skillsClaude Code users can also install via the plugin marketplace:
/plugin marketplace add superset-sh/supersetWhat to Ask For
- Fan out a refactor or migration across several worktrees at once ("split this migration into independent slices and run a worker on each")
- Hand a branch from one agent to another with its full terminal context
- Dispatch to a remote host and monitor until every worker reports done or blocked
How It Works
Under the hood the coordinator uses the Superset CLI:
superset workspaces createfor an isolated branch per workersuperset agents createto launch a worker with a bounded promptsuperset terminals read/sendto monitor progress and deliver follow-ups or dependency results
Workers finish by reporting a structured completion or blocked message, which the coordinator verifies before integrating. You review the results the same way as always: one branch and PR per worker.
Related: Automations for scheduled dispatch, and the MCP server for agents that drive Superset over MCP instead of the CLI.