Agent skill · operations · wshobson
on-call-handoff-patterns
Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use this skill when transitioning on-call responsibilities between engineers and ensuring the incoming responder has full situational awareness, when writing a shift summary that captures active incidents, ongoing investigations, and recent changes, when handing off mid-incident so a fresh engineer can take over the incident commander role without losing context, when onboarding a new engineer to the on-call rotation for the first time, or when auditing and improving the quality of existing handoff processes across teams.
Why this skill is useful
Provides detailed templates and procedures for effective on-call handoffs that improve incident response continuity and situational awareness.
What it needs
About 2k tokens when loaded. Last updated 2026-08-05. 38,570 stars on the source repository.
What this skill does
On-Call Handoff Patterns Effective patterns for on-call shift transitions, ensuring continuity, context transfer, and reliable incident response across shifts. When to Use This Skill Transitioning on-call responsibilities Writing shift handoff summaries Documenting ongoing investigations Establishing on-call rotation procedures Improving handoff quality Onboarding new on-call engineers Core Concepts 1. Handoff Components Component Purpose -------------------------- ----------------------- Active Incidents What's currently broken Ongoing Investigations Issues being debugged Recent Changes Deployments, configs Known Issues Workarounds in place Upcoming Events Maintenance, releases 2. Handoff Timing Templates and detailed worked examples Full template library and detailed worked examples live in references/details.md. Read that file when you need the concrete templates. Troubleshooting Incoming engineer misses a critical issue because the handoff document was incomplete. Use the outgoing checklist as a gate: do not mark handoff complete until every section has at least one entry (or an explicit "none"). Make incomplete handoffs a blameless postmortem action item. A 30-minute sync call is not possible due to timezone gaps. Fall back to the async quick handoff template (Template 2). Supplement with a short Loom or voice memo walking through the watch list. Ensure the incoming engineer has a direct contact method if they have follow-up questions. The incoming engineer inherits a mid-incident and is immediately overwhelmed. Use the incident handoff template (Template 3) specifically. The outgoing engineer should remain available on Slack for 15 minutes after handoff, even if off-call, to answer clarifying questions. On-call handoff documents are inconsistently formatted across teams. Adopt the shift handoff template organization-wide and store completed handoffs in a shared location (wiki, Notion, Confluence). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills wshobson/on-call-handoff-patterns