pause — Claude Code skill: task state and install
The pause Claude Code skill saves a task’s state when work needs to stop temporarily. The next session offers a way to resume it.
MIT ★ 26 updated 2026-11-16
npx skills add wrg32786/aigent-os --skill pause -a claude-codeWhat pause does
The skill records the task objective, touched files, skills and agents used, verified results, open questions, and blockers. Start it with /pause or /pause waiting on {blocker}.
It identifies whether progress depends on an operator, a sub-agent, a tool, or someone outside the system. Then it writes a Capsule v2 with status: paused, using the /context-capsule schema, and updates state.last_capsule in BODY_STATE.json. Waiting for a sub-agent or an external person sets resumption for the next session; the other cases use a manual trigger.
At the next session boot, the system offers /resume automatically. This workflow uses the Capsule v2 format and BODY_STATE.json.
What it helps with
- save the objective and state of unfinished work
- record files and results confirmed during a session
- note who or what the task is waiting on
- leave context for resuming work in a later session
Example prompts for the agent
- Pause this task and save its state for later.
- Pause the work while I wait for a colleague’s reply.
- Stop here until the sub-agent finishes.
How to install pause
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill pause -a claude-code2Manually: put the files in place
~/.claude/skills/pause/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pause/
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill pause -a codex2Manually: put the files in place
.agents/skills/pause/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill pause -a cursor2Manually: put the files in place
.cursor/skills/pause/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wrg32786/aigent-os skills/pause2Manually: put the files in place
.github/skills/pause/SKILL.md1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill pause -a gemini-cli2Platform CLI
gemini skills install https://github.com/wrg32786/aigent-os --path skills/pauseManually: put the files in place
.devin/skills/pause/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill pause -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about pause
How do I install pause in Claude Code?
Run npx skills add wrg32786/aigent-os --skill pause -a claude-code. The skill file is at ~/.claude/skills/pause/SKILL.md.
What does pause do?
It saves the current task in a Capsule v2 with status: paused and records how work can resume. The system offers /resume at the next session boot.
How does pause decide when work can resume?
It records whether the task is waiting on an operator, a sub-agent, a tool, or someone external. Sub-agent and external waits resume at the next session boot; the other cases use a manual trigger.
Source text
SKILL.md · MIT
---
name: pause
description: "Pause current work with resumable state. Use when pausing a task or stopping work temporarily before returning to it."
---
# /pause — Pause current work with resumable state
Create a Capsule v2 with `status: paused` capturing full execution state for later resume.
## Trigger
`/pause` or `/pause waiting on {blocker}`
## Flow
1. **Capture state** — gather from current session:
- Objective (what we were working on)
- Files touched (from tool call history)
- Skills and agents used
- Last verified state (what was confirmed working)
- Open questions and blockers
2. **Determine waiting_on** — from argument or ask:
- `will` — needs the operator's decision or input
- `agent` — waiting on a sub-agent to complete
- `tool` — waiting on external tool/API/deploy
- `external` — waiting on someone outside the system (a colleague, a client, etc.)
3. **Set resume_trigger**:
- `will` → `manual` (the operator decides when to resume)
- `agent` → `open` (resumes at next session boot, which checks agent status)
- `tool` → `manual` (check tool status on resume)
- `external` → `open` (resumes at next session boot, surfacing the wait)
4. **Write capsule** — use `/context-capsule` schema with `status: paused`
5. **Update BODY_STATE.json** — set `state.last_capsule` with paused capsule info
6. **Output**:
```
Paused: {objective}
Waiting on: {waiting_on}
Resume trigger: {resume_trigger}
Next action: {next_valid_action}
Resume with /resume (offered automatically at next session boot).
```
## Related
- `/resume` — pick up paused work
- `/context-capsule` — the underlying capsule system
- [[concepts/Capsule v2 Doctrine]] — design rationale
© wrg32786 · MIT · wrg32786/aigent-os