Delegate & Review

Pick the right agent for a piece of work, hand it off as a task, then poll and review delegated tasks so the fleet keeps moving.

When to use

You need to break off a piece of work and route it to a specific agent instead of doing it yourself.
You have outstanding delegated tasks and need to check whether they are done, blocked, or stalled.
A goal requires matching sub-work to the agent best suited for it before handing it off.
You are unblocking the fleet by reviewing completed or blocked delegated tasks and deciding next steps.

list-agents — see which agents exist and what they are suited for, so you can pick the right one before delegating.
delegate-task — hand a task off to the agent you selected.
list-tasks — see the current state of delegated tasks (open, in-progress, complete, blocked).
check-task — pull the full detail and result of a specific delegated task.

Clarify the unit of work to delegate: what outcome is needed, and what would count as done.
Call list-agents to see the available agents and their descriptions.
Match the work to the agent whose description best fits the required skill or domain. If no agent fits, do not force a mismatch — note the gap and escalate via send-message instead of delegating blindly.
Call delegate-task with a clear, self-contained description of the work, including any context the receiving agent will need (it will not have your conversation history).
Record what you delegated and to whom, so you can follow up later without re-deriving it.
Periodically call list-tasks to see the status of delegated tasks across the fleet.
For any task that shows as complete or blocked, call check-task to pull its full result or blocker detail.
If a task is complete, use its result to continue your own work or to inform further delegation. If a task is blocked, read the blocker reason and either re-delegate with clarified instructions or escalate to a human.
If a delegated task has been sitting idle far longer than the work should take, treat it as stalled: check it again, and if still stuck, re-delegate or escalate rather than waiting indefinitely.

401/403 on any underlying integration call the delegated task depends on -> missing Integration; escalate to a human via send-message naming the service and required scopes.
list-tasks or check-task returns empty or missing data -> verify you are querying the right task IDs and that the delegation actually went through; re-check with list-tasks.
Rate limited when delegating or polling -> back off and retry later; note the rate limit in memory so future runs pace themselves.
No agent in list-agents fits the work -> do not delegate to a mismatched agent; escalate to a human instead.

The task appears in list-tasks with a terminal status (complete or blocked) and check-task shows a concrete result or blocker reason.
Work that was mismatched to any available agent was escalated rather than force-delegated.
Stalled or blocked delegated tasks have been re-delegated with clarified instructions or handed to a human, not left silently idle.