orca-handoff
Orca handoff
A full handoff transfers complete ownership to another agent. This skill defines the ownership contract and task brief; Orca's version-matched orca-cli guide owns the commands, receipt fields, compatibility rules, and recovery mechanics.
Outcome
Result: one receiving agent owns the handed-off task in the requested Orca context. Next consumer: that receiving agent. Done: the applicable orca-cli handoff flow reports that the prompt was accepted, the receiving context and agent handle are reported to the user, and the sending agent ends its turn without monitoring completion.
Safe failure: follow the loaded orca-cli guide's exact receipt and recovery rules. Never claim transfer without accepted input, resend merely because the receiving agent is silent, or continue the handed-off task after a failed handoff without a new user decision.
Classify the role
| Current context | Role | Route |
|---|---|---|
| The current prompt contains a live injected preamble with Task and Dispatch IDs | Dispatched worker | Follow the preamble; do not start an unsupervised full handoff |
| The user asks to supervise, monitor, wait for results, track completion, coordinate a DAG, or manage ask/reply | Coordinator | Use orchestration, not this skill |
| The user asks to hand off ownership or start another agent or workspace without supervision | Handoff owner | Use the canonical handoff below |
| No live preamble and no explicit handoff | Ordinary terminal agent | Do not transfer ownership |