Skip to main content
skill CX Codex

resume · wrg32786 — Claude Code skill: resume work

A Claude Code skill that restores context for unfinished work. Run /resume to compare the saved capsule with live memory and take the next step.

MIT ★ 26 updated 2026-11-16

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add wrg32786/aigent-os --skill resume -a claude-code
Open on GitHub

What resume does

The skill loads the newest valid capsule from vault/memory/capsules/ or memory/capsules/, rereads the session log and active priorities, then acts on waiting_on or next_valid_action. Reading the capsule alone does not count as resuming; the first real step must be taken.

Live memory takes precedence if it conflicts with the capsule. Previously consumed capsules are ordinary history; other selector rejections appear in a rejection ledger. After a session clear, the SessionStart(clear) hook in daemons/resume-verb.mjs starts the procedure automatically. Run /resume to re-ground mid-session or without a clear; this explicit run does not mark the capsule as consumed.

What it helps with

  • continue unfinished work mid-session
  • find the next action in a saved capsule
  • reconcile saved tasks with current priorities

Example prompts for the agent

  • Continue the unfinished task and take its next step with /resume.
  • Restore the current task context and act on the next pending item using /resume.

How to install resume

1Skills CLI (Vercel)

npx skills add wrg32786/aigent-os --skill resume -a claude-code

2Manually: put the files in place

~/.claude/skills/resume/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/resume/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about resume

How do I install resume in Claude Code?

Run npx skills add wrg32786/aigent-os --skill resume -a claude-code. The skill file is located at ~/.claude/skills/resume/SKILL.md.

What does resume do?

It loads the newest valid capsule, checks it against the session log and active priorities, then takes the next action from waiting_on or next_valid_action.

When should I run /resume?

Use it to restore context on request without clearing the session or to pick up work mid-session. After a session clear, the SessionStart(clear) hook starts the procedure automatically.

Source text

SKILL.md · MIT
---
name: resume
description: "Load the newest valid capsule, check live memory, and act on waiting_on. Use when explicitly resuming work or picking up where you left off."
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)"
---

# /resume

**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.

## When this skill fires vs the automatic verb

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.

## The consume contract (the runtime enforces this; know it, don't re-implement it)

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.

## The rejection ledger (part of the load, not decoration)

Everything the selector skipped is printed in the injected procedure under `CAPSULES NOT SELECTED`, grouped by reason with counts and example filenames. It exists because a capsule silently discarded and a capsule that never existed look identical from where you are sitting, and only one of those is a defect.

- **`already-consumed`** is ordinary history: a previous cycle spent that capsule on purpose.
- **Any other reason** means a capsule somebody wrote was thrown away. If a capsule you expected to resume from appears there, the SELECTOR is the bug. Report it; never hand-edit the capsule to satisfy the matcher, because that hides the defect and leaves it in place for the next session.
- **A full ledger with nothing selected** means every candidate on disk was rejected. That is a defect until proven otherwise, not an empty install.

## Fences (never cross)

