菜单
The resume verb, invoked explicitly — load the newest valid capsule by created_at, re-ground against live memory, then ACT on waiting_on. Mid-session or on explicit ask; the post-clear boot fires the same procedure automatically via daemons/resume-verb.mjs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
The capsule verb, invoked explicitly — reconcile from the live memory, write a resume-ready capsule, then stop. Mid-session checkpoint or completion capsule; a rolling best-effort version of the same write also runs automatically on every Stop event via daemons/stop-capsule-writer.mjs.
Run the volunteering ledger before declaring work done. Forces surfacing of what changed/didn't, what was noticed-but-not-fixed, what was guessed, and what tradeoffs were made on the principal's behalf. The standard - the principal should never be surprised later by something the agent knew at the time.
Capture a confident agent claim (Phase 1) or resolve one as right/wrong (Phase 2) in vault/memory/TRUST_DECAY.md. Builds the longitudinal record of agent calibration over time. Pairs with /honesty-check (which should reduce Phase 1 frequency) and /diagnose (which surfaces causes that often reveal Phase 2 events).
One evidence-gated pass that sequences /dream, /reconcile, /sweep-now, and /digest over your own vault, with a /system-check gate and a ledger-review pass over the measurement layer (Honesty Ledger, Trust Decay, Failure Modes). Stays exactly as human-gated as the legs it calls -- stages, never auto-applies. Skips a leg gracefully when there is nothing to do; every leg that runs leaves an evidence line.
Dispatch Hestia to run all 3 vault sweeps (DELEGATION_TRACKER stale items, HEAT_INDEX dormant flips, broken wikilinks) and append the result to HESTIA_SWEEP_LOG.
Route ONE bounded, mechanical task to the Codex CLI as a non-Claude executor, under the same review-before-merge gate as any other agent-produced diff. Use when the user explicitly asks to hand a task to Codex, or names OpenAI Codex / a non-Claude executor for a mechanical change (rename a symbol across files, add a config entry, apply a scripted find/replace). Not for open-ended or strategic work -- that stays with the operating Claude session.
| name | resume |
| description | The resume verb, invoked explicitly — load the newest valid capsule by created_at, re-ground against live memory, then ACT on waiting_on. Mid-session or on explicit ask; the post-clear boot fires the same procedure automatically via daemons/resume-verb.mjs. |
| trigger | /resume |
| status | Two-verb lifecycle — supersedes the v1 open skill and absorbs /open (there is no separate open ceremony). |
| related | ["docs/two-verb-lifecycle.md (design doc — schema, content gate, sovereignty rules)","daemons/resume-verb.mjs (the runtime container — SessionStart(clear) hook)","skills/context-capsule/SKILL.md (the mirror verb)"] |
The entire job: load → re-ground → ACT on waiting_on. Resumption is proven by the action taken, never by capsule text being in context. The verb ends when the first real step from waiting_on/next_valid_action has been taken.
The post-clear boot does NOT need this skill — daemons/resume-verb.mjs injects the full procedure automatically on SessionStart(clear). Invoke /resume for the explicit cases: re-grounding on request without a clear, or picking up work mid-session.
On the post-clear boot, the capsule the runtime loads is marked status: resumed mechanically at load — the same capsule is never silently re-resumed on a later clear. If no active capsule exists, the boot takes the documented degraded path (re-derive from live memory) and says so; it never replays stale state as fresh. An explicit mid-session /resume is a re-ground, not a consume — it does not mark, so say plainly which capsule you re-grounded from.
created_at, never a pointer. Load the valid capsule with the newest frontmatter created_at in vault/memory/capsules/ (or memory/capsules/) — there is no pointer file to consult.waiting_on proves it.Done / Historical-* / Pending-Gates / Claimed-Rows are [REFERENCE ONLY], stale-by-default; re-grounding is what makes acting safe.created_at. Pull id, objective, waiting_on, next_valid_action from its frontmatter.waiting_on/next_valid_action resolved against step 2. Terminal: done when the action is TAKEN, not summarized.No stillness clock — resume is the wake-up, not the seal — but stay terminal: still reading past re-grounding without acting is the exact trap this verb exists to prevent.