Handover note

Shorten an operational handover to the state the next person must act on.

Condense the supplied handover into instructions for the person taking over the work. Use this for ongoing human operations or temporary cover, not an agent's technical context history.

Lead with the coverage period and current state. Retain unfinished work, the next required action, the exact deadline and time zone, and the person responsible. Include where to find the working record. Keep conditions that determine whether to act, wait, or escalate, plus any action already taken that must not be repeated.

Separate routine checks from exceptions needing attention. Distinguish acknowledged requests from completed tasks. Keep access constraints and contact details necessary for the handover, but do not reproduce passwords or secret tokens.

Use short sections for Current state, To do, and If needed. Remove the outgoing person's activity narrative. Do not turn the handover into a new plan or invent authority, contacts, deadlines, or escalation rules.

Example

Fulfillment desk cover

Before 136 words

Nia is covering the fulfillment desk for Omar on Friday, 12 June, from 09:00 to 17:00 UTC. The morning pickup has already left, so it must not be booked again. Order F-218 is packed but is waiting for the customer to confirm the delivery address. Nia should check the shared fulfillment inbox at 11:00 UTC. If the confirmation has arrived, Nia should update F-218 in the dispatch board and book it for the 14:00 UTC pickup. If there is no confirmation by 12:00 UTC, Nia should tell the customer that dispatch is on hold and leave the parcel in shelf B3. Omar has already sent the address request. The courier portal login is available through the team's password manager. Any courier booking failure should go to desk lead Imani. Omar spent the morning checking packing labels.

After 87 words

Cover: Nia for Omar, Friday 12 June, 09:00–17:00 UTC. Current state: Morning pickup has left; do not rebook. F-218 is packed on hold for address confirmation. Omar already requested it. To do: Check the shared fulfillment inbox at 11:00 UTC. If confirmed, update F-218 in the dispatch board and book the 14:00 UTC pickup. If unconfirmed by 12:00 UTC, tell the customer dispatch is on hold; leave the parcel on shelf B3. If needed: Courier login is in the team password manager. Send booking failures to Imani.

Examples illustrate the method. They do not measure model output.

Files and sources

prompt.txt Complete prompt as plain text.
SKILL.md The same prompt with a skill header.
llms.txt (JSON) Prompt, metadata, example, and sources.
LICENSE MIT license text.

An original sho.rten.it skill. Source notes.