# Write A Runnable Handoff Note

> Use when ending a shift or session mid-task. Leave a handoff another operator can execute end to end without reading your whole history.

- Skill: `jiayaoqijia/write-a-runnable-handoff-note` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx get-skill add jiayaoqijia/write-a-runnable-handoff-note`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jiayaoqijia/write-a-runnable-handoff-note/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: jiayaoqijia (https://skillmd.com/u/jiayaoqijia)
- Updated: 2026-11-12
- Page: https://skillmd.com/skills/jiayaoqijia/write-a-runnable-handoff-note

---


# Write a runnable handoff note

A handoff is only useful if the next person can act from it alone. History may be gone; the note must carry goal, state, ordered commands, and open decisions.

## Procedure

1. State the goal and the current state in two lines.

2. List what is done and verified, each with the command that proves it.

3. List what is left as ordered next steps, each with the exact command.

4. Name every open decision and the default you will take if no one answers.

5. List running processes, ports, and temp files (`lsof -i :8080`), so the next person knows the environment.

6. Reference credentials by location, never by value — point at the secret store.

7. Add the one thing that would waste an hour if missed.

## Pitfalls

- "See my earlier messages" is not a handoff; the history may be unavailable.
- Leaving a background process running with no note blocks the next person.
- Steps without commands invite improvisation and drift.
- Handing off mid-decision with no default causes a silent stall.
- Copying secrets into the note leaks them; reference the vault instead.

## Verification

    ls -l HANDOFF.md && grep -c "^[0-9]\." HANDOFF.md   # ordered steps present

Hand off goal, state, ordered commands, open decisions, and running services.

