スキル on-call-handoff-patterns
📋

on-call-handoff-patterns

安全

Streamline On-Call Shift Handoffs

こちらからも入手できます: wshobson

Reduce incident response gaps during shift changes with structured handoff templates and procedures. This skill provides documented patterns for transferring context, ongoing investigations, and escalation procedures between on-call engineers.

対応: Claude Codex Code(CC)
🥉 75 ブロンズ
1

スキルZIPをダウンロード

2

Claudeでアップロード

設定 → 機能 → スキル → スキルをアップロードへ移動

3

オンにして利用開始

テストする

「on-call-handoff-patterns」を使用しています。 Create a shift handoff document for platform team

期待される結果:

A markdown document with sections for active incidents (none currently), ongoing investigations with ticket links, recent deployment table, known issues with workarounds, upcoming maintenance windows, escalation contacts, and verification checklists for both outgoing and incoming engineers.

「on-call-handoff-patterns」を使用しています。 Generate escalation guidelines for our team

期待される結果:

A structured guide covering immediate escalation triggers (SEV1, data breach, 30-minute diagnosis timeout), when to consider escalation (multi-team issues, expertise gaps), and the escalation process (page appropriate contact, provide context, stay engaged until acknowledgment).

セキュリティ監査

安全
v1 • 2/24/2026

This skill is a documentation-only resource providing on-call handoff templates and best practices. All 39 static analysis findings are false positives: the 'external_commands' detections are markdown code blocks showing example commands (not actual execution), 'network' detections are reference URLs in documentation templates (not network calls), and other findings misinterpret markdown content as code. No executable code or security risks exist.

1
スキャンされたファイル
456
解析された行数
0
検出結果
1
総監査数
セキュリティ問題は見つかりませんでした
監査者: claude

品質スコア

38
アーキテクチャ
100
保守性
87
コンテンツ
50
コミュニティ
100
セキュリティ
100
仕様準拠

作れるもの

Platform Team Shift Handoffs

Create consistent, comprehensive handoff documents when transitioning on-call responsibility between engineers on a weekly rotation.

Incident Response Continuity

Maintain context and momentum during ongoing incidents when the on-call engineer's shift ends mid-resolution.

New On-Call Engineer Onboarding

Provide structured guidance and checklists for engineers new to on-call rotations to ensure they are prepared.

これらのプロンプトを試す

Basic Shift Handoff Document 
Create a shift handoff document for my platform team. Outgoing engineer is @alice, incoming is @bob. Include sections for active incidents, ongoing investigations, recent deployments, known issues, and upcoming events. We use Grafana for dashboards and have a weekly on-call rotation.
Quick Async Handoff 
Generate a brief async handoff summary. No active incidents. One ongoing investigation into API timeouts during backup window (ticket ENG-1234). Major release scheduled for tomorrow. Keep it under 10 lines.
Mid-Incident Handoff 
Create an incident handoff for an ongoing payment service degradation. Started 45 minutes ago, currently at SEV2. Error rate dropped from 40% to 15% after scaling pods. Root cause appears to be memory pressure from traffic spike. Incoming engineer needs to monitor for next 30 minutes.
On-Call Preparation Checklist 
Generate a pre-shift checklist for a new engineer starting their first on-call rotation. Include access verification, alerting setup, knowledge refresh, and environment preparation. Our stack includes Kubernetes, PostgreSQL, Redis, and we use PagerDuty and Slack.

ベストプラクティス

  • Schedule 30-minute overlap between shifts for synchronous handoff calls
  • Document all active and recent incidents with investigation notes and next steps
  • Verify alerting and access before each shift starts using the pre-shift checklist
  • Escalate early when uncertain rather than struggling alone for extended periods

回避

  • Skipping synchronous handoff and relying only on async documentation
  • Disappearing at shift end without confirming incoming engineer has context
  • Ignoring alerts during shift even if they seem minor or intermittent
  • Attempting to resolve complex issues alone rather than escalating for help

よくある質問

How long should a shift handoff take?
Plan for 30 minutes total: 15 minutes for the outgoing engineer to write the handoff document, and 15 minutes for a synchronous sync call between outgoing and incoming engineers. The incoming engineer should review the document before the call.
What if an incident is active when my shift ends?
Use the incident handoff template to transfer context. Stay on the sync call until the incoming engineer confirms they understand the current state, mitigation steps, and escalation path. Do not leave until they explicitly acknowledge ownership.
Should we do async or synchronous handoffs?
Use both. Async documentation provides a written record, but synchronous calls prevent context loss. The combination ensures clarity and allows real-time questions. Async-only handoffs frequently miss critical context.
When should I escalate an incident?
Escalate immediately for SEV1 incidents, suspected data breaches, or if you cannot diagnose the issue within 30 minutes. Also escalate when the issue spans multiple teams or requires expertise you do not have.
What should be in a handoff document?
Include active incidents, ongoing investigations with status and next steps, recent deployments and configuration changes, known issues with workarounds, upcoming maintenance or releases, and escalation contacts. Add a quick reference section for common commands and dashboard links.
How do I prepare for my first on-call shift?
Complete the pre-shift checklist: verify VPN and tool access, confirm PagerDuty scheduling, install and test alerting apps, review recent incidents and runbooks, and ensure your laptop and phone are charged. Identify a backup contact if traveling.

開発者の詳細

作成者

sickn33

ライセンス

MIT

リポジトリ

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/on-call-handoff-patterns

参照

main

ファイル構成

📄 SKILL.md