---
name: ccd-checkpoint
description: This skill should be used as a lightweight mid-session checkpoint to snapshot progress without full wrap-up — runs ccd checkpoint for a fast delta-aware status that carries the shared continuity foundation (session boundary, context health, behavioral drift, handoff refresh candidates) but omits handover-only evaluation buckets, memory candidates, repo native checks, and approval steps
---

# CCD Checkpoint

Lightweight mid-session checkpoint. Captures a fast delta-aware snapshot of session state — session boundary, context health, behavioral drift, and handoff refresh candidates — but omits handover-only surfaces (evaluation buckets, memory candidates, repo native checks, approval steps). For full wrap-up, use `/ccd-radar`.

## When to use

- **Checkpoint (`ccd checkpoint`):** fast, read-mostly. Good for mid-session progress checks, retry triage, deciding continue vs wrap up.
- **Radar (`ccd handover`):** full evaluation. Use for session wrap-up and handoff drafting.

## Gotchas

- **Strict subset:** `ccd checkpoint` omits `evaluation`, `approval_steps`, `approval_intents`, `repo_native_checks`, and `candidate_updates.memory` — they are **absent**, not empty.
- **Shared safety contract:** start from read-only inspection, keep machine-readable stdout clean, prefer compact output.
- **Stale worktree binaries:** never fall back to `./target/debug/ccd`.
- **Recovery is CLI-owned:** persist via `ccd recovery write` (stdin JSON), not by editing `state.db`.

## Run checkpoint

1. Resolve CLI: `CCD_BIN` → `which ccd` → `$HOME/.ccd/bin/ccd` → `$HOME/.cargo/bin/ccd`. Do **not** fall back to `./target/debug/ccd`.
2. If unavailable, stop and report.
3. Run:
   ```bash
   ccd --output json checkpoint \
     --since-session current \
     --memory-depth metadata \
     --fields command,mode,schema_version,ok,delta_warning,session_delta,projection_telemetry,work_stream_decay,session_boundary,context_health,behavioral_drift,candidate_updates,git,checkout_state,session_state,escalation,handoff \
     --path .
   ```

## Interpret results

- **Session boundary:** surface `session_boundary.action` and `.summary` as primary recommendation.
- **Context health:** if `band` is `risky`/`critical`, recommend wrapping up via `/ccd-radar`.
- **Work-stream decay:** if `status` is `warning`/`critical`, treat as wrap-up signal.
- **Handoff currency:** note whether handoff is aligned with session work.

Based on `session_boundary.action`: `continue` → resume work; `refresh`/`wrap_up` → run `/ccd-radar`; `stop` → run `/ccd-radar` immediately.

For detailed field descriptions and recovery snapshot format, load `references/checkpoint-details.md`.
