checkpoint
save restartable work-state before stepping away or handing off
Writes down where the work stands so someone else, or you tomorrow, can start cold: what is done, the exact next action, and anything that exists only in this conversation.
structure generate skill checkpointSkill — checkpoint
Invoke in any agent conversation with /checkpoint. The steps below are a starting opinion, and
they are what runs — edit them until they describe how this company actually hands work over.
When to use. Before stepping away mid-task, before handing work to someone else, and any time the only copy of what is going on is this conversation.
Steps.
- Say where you are in one sentence — the task, not the tool.
- List what is done and what is not, in the order it happened.
- Write the exact next action, specific enough to start on cold: the command to run, the person to ask, the file to open.
- Record what exists only in this conversation — a decision, a dead end, something tried that did not work. This is the part that is otherwise lost.
- Name the files touched, by path, and the branch they are on.
- Save it under
memory/checkpoints/as<date>-<slug>.md, and say where you put it.
---
type: skill
name: checkpoint
description: save restartable work-state before stepping away or handing off
standing: draft
owner: "{{owner}}"
updated: "{{date}}"
---
# Skill — checkpoint
_Invoke in any agent conversation with `/checkpoint`. The steps below are a starting opinion, and
they are what runs — edit them until they describe how this company actually hands work over._
**When to use.** Before stepping away mid-task, before handing work to someone else, and any time
the only copy of what is going on is this conversation.
**Steps.**
1. Say where you are in one sentence — the task, not the tool.
2. List what is done and what is not, in the order it happened.
3. Write the exact next action, specific enough to start on cold: the command to run, the person to
ask, the file to open.
4. Record what exists only in this conversation — a decision, a dead end, something tried that did
not work. This is the part that is otherwise lost.
5. Name the files touched, by path, and the branch they are on.
6. Save it under `memory/checkpoints/` as `<date>-<slug>.md`, and say where you put it.
type: skill
name: checkpoint
about: "Writes down where the work stands so someone else, or you tomorrow, can start cold: what is done, the exact next action, and anything that exists only in this conversation."
version: "0.1.0"