AutoGineer
Generated banner for On Call Handoff Patterns
Generated logo for On Call Handoff Patterns

On Call Handoff Patterns

Seth HobsonCommunityCreated by Seth Hobson

  • Skill
  • Guidelines
  • Software development
  • MIT
  • No issues found
Download ZIP

From the author

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.
— the description by Seth Hobson

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured approach to transitioning on-call responsibilities between engineers. It focuses on maintaining situational awareness through standardized documentation, defined handoff components, and recommended timing patterns. By establishing consistent practices for transferring context regarding active incidents, ongoing investigations, and recent changes, it helps teams minimize knowledge gaps and reduce the risk of critical issues being overlooked during shift changes.

What it does

  • Defines core components for comprehensive handoff documentation
  • Provides a recommended 30-minute overlap procedure for shift transitions
  • Offers templates for shift handoff documents and incident handoffs
  • Includes strategies for handling timezone gaps and async handoffs
  • Suggests verification steps to ensure alerting is functional for the incoming responder
  • Provides guidance on managing escalation reminders and quick reference information

When to use it

  • When transitioning on-call responsibilities between engineers
  • When writing a shift summary for active incidents and ongoing investigations
  • When handing off mid-incident to ensure context is preserved
  • When onboarding a new engineer to the on-call rotation
  • When auditing or improving existing handoff processes across teams

Advantages

  • Reduces the risk of missing critical information during shift changes
  • Ensures incoming responders have immediate situational awareness
  • Standardizes handoff formats across different teams
  • Provides clear procedures for both synchronous and asynchronous handoffs
  • Helps prevent incoming engineers from being overwhelmed during mid-incident handovers

Usage examples

“How should I structure my on-call handoff document for the next shift?”
The agent provides a template covering active incidents, ongoing investigations, recent changes, known issues, and upcoming events.
“What is the recommended process for handing off an active incident?”
The agent suggests using the incident handoff template and keeping the outgoing engineer available for 15 minutes post-handoff for questions.
“How can I handle a handoff when the incoming engineer is in a different timezone?”
The agent recommends using an async quick handoff template supplemented by a short voice memo or video walkthrough.
“How do I ensure the incoming engineer's alerts are working?”
The agent advises a standard verification step where the outgoing engineer fires a test alert to confirm receipt by the incoming engineer.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/wshobson/on-call-handoff-patterns/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip on-call-handoff-patterns.zip -d .agents/skills

Documentation by Seth Hobson

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
ComponentPurpose
Active IncidentsWhat's currently broken
Ongoing InvestigationsIssues being debugged
Recent ChangesDeployments, configs
Known IssuesWorkarounds in place
Upcoming EventsMaintenance, releases
2. Handoff Timing
Recommended: 30 min overlap between shifts

Outgoing:
├── 15 min: Write handoff document
└── 15 min: Sync call with incoming

Incoming:
├── 15 min: Review handoff document
├── 15 min: Sync call with outgoing
└── 5 min: Verify alerting setup

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). Link each handoff from the on-call schedule entry in PagerDuty.

Incoming engineer cannot verify their alerting is working before the outgoing engineer logs off. Add a standard step: outgoing engineer fires a test alert and confirms incoming engineer receives it in PagerDuty and Slack before ending the overlap window.

Related Skills

  • incident-runbook-templates — Runbooks for the incidents that are handed over mid-response

  • postmortem-writing — Turn resolved incidents from the shift into structured postmortems

Files

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Seth Hobson
Publisher
Seth Hobson (Community)
Source
wshobson/agents · plugins/incident-response/skills/on-call-handoff-patterns · commit 4bde316
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Seth Hobson.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download on-call-handoff-patterns.zip