---
name: handoff
description: Produce a clean handoff document at the end of a work session or project stage, capturing decisions made, open items, assumptions and the exact next step, so the next person (or your next chat) starts sharp instead of cold. Use before handing a project to a PM, a colleague or a fresh session.
---

# Hand Off

## What it does
Compresses everything decided and everything still open into a short, structured handoff so the receiver needs no verbal briefing.

## When to use
- Handing a project or stage from architect to PM.
- Ending a long chat you will resume later, or passing work to a colleague.

## Instructions
1. Review the session or project state.
2. Separate decided from open. Record who decided and why for the non-obvious calls.
3. State the single most important next action first, unambiguously.
4. List assumptions and risks the receiver must not lose.

## Output format
- Project and stage summary
- Decisions made (with rationale for the non-obvious ones)
- Open items and who owns each
- Assumptions and risks
- The next step, stated as one clear action

## The one mistake to avoid
Do not hand off decisions dressed as facts. Anything assumed must be labelled, so the receiver can challenge it rather than inherit it blindly.