multi-agent

Decide whether a task should run as a workflow, as delegated subagents, or in this single context, and say why in one line; checks first whether workflows are available in this session and downgrades `workflow` to `subagent` when they are not. Writes nothing. Use when: 'should this be a workflow', 'workflow or subagents', 'is this worth a workflow', 'how should I orchestrate this', 'fan this out or do it inline', 'is the Workflow tool available', or before a skill launches a workflow.

Recheck every bundled multi-agent role default (model, effort, the fan-out guard) against the upstream pointer recorded beside it, and report which defaults have drifted or whose recheck trigger has fired, each with fetched evidence and a proposed diff to reference/defaults.yaml; `repo` mode sweeps the repository's own model, effort, subagent and workflow guidance for stale or copied upstream claims. Proposes only; never edits a file. Use when: 'are the routing defaults current', 'audit the role map', 'recheck model defaults', 'did the workflow guidance change', 'new model released, check the defaults', 'is our model guidance stale', or when an as-of date in defaults.yaml looks old.

Read-only check that node resolves for the multi-agent drift-checker fetch gate hook and that the hook is registered. Use when a hook notice says node is missing, or before assuming the fetch gate ran. Does not install.

Resolve which model and effort each agent role gets in a multi-agent run (orchestrator, worker, verifier, retrieval) through the bundled defaults and the user, team and overlay config layers, and print it as fenced JSON with a single-agent and a fan-out variant per role and the layer that supplied each value. A fan-out stage never runs on a frontier model unless the config opts in. Use when: 'which model for the subagents', 'route the roles', 'what effort should the workers use', 'roles for the workflow args', 'model routing', 'is fan-out on Fable', or before a skill launches a workflow that takes args.roles.

Configure the multi-agent role map for a person or a repository: check prints the resolved map (model and effort per role, single and fan-out variants, the layer behind each value) and whether the personal overlay is gitignored; apply writes the keys you confirm into the user-global, team or local multi-agent.yaml layer, showing the map before and after. Use when: 'set up multi-agent', 'configure model routing', 'change the worker effort for this repo', 'turn off the fan-out guard', 'which layer sets the verifier model', 'multi-agent setup'. Re-runnable.