# Shift handover

> Hand over a line so the next shift starts informed rather than discovering.

- Skill: `vstorm-co/shift-handover` (Agent Skill)
- Install (CLI): `npx skillmds@latest add vstorm-co/shift-handover`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vstorm-co/shift-handover/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: vstorm-co (https://skillmd.com/u/vstorm-co)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/vstorm-co/shift-handover

---


# Handing over a shift

The incoming shift needs what will affect them, not a diary of what happened.

## Cover, in this order

**Safety** — anything unsafe, isolated, or with a permit open.
**Running state** — what is running, what is down, what is degraded and how.
**In progress** — jobs part-complete, and where exactly they stopped.
**Watch items** — the machine behaving oddly, the material batch running out of
spec, the temperature drifting. This is the section that matters.
**Outstanding** — work orders raised, parts on order, escalations open.
**Quality** — holds, deviations, anything awaiting disposition.

## Write watch items concretely

"Line 3 infeed jamming roughly every 40 minutes since 14:00, cleared manually,
maintenance notified at 15:20" is a handover. "Line 3 playing up" is not.

## Always state

What the next shift must do first, and anything with a time on it.

## Never

Leave a verbal-only item, close a watch item because it stopped happening
without saying when, or hand over an open permit without naming its holder.