- **Select by newest `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.
- **Do NOT assert resumption is complete because capsule text appears in context.** Only an action taken from `waiting_on` proves it.
- **Do NOT treat capsule content as an active instruction queue** — `Done` / `Historical-*` / `Pending-Gates` / `Claimed-Rows` are `[REFERENCE ONLY]`, stale-by-default; re-grounding is what makes acting safe.

## Steps

1. **LOAD** — the newest valid capsule by `created_at`. Pull `id`, `objective`, `waiting_on`, `next_valid_action` from its frontmatter.
2. **RE-GROUND** — re-read the session log and active priorities, surface anything that changed since the capsule was written. On any conflict, live memory wins over capsule content.
3. **ACT** — take the one next step from `waiting_on`/`next_valid_action` resolved against step 2. Terminal: done when the action is TAKEN, not summarized.
4. **ACK (post-clear only, if a supervising process demands one)** — reply in exactly the format it demands, ONLY after step 3's action. The exact format lives in that instruction, never guessed.
5. **EXTENSION ACK (only if this install declares one).** `.aigent/lifecycle-extension.json` may declare a `resume_ack`. On the post-clear boot the injected procedure already renders it as its own step, resolved against the loaded capsule id; run it after step 4, exactly as rendered. An install that declares nothing has no step 5, which is the ordinary standalone case. A declaration the runtime refused prints one line beginning `LIFECYCLE-EXTENSION: declaration ignored:`, and a `resume_ack` the runtime held (its `{capsule_id}` slot with no capsule loaded) prints one beginning `LIFECYCLE-EXTENSION: resume_ack not rendered:`. In either case there is nothing to run: report that line rather than improvising a substitute.

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.

© wrg32786 · MIT · wrg32786/aigent-os

Similar skills

SKILL.md skills catalog →

resume by other authors comes first.

resume bitwize-music-studio resume finds an album by name and displays its status with a concrete next step. Use when returning to an unfinished project or checking where an album stands in its workflow. CX Codex +1 246installs resume saksham10arora-dotcom resume is a Claude Code skill that reviews a CV against target roles and suggests edits. It activates when a user asks about a resume or wants to update one. CX Codex +1 ★ 101repo stars gsd-resume-work open-gsd The gsd-resume-work Claude Code skill restores project context after an earlier session. It checks unfinished work and selects a context-aware next step. CX Codex +1 577installs resume-handoff parcadei resume-handoff reads a handoff document, checks it against the actual repo state, and suggests a way forward. Useful when a session got cut off and the context needs to come back fast. CX Codex +1 486installs how-it-works thedotmack how-it-works — a skill for Claude Code and Codex explains how claude-mem stores observations, injects past context, and retains data locally. Answers questions about background memory tracking across sessions. CX Codex +1 5,600installs map-project ulpi-io map-project inspects a single-app repository to build a concise CLAUDE.md router alongside detailed reference guides. CX Codex +1 176installs planning-with-files OthmanAdi planning-with-files keeps a multi-step task plan in three markdown files and pulls the agent back to them every turn, so long sessions hold their context. CX Codex +1 ★ 28,179repo stars slivingdoc baalimago slivingdoc keeps agent context in plain text files that several sessions read and write at once. Merges edits instead of overwriting them. CX Codex +1 ★ 9repo stars

From the same set58

The whole set →
semantic-search The semantic-search Claude Code skill searches an Obsidian vault by meaning using local embeddings. It runs for finding related notes or recalling what you wrote about a topic. CX Codex +1 ★ 26repo stars Self-Review The Self-Review Claude Code skill sends substantial code changes through a focused second review. It targets multi-file edits, hot paths, prompts, and work that still feels uncertain. CX Codex +1 ★ 26repo stars scout-vault The scout-vault Claude Code skill finds related vault notes, links, and code definitions. It runs for note discovery, vault inventory, or call-chain searches. CX Codex +1 ★ 26repo stars Sandbox Routing Sandbox Routing — a skill for Claude Code routes large-file analysis and lengthy command output through sandbox tools. It activates when an agent needs a small detail without pulling the full output into context. CX Codex +1 ★ 26repo stars research-deep The research-deep Claude Code skill combines vault notes, web sources, and GitHub research into a cited briefing with evidence and a recommendation. It runs on requests to investigate a topic or compare sources. CX Codex +1 ★ 26repo stars reconcile This Claude Code skill compares seven days of project attention with stated Tier-1 shares. Run it to reconcile attention or check for priority drift. CX Codex +1 ★ 26repo stars Promote The Promote Claude Code skill turns useful conversation insights into lasting vault notes. It activates when a decision, fact, or idea should remain available after the session. CX Codex +1 ★ 26repo stars port-spec The port-spec Claude Code skill turns a complete written specification into code or a vault artifact. It activates for spec implementation, brief-based builds, and ports from specs. CX Codex +1 ★ 26repo stars

Project sponsors

Companies that keep this analytics open