on-call-handoff-patterns
- Use it when:
- Your on-call shift is ending, you're handing over mid-incident, or you're setting up or improving a team's handoff routine.
- It does:
- Has the outgoing engineer cover five things: active incidents, ongoing investigations, recent changes, known issues and upcoming events.
- You get:
- A handoff document from one of three Markdown templates: a full shift handoff, a quick async one or a mid-incident handoff.
- Timing:
- A 30-minute overlap: the outgoing engineer writes for 15 minutes, then both join a 15-minute sync call.
TL;DR
A handoff routine for human on-call rotations that the agent helps write. The SKILL.md names what every handoff carries and how to time it: the outgoing engineer writes the document and holds a sync call, and the incoming engineer reviews it, joins the call and checks their alerting works. Its troubleshooting covers incomplete handoffs (no section may stay empty: write "none"), time zones that rule out a call (use the async template plus a recorded walkthrough), inheriting an incident mid-response (the outgoing engineer stays reachable on Slack for 15 minutes), inconsistent formats across teams, and confirming alerts with a test alert before the overlap ends. The reference file's templates: a full shift handoff with incidents, investigations with their tickets, issues resolved this shift, deployments and config changes, workarounds, upcoming events, escalation contacts, common commands, links and checklists for both engineers; a short async handoff with a TL;DR and a watch list; and an incident handoff with current state, what's known, what's been done, next steps, key people and communication status. It points to incident-runbook-templates and postmortem-writing.
Summarizes the skill at 4bde316.
npx skills add https://github.com/wshobson/agents --skill on-call-handoff-patterns skills.sh pageSource on GitHubAll skills from wshobson/agents
- Total Downloads
- 10,700 on skills.sh, Nov 9, 2026
- Repo stars
- 42,334 wshobson/agents
- First seen
- Jan 20, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 177 |
| Sep 28 | 205 |
| Oct 5 | 271 |
| Oct 12 | 218 |
| Oct 19 | 182 |
| Oct 26 | 181 |
| Nov 2 | 166 |
| Nov 9 | 153 |
| Category |
Deploy, provision, observe and debug cloud apps. Articles, docs, internal comms, research write-ups and prose that doesn't read as generated. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
Knowledge and rules the agent applies while it works: best practices, design principles, API references. |
| Effect |
Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code. |
| Needs |
Instructions only. Works in any agent that supports skills. |
| Publisher |
Everyone else. Unverified vendor claims default to community. |
| Topics |
SKILL.md
From wshobson/agents at 4bde316. Checked daily, last changed Nov 6, 2026.
Frontmatter
name: on-call-handoff-patterns
description: 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.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
- incident-runbook-templates — Runbooks for the incidents that are handed over mid-response
- postmortem-writing — Turn resolved incidents from the shift into structured postmortems