skilld
All skills
wshobson avatar

/on-call-handoff-patterns

@51b6e0b
by Seth Hobsonwshobson/agents40k stars
4,281

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.

Ask your Agent

Use this Skill: https://skilld.dev/gh/wshobson/agents/on-call-handoff-patterns

This session only. Nothing lands on disk.

SKILL.md

≈162 tokens always: the name and description. ≈756 when used: this file. ≈1.6k more on demand in 1 file.

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

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

Source: SKILL.md on GitHub

Third-party checks

1 warning2d5 checks · Risk SAFE
  • Gen Agent Trust Hub2d

    This skill provides documentation templates and best practices for coordinating on-call engineering handoffs. It contains no executable code, scripts, or network-enabled functionality.

  • Socket2d

    No alerts

  • Snyk2d

    Risk: LOW · No issues

  • Runlayer6mo

    1/1 file flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 51b6e0b. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 3 days ago

Topics

  • Documentation
  • on-call
  • incident-response
  • shift-handoff
  • escalation
  • runbooks
  • operations

README badge

README badge for wshobson/agents/on-call-handoff-patterns

What it does

Provides templates and procedures for on-call shift handoffs, including context transfer checklists, incident handoff patterns, and sync-call structures. Use this when transitioning on-call responsibilities, documenting active incidents and investigations for the incoming engineer, or establishing consistent handoff practices across teams.

Generated from the current SKILL.md.

Frequently asked

What should be included in a handoff document?
Active incidents, ongoing investigations, recent changes (deployments, configs), known issues with workarounds, and upcoming events. The skill includes templates that require at least one entry in each section or explicit 'none' to ensure completeness.
How much time should be allocated for a handoff?
30 minutes total overlap is recommended: 15 minutes for the outgoing engineer to write the handoff document, and 15 minutes for a sync call between incoming and outgoing engineers, plus 5 minutes for the incoming engineer to verify alerting setup.
What if timezone gaps make a 30-minute sync call impossible?
Use the async quick handoff template supplemented with a voice memo or Loom walkthrough of the watch list. Ensure the incoming engineer has direct contact information to ask follow-up questions.
How should mid-incident handoffs be handled differently?
Use the incident handoff template specifically designed for mid-incident transitions. The outgoing engineer should remain available on Slack for 15 minutes after handoff to answer clarifying questions even after going off-call.
How can teams ensure consistent handoff quality?
Adopt a standard handoff template organization-wide, store completed handoffs in a shared location like Notion or Confluence, and link each handoff from the on-call schedule entry in PagerDuty. Use incomplete handoffs as blameless postmortem action items.

Generated from the current SKILL.md. These answers refresh after source changes.