checkpoint
Checkpoint
Use only when explicitly invoked. Capture the requested scope in conversation unless the user requests a saved file.
Establish the current state
Identify the outcome and sources. Inspect each repository's identity, branch, HEAD, dirty state, and relevant files. For other work, identify the authoritative document or tracker and observed state.
Reconcile conversation claims with current evidence. Distinguish intended, attempted, implemented, and verified outcomes. Plans and agent claims do not prove completion.
Include only material decisions, completed outcomes, outstanding work, blockers, verification, and the next action. Preserve unrelated dirty changes.
Verification evidence
Identify each check's command, result, and covered revision or working-tree state. Use available results or saved evidence; do not rerun expensive checks solely for a checkpoint.
Flag results invalidated by later relevant changes. When the tested state is unknown, label results historical and current verification unknown. List unconfirmed or unrun required checks; never report unavailable evidence as passed.