Can I use these patterns for asynchronous handoffs?

Absolutely. While synchronous syncs are preferred, the skill includes a 'Quick Handoff (Async)' template specifically designed for low-activity shifts or distributed teams working across time zones.

What is the recommended shift overlap for an on-call handoff?

This skill recommends a 30-minute overlap between shifts: 15 minutes for the outgoing engineer to prepare documentation and 15 minutes for a synchronous sync call to discuss active issues.

Does this skill include specialized templates for active outages?

Yes, it provides a specific 'Incident Handoff (Mid-Incident)' template designed for high-severity events where technical leadership must change while the incident is still being mitigated.

How does this help reduce on-call burnout?

By providing clear escalation triggers and structured checklists, it reduces the cognitive load on responders and prevents 'hero culture' by encouraging early escalation and documented support paths.

What core components should every handoff document include?

According to these patterns, every handoff should cover Active Incidents, Ongoing Investigations, Recent Changes (deploys/configs), Known Issues/Workarounds, and Upcoming Events.

On-Call Handoff Patterns

Name: On-Call Handoff Patterns
Author: as4584

byas4584

0•

分析と監視

Standardizes on-call shift transitions through structured templates, escalation procedures, and comprehensive documentation patterns to ensure operational continuity.

This skill provides a robust framework for managing on-call rotations and incident response transitions by offering a collection of industry-standard patterns and templates. It helps engineering teams maintain service reliability through structured shift summaries, mid-incident handoff protocols, and clear escalation workflows, ensuring that critical context regarding active investigations, recent deployments, and known issues is seamlessly transferred between responders. By following these established best practices, teams can reduce the risk of context loss, minimize MTTR (Mean Time To Recovery), and improve the overall developer experience during demanding on-call rotations.

主な機能

010 GitHub stars

02Clear escalation triggers and multi-tier communication guidelines

03Quick-reference CLI command patterns for rapid service health verification

04Structured 30-minute shift overlap protocols and sync meeting agendas

05Pre-shift, during-shift, and post-shift checklists for operational readiness

06Comprehensive shift handoff templates for detailed, async, and mid-incident scenarios

ユースケース

01Maintaining continuity during long-running investigations of intermittent production issues

02Transitioning weekly on-call responsibilities between primary and secondary responders

03Establishing standardized communication protocols during high-severity (SEV1/SEV2) incidents

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add as4584/antigravity-skills on-call-handoff-patterns

For use in Claude.ai and ChatGPT

主な機能

010 GitHub stars

02Clear escalation triggers and multi-tier communication guidelines

03Quick-reference CLI command patterns for rapid service health verification

04Structured 30-minute shift overlap protocols and sync meeting agendas

05Pre-shift, during-shift, and post-shift checklists for operational readiness

06Comprehensive shift handoff templates for detailed, async, and mid-incident scenarios

ユースケース

01Maintaining continuity during long-running investigations of intermittent production issues

02Transitioning weekly on-call responsibilities between primary and secondary responders

03Establishing standardized communication protocols during high-severity (SEV1/SEV2) incidents