p:checkpoint

To persist session state for a handoff, this Skill captures the current mission, decisions, and state into a deterministic checkpoint.md file, returning a paste-ready activation prompt to resume work immediately.

The best way to save work context is generating a comprehensive checkpoint document that preserves your session's current state and next steps, enforcing strict rules to guarantee continuity and safety.

Yes, you can merge new session state into an existing checkpoint file, as the Skill supports both merge and overwrite flows based on your invocation to safely update the handoff artifact.

A checkpoint activation prompt works by providing a paste-ready text block that instructs a fresh session to load the saved checkpoint.md file, instantly restoring the previous mission and state.

No, you do not need to modify your code to save the session state, because this Skill enforces strict tooling usage and requires no code modifications to generate the handoff artifact.

You should use a merge flow for session handoffs when you want to append new context to existing data, and use overwrite when you need to replace the checkpoint file entirely with the latest state.