checkpoint

Trigger the checkpoint workflow, which walks the conversation message by message, builds a pass table of substantive points, and saves everything not already in files. After your confirmation, it updates project artifacts and marks the current step with [ACTIVE].

It updates three categories: project artifacts (plan.md, topic files), relevant documentation (README, PRODUCT.md, COMPONENT.md), and target artifacts (code, instructions, specs). The exact files depend on the project structure determined during the walkthrough.

It flags a compression risk section in the output when the beginning of a long conversation may have been lost. If important early decisions were not saved along the way, the report notes what might be missing so you can reconstruct it.

Yes. The workflow stops after presenting the conversation pass table and packing plan, and only proceeds to saving after your explicit confirmation. You can edit the plan and have it re-presented before any writes occur.

It relies on the agent's judgment of what is substantive, so ephemeral context or implicit reasoning may not be captured. It also requires existing project files to be readable, and cannot recover content already lost to context compression.