Menu
Use when a session reaches a durable boundary that future work may need to resume, review, or branch from.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when a project has no suitable confirmed member, a user asks to discover or import reusable experts, or repeated prior-session needs suggest a member candidate may exist.
Use when a user gives durable constraints or rejected directions, a session reaches a stable decision, compact/prune pressure appears, or future work may need to resume or branch from this point.
Use when a consequential next step depends on what happened earlier in the session and may need an independent checkpoint-derived reviewer, checker, oracle, reflector, or planner.
Use when a consequential next step depends on earlier session context and may need an independent checkpoint-derived reviewer, checker, oracle, reflector, or planner.
| name | context-tree-save-checkpoint |
| description | Use when a session reaches a durable boundary that future work may need to resume, review, or branch from. |
Save a checkpoint when the session reaches a boundary that later work may need.
Use this when:
Provide only boundary metadata:
label: <short boundary name>
purpose: <why future work may need this boundary>
target refs:
- <optional file/report/spec/diff ref>
Do not summarize the session yourself. Do not choose which context matters. Context Tree owns context recovery and writeback.