memory-checkpoint

Context preservation saves detailed memory to external files before conversation summarization. Create a checkpoint to batch-update memory files (activeContext, progress, decisionLog, architect) and retain all decisions and project state across long sessions or interruptions.

Use checkpoints after completing major features, during long-running sessions (over 10 turns), or manually trigger them with 'checkpoint', '存檔', or '記一下'. This prevents critical project context from being lost during conversation summarization.

A checkpoint externalizes detailed memory to Memory Bank by batch-updating four memory files: activeContext (current state), progress (completed work), decisionLog (choices made), and architect (design notes), while preserving file paths and decisions.

Yes, checkpoints are applied automatically during long-running sessions exceeding 10 turns or triggered manually via command. This ensures memory preservation happens consistently without manual intervention at regular intervals.

The Skill requires a Memory Bank as the storage destination for checkpoint files. Set up your memory file structure (activeContext, progress, decisionLog, architect) before creating checkpoints to batch-update all required files successfully.