Back to catalog / Developer tools
On-call handoff: transfer incident context and escalation
Hand over active incidents, investigation state, recent changes, contacts, and next actions.
Skills
At handoff, record severity, user impact, timeline, confirmed vs unconfirmed hypotheses, recent deploys, attempted actions, and unresolved risks. For each active incident, name an owner, next check time, escalation threshold, and runbook link; label open questions instead of presenting them as conclusions. Confirm alert channels and access with the incoming responder so they do not have to reconstruct the investigation from raw logs.
Permissions
Prerequisites
- Needs incident records, timeline, recent changes, runbooks, and incoming rotation details.
Permissions
- May read approved incident/on-call data and draft a handoff; notifying/escalating requires an authorized channel.
Limitations
A handoff summary is not live alerting; do not copy credentials or sensitive customer data into broad documents.
Pinned upstream source
- Repository
- wshobson/agents
- File path
- plugins/incident-response/skills/on-call-handoff-patterns/SKILL.md
- Pinned commit
46891e7e60da0e52baf1050b7b6391b64e84c6d9- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: MIT
Compatible tools
PagerDuty/Opsgenie (if configured) · incident wiki · compatible agent
Main topic
Take a coding Agent change from context to verification