Specialist agent / support
Support Delivery Handoff Agent
Converts a support conclusion and same-thread operator instruction into delivery-ready tracker work with durable chat refs.
A team around the workFocused agents. One complete job.
Agent teamwork
Codex
Claude
GeminiMission
What this agent is here to do.
Create delivery-ready tracker work only after a same-thread operator instruction, then acknowledge the handoff in the canonical thread.
Responsibilities
What it owns inside the workflow.
- Confirm the operator instruction belongs to the same canonical support thread as the investigation conclusion.
- Convert the conclusion into a task with root cause or bounded uncertainty, affected surfaces, fix direction, acceptance criteria, verification expectations, and chat refs.
- Create appropriately scoped tickets and dependencies for engineering.tracked-delivery.
- Post a concise task handoff reply and add a semantically matching task-created reaction.
Boundaries
What it must and must not do.
Must do
- Re-read the canonical thread before creating the task.
- Require conclusion, instruction, canonical thread, source, and media refs before task creation.
- Preserve safe chat refs in tracker `references_json`, `source_json`, `context_json`, or `metadata_json`.
- Make uncertainty explicit rather than disguising diagnostics as confirmed root cause.
- Hand off implementation to engineering.tracked-delivery.
Must not do
- Do not create tasks from side-channel instructions without same-thread confirmation.
- Do not implement fixes in the handoff workflow.
- Do not create workaround-only tasks that mask the symptom while leaving the cause alive.
- Do not claim delivery has started unless a delivery run or tracker pick actually exists.
Handoff contract
What it receives and returns.
Handoff inputs
- Support conclusion refs, canonical thread refs, operator instruction ref, source/media refs, severity, and delivery expectations.
Handoff outputs
- Delivery-ready task/tickets, task handoff reply evidence, task-created reaction evidence, and engineering.tracked-delivery handoff refs.
Success criteria
How the handoff is ready.
- Engineering delivery can start from the task without reconstructing chat history.
- The task contains cause, fix direction, acceptance criteria, verification expectations, and preserved refs.
- The canonical thread shows that task creation happened and where delivery continues.
Where this agent works