Save a resumable checkpoint of the current operational context to `.planning/checkpoints/` — YAML frontmatter + prose. Call before `/clear` or any long-running Task dispatch.
Persist a resumable snapshot of the current session's operational context so
work can continue in a fresh Claude Code session (post-/clear) without losing
phase/plan position, open questions, or resume-hint file references.
$ARGUMENTS — a short human-readable label (slug). Required. Always quote it
on Windows Git-Bash (P15, WIN-01).Delegate serialization to the qsd CLI so the Skill itself stays side-effect-free:
MSYS_NO_PATHCONV=1 node "$HOME/.claude/qsd/bin/qsd-tools.cjs" checkpoint save --label "$ARGUMENTS"
The CLI writes .planning/checkpoints/<YYYY-MM-DDTHH-MM-SS>-<label>.md with
full YAML frontmatter (schema_version: 1, generator: [email protected], pointers,
state, budget, intel_read) plus four prose sections: Narrative, Next Action,
Resume Hints, Open Questions.
The CLI also atomically refreshes .planning/checkpoints/LATEST.json (a
JSON pointer file — never a symlink, Windows-restricted, JANITOR-03).
Run this before /clear. The hook harness will surface a warning at 70%
and a blocking notice at 85% context pressure (UserPromptSubmit hook), but the
user remains in charge of when to snapshot.
MSYS_NO_PATHCONV=1 prefix prevents $HOME and forward-
slash paths from being mangled (WIN-05).LATEST.json is a plain file..planning/logs/qsd-hooks.log records every hook-fired
save via PreToolUse; this skill is user-initiated and logs to stdout only.