On Call Handoff Patterns
Unverified●25/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add on-call-handoff-patternsWho is stuck, and on what
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 whole source
Frontmatter — 2 properties
| 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. |
| 1 | --- |
| 2 | name: on-call-handoff-patterns |
| 3 | 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.B1 — Line is 635 characters — unreadable by eye |
| 4 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 5 | |
| 6 | # On-Call Handoff Patterns |
| 7 | |
| 8 | Effective patterns for on-call shift transitions, ensuring continuity, context transfer, and reliable incident response across shifts. |
| 9 | |
| 10 | ## When to Use This Skill |
| 11 | |
| 12 | - Transitioning on-call responsibilities |
| 13 | - Writing shift handoff summaries |
| 14 | - Documenting ongoing investigations |
| 15 | - Establishing on-call rotation procedures |
| 16 | - Improving handoff quality |
| 17 | - Onboarding new on-call engineers |
| 18 | |
| 19 | ## Core Concepts |
| 20 | |
| 21 | ### 1. Handoff Components |
| 22 | |
| 23 | | Component | Purpose | |
| 24 | | -------------------------- | ----------------------- | |
| 25 | | **Active Incidents** | What's currently broken | |
| 26 | | **Ongoing Investigations** | Issues being debugged | |
| 27 | | **Recent Changes** | Deployments, configs | |
| 28 | | **Known Issues** | Workarounds in place | |
| 29 | | **Upcoming Events** | Maintenance, releases | |
| 30 | |
| 31 | ### 2. Handoff Timing |
| 32 | |
| 33 | ``` |
| 34 | Recommended: 30 min overlap between shifts |
| 35 | |
| 36 | Outgoing: |
| 37 | ├── 15 min: Write handoff document |
| 38 | └── 15 min: Sync call with incoming |
| 39 | |
| 40 | Incoming: |
| 41 | ├── 15 min: Review handoff document |
| 42 | ├── 15 min: Sync call with outgoing |
| 43 | └── 5 min: Verify alerting setup |
| 44 | ``` |
| 45 | |
| 46 | ## Templates and detailed worked examples |
| 47 | |
| 48 | Full template library and detailed worked examples live in `references/details.md`. Read that file when you need the concrete templates. |
| 49 | |
| 50 | ## Troubleshooting |
| 51 | |
| 52 | **Incoming engineer misses a critical issue because the handoff document was incomplete.** |
| 53 | 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. |
| 54 | |
| 55 | **A 30-minute sync call is not possible due to timezone gaps.** |
| 56 | 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. |
| 57 | |
| 58 | **The incoming engineer inherits a mid-incident and is immediately overwhelmed.** |
| 59 | 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. |
| 60 | |
| 61 | **On-call handoff documents are inconsistently formatted across teams.** |
| 62 | 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. |
| 63 | |
| 64 | **Incoming engineer cannot verify their alerting is working before the outgoing engineer logs off.** |
| 65 | 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. |
| 66 | |
| 67 | ## Related Skills |
| 68 | |
| 69 | - [incident-classification](../../skills/incident-classification/SKILL.md) — Classify and prioritize incidents that need to be included in the handoff document |
| 70 | - [postmortem-facilitation](../../skills/postmortem-facilitation/SKILL.md) — Turn resolved incidents from the shift into structured postmortems |
| 71 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Paper Poster (HTML): measurement-gated poster generationDEFAULT poster pipeline — build an academic conference poster (ICML/NeurIPS/ICLR/CVPR/...) as a single HTML/CSS file with measurement-driven hard gates, real paper figures, a two-hue design-token system, and print-ready PDF via headless Chromium. Use when the●····●36/40Brand Monitoring 📡Brand monitoring tool for tracking mentions across social media platforms. Monitor Reddit, Google News, YouTube, and DuckDuckGo for brand mentions. Includes sentiment analysis, trend tracking, crisis detection, and competitor comparison. No API key required fo◐····●34/40Spark Memory & Thermal OpsManage unified memory and thermals during long-running ML jobs on NVIDIA DGX Spark. Use when planning memory headroom for a training run on GB10, when a job OOMs on unified memory, or when monitoring temperature and power during multi-hour training.◐····●32/40Secrets ManagementImplement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.◐····●32/40