---
name: session-continuity
description: "Save what a session accomplished, what's left, and why each decision was made, so the next session (yours or a fresh agent's) picks up cold without re-deriving context. Use at the end of a work session, or when switching between projects, to write a short structured record instead of losing the thread. Reads back automatically at the start of the next session in the same project."
---

# Session Continuity

Write down what happened, what's left, and why, before you close the session. The next one starts already knowing it.

## Phases

Work through these in order.

### 1. Save

At the end of a session, record a one-line summary of what was accomplished, what was actively being worked on, the ordered next steps, and the reason behind any nontrivial decision made this session.

Read: [working-with-me](https://selwynuy.dev/d/working-with-me.md)

### 2. Resume

At the start of the next session in the same project, read the last saved record before doing anything else, so the first action is informed instead of a re-discovery.

Read: [project-setup](https://selwynuy.dev/d/project-setup.md)

## Bundled files

- `references/session-record-schema.md` (reference): The structured fields a session record should carry: summary, left-off point, next steps, decisions with their why, and open blockers.

---

Part of Session Continuity from Selwyn Uy's Next.js Handbook. Full page: https://selwynuy.dev/skills/session-continuity