digest

/digest

Captures the meaningful state of the current session to state/digests/latest.md. The Scripts/sessionstart-digest.ps1 hook reads it on the next session start and emits it as additionalContext for the model. Pairs with Scripts/precompact-digest.ps1 which provides a metadata-only fallback when /digest isn't invoked before auto-compaction.

When to run

• Before compaction is imminent (context feels >60% full).
• At a natural breakpoint — after finishing a feature, before a risky operation, before handing off to another agent.
• Before launching long-running background work so the digest captures what you expect that work to do.

Do NOT invoke on every message or tool call. The digest is for meaningful state changes, not transcript capture.

What it captures

Git metadata is gravy. The value is in the content sections + the success_criteria field (Karpathy R4: "task complete != goal achieved").

---
schema_version: 1
session_id: <session_id, propagated from PreCompact stdin when known>
written_at: <RFC3339 UTC>
trigger: digest-skill
branch: <git branch>
head_sha: <short SHA>
head_subject: <commit subject>
open_pr: <"#N" or null>
last_model_update: <RFC3339 UTC>
success_criteria:
  - criterion: "<testable assertion for the Next action>"
    status: pending | in-progress | achieved | abandoned
    evidence: "<file:line | PR# | metric path | null>"
---

# Session digest — <branch> @ <sha>

## Next action

ONE imperative sentence describing the next concrete step. If multiple
things are queued, pick the one with highest blast radius. If nothing is
queued, write `Wait for user direction on <specific question>`.

The next action must map 1:1 to entries in the `success_criteria`
frontmatter array — each criterion testable, not vibes.

## In-flight

Bulleted list of work currently mid-execution. For each item: the
file/feature, the current step number out of total, and the immediate
next sub-step.

## Live hypotheses

Bulleted list of working hypotheses the next session should inherit.
"X is the bottleneck because Y" / "If we change A, B should follow."
These are *unconfirmed*; do not promote to MEMORY.md until validated.

## Open questions

Numbered. Questions you would ask the user if they walked in right now.

## Do NOT carry forward

**Highest-leverage field.** Things the next session must NOT re-propose:
rejected designs, abandoned approaches, paths the user explicitly closed.
Without this, a fresh model context will silently re-derive bad ideas you
already filtered.

## Prior success criteria status (Karpathy R4)

When a prior digest exists, this section reports the status delta:

• ✅ achieved: — evidence: <file:line | commit | PR>
• ⏳ in-progress: — last touched:
• ⛔ abandoned: — reason:

Carrying forward only the still-pending or in-progress criteria into the
new `success_criteria` frontmatter prevents drift.