qsd-save-checkpoint

To save a resumable checkpoint, delegate serialization to the qsd CLI with a descriptive label. This writes a snapshot with full YAML frontmatter, including phase position and resume hints, to the .planning/checkpoints directory.

A session checkpoint captures phase and plan position, open questions, budget, and resume-hint file references. It writes this state with full YAML frontmatter into a checkpoint file to ensure no operational context is lost.

Saving a checkpoint requires the qsd CLI to handle serialization, keeping the Skill itself side-effect-free. No other dependencies or components are needed, as the process atomically updates a LATEST.json pointer without creating symlinks.

You should create a session checkpoint before a clear during high context pressure or when starting a long-running multi-step task. This user-driven mitigation ensures your phase position and open questions survive a Claude Code restart.

The system atomically updates a LATEST.json file in the .planning/checkpoints directory after saving. This file acts as a single pointer to the latest checkpoint, enabling quick and seamless resumption without scanning files.

Yes, checkpoint session management writes full YAML frontmatter with pointers and atomically updates LATEST.json to track state. It avoids creating symlinks entirely, relying on the qsd CLI for clean serialization during multi-step tasks.