---
description: Review verified work and prepare a continuity checkpoint.
---
Wrap up this work. Focus: $ARGUMENTS

Review the latest objective, changed files, checks actually run, durable decisions,
open tasks, and one next action. Use the memory-tasks skill to update relevant
existing tasks in the approved write project when warranted; do not create
lifecycle-event notes or duplicate decisions in the checkpoint folder.

Give a concise handoff and ask the user to run /bm-checkpoint with the desired
focus. Explain that it synthesizes eligible public session text with the active
model, can incur model charges, and saves to the configured project. A text reply
cannot invoke that command. Do not claim the checkpoint was saved until a
confirmed receipt exists and its returned note has been read back.