Use case · By situation
Leave a handoff the next responder can use
For engineers handing an incident to another responder.
A responder joining later needs the current state, what was tried and the next action. Those details can be scattered across messages. Keep the investigation in a Work task. Set its priority and owner, add evidence links, and update the next action before handing it over.
An incident
Investigate the service failure
- 1
Next action
Confirm the current impact before the next change
- 2
Context
Current symptoms and impact
- 3
Evidence
Actions attempted and evidence links
What to put in the task
- Assign the task to the person responsible for the next action.
- Add evidence links and explain what they show in a comment.
- Update the task when the work changes so the next reader has the current state.
Before you rely on it
Command interception depends on your client's hooks or proxy; see the setup guide for Claude Code, Codex, Cursor and other MCP clients.
- Specify tasks do not page an on-call engineer, execute a rollback or replace incident tooling. Record external actions and decisions explicitly.
- Work must be enabled for the selected account, and you need permission to read or change the task. Security access and device setup are separate.
Related use cases and clients
By riskProtected branchesA maintainer can follow the request from its reason to the review without reconstructing it from terminal messages.By riskProduction changesThe person reviewing the release can read the proposed change and its supporting evidence in the same task.By situationA releaseThe team can see who owns each next action and read the evidence without replaying every conversation.
All use cases →