---
name: session-handoff-document
description: "Compresses a working session into a handoff another person or agent can pick up cold, pointing to files and artifacts by path. Use when a long working session must be summarised so another person or agent can continue without the history. Do not use for summarising a meeting for stakeholders or writing project documentation. Related topics: AI, productivity."
---

# Session Handoff Document

Compresses a working session into a handoff another person or agent can pick up cold, pointing to files and artifacts by path.

## When to use

Use this skill when a long working session must be summarised so another person or agent can continue without the history. Do not use it for summarising a meeting for stakeholders or writing project documentation.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Write a three-sentence opener stating the goal and where the work stands now.
3. List completed work by artifact path instead of pasting content.
4. Record each decision with its reason and each failed attempt with why it failed.
5. List open questions and blockers, then state the first concrete next action if it is known.
6. Trim to one page with the most important item first.

## Inputs

- **Session goal** (free text, e.g. "What we set out to do")
- **What happened** (longer free text)
- **Artifacts** (longer free text)
- **Who picks it up** (choose one: A teammate, A fresh agent session, Me later)
- **Next step known** (choose one: Yes, No)

## Output

A one-page handoff with sections for state, done, decisions, failed attempts, open questions and next action, every artifact given as a path.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Session Handoff Document

Write a handoff for the work done in this session.

- Session goal: {{Session goal}}
- What happened: {{What happened}}
- Artifacts: {{Artifacts}}
- Who picks it up: {{Who picks it up}}
- Next step known: {{Next step known}}

Write for a reader with zero memory of the session. Open with the goal and current state in three sentences. Then list what is done, with the path of each artifact instead of pasted content. Record decisions made and the reason for each, so nobody reopens them by accident. List what was tried and failed, which saves the next person the same trip. Give open questions and blockers. If the next step is known, state it as the first concrete action with the file and command; otherwise list the likely options. Do not paste long code or logs; reference them by path. Keep it under one page and put the most important thing first.

## Pitfalls

- Pasting long logs into the handoff, which buries the state the reader needs.
- Leaving out failed attempts, so the next person repeats them.
- Writing in shorthand only the author understands.
