Claude Cursor Skill

on-call-handoff-patterns

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 captur

LLM Mart · 0 points · 15 views 0 listing impressions 0 install-command copies
Download wshobson-agents-plugins_incident-response_skills_on-call-handoff-patterns-46891e7.zip · 4 KB

Install

skills CLI npx skills add https://github.com/wshobson/agents/tree/main/plugins/incident-response/skills/on-call-handoff-patterns
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install wshobson-agents@llmmart
Git git clone https://github.com/wshobson/agents.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole wshobson/agents collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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

Files (agents)
  • references
    • details.md 6.1 KB
      Loading…
  • SKILL.md 3.6 KB
    ---
    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](../incident-runbook-templates/SKILL.md) — Runbooks for the incidents that are handed over mid-response
    - [postmortem-writing](../postmortem-writing/SKILL.md) — Turn resolved incidents from the shift into structured postmortems
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.