Name: on-call-handoff-patterns
Author: wshobson

Imported from wshobson/agents (plugins/incident-response/skills/on-call-handoff-patterns/SKILL.md) via skills.sh. Install upstream with npx skills add wshobson/agents --skill on-call-handoff-patterns. Copyright stays with the author.

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-classification — Classify and prioritize incidents that need to be included in the handoff document
postmortem-facilitation — Turn resolved incidents from the shift into structured postmortems

Install on-call-handoff-patterns and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "wshobson-agents-on-call-handoff-patterns", "kind": "skill", "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.", "publisher": "wshobson", "version": "1.0.0", "capabilities": { "domains": [ "hr" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "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." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/wshobson/agents", "path": "plugins/incident-response/skills/on-call-handoff-patterns/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/wshobson/agents/on-call-handoff-patterns", "key": "wshobson/agents/plugins/incident-response/skills/on-call-handoff-patterns/SKILL.md" } }, "instructions": "# On-Call Handoff Patterns\n\nEffective patterns for on-call shift transitions, ensuring continuity, context transfer, and reliable incident response across shifts.\n\n## When to Use This Skill\n\n- Transitioning on-call responsibilities\n- Writing shift handoff summaries\n- Documenting ongoing investigations\n- Establishing on-call rotation procedures\n- Improving handoff quality\n- Onboarding new on-call engineers\n\n## Core Concepts\n\n### 1. Handoff Components\n\n| Component | Purpose |\n| -------------------------- | ----------------------- |\n| **Active Incidents** | ", "cost": { "context_tokens": 759 } }

on-call-handoff-patterns

About