# On Call Handoff Patterns > Domina los handoffs de turno de guardia con transferencia de contexto, procedimientos de escalado y documentación entre ingenieros. Fuente: https://skillsagentes.com/skills/wshobson/agents/on-call-handoff-patterns Markdown: https://skillsagentes.com/skills/wshobson/agents/on-call-handoff-patterns.md Repositorio: https://github.com/wshobson/agents Autor: wshobson Licencia: MIT Actualizado: hace 4 meses Coste de contexto: 156 tok instalada, 937 tok al activarse, 2.5k tok con todos los archivos del bundle Bundle: 2 archivos, 10 KB Permisos que pide: ninguno declarado ## Instalación Un skill son archivos markdown: los mismos archivos valen para cualquier agente y lo único que cambia es el directorio de destino, es decir la bandera `--agent`. Añade `-g` para instalarlo en todos los proyectos de la máquina. ```bash # Claude Code npx -y skills add wshobson/agents --skill on-call-handoff-patterns --agent claude-code # Cursor npx -y skills add wshobson/agents --skill on-call-handoff-patterns --agent cursor # Codex npx -y skills add wshobson/agents --skill on-call-handoff-patterns --agent codex # Gemini CLI npx -y skills add wshobson/agents --skill on-call-handoff-patterns --agent gemini # Windsurf npx -y skills add wshobson/agents --skill on-call-handoff-patterns --agent windsurf # Cline npx -y skills add wshobson/agents --skill on-call-handoff-patterns --agent cline ``` ## Qué hace - Proporciona plantillas y estructura para documentos de handoff de guardia (incidentes activos, investigaciones, cambios recientes) - Define la mecánica de tiempo para la transición entre turnos (overlap de 30 min) - Ofrece soluciones de troubleshooting para handoffs incompletos, remotos o en medio de un incidente ## Cuándo usarla - Transicionar responsabilidades de guardia entre ingenieros - Escribir un resumen de turno que capture incidentes activos e investigaciones - Hacer handoff en medio de un incidente para transferir el rol de incident commander - Incorporar a un nuevo ingeniero a la rotación de guardia por primera vez ## Qué la activa - "Ayúdame a escribir el resumen de handoff para el próximo turno de guardia" - "Necesito transferir el rol de incident commander a otro ingeniero" - "¿Cómo estructuro el onboarding de un nuevo ingeniero a la rotación on-call?" ## Antes de instalar - Consultar references/details.md para las plantillas completas y ejemplos detallados. ## Archivos - SKILL.md — 4 KB - references/details.md — 6 KB ## SKILL.md Reproducido tal cual desde wshobson/agents bajo MIT. Esta sección es el documento original y está en inglés. # 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 ## Dónde encaja - Categoría: [DevOps e infraestructura](https://skillsagentes.com/categorias/devops-infraestructura.md) — Despliegues, contenedores, IaC y flujos de gestión de incidentes. - Creador: [wshobson](https://skillsagentes.com/creators/wshobson.md) — 183 skills en el directorio - [Todas las skills](https://skillsagentes.com/skills.md) - [Ranking de instalaciones](https://skillsagentes.com/ranking.md) --- Skills Agentes · [Índice de páginas en markdown](https://skillsagentes.com/sitemap.md) · [Inicio](https://skillsagentes.com/index.md)