continue
/continue
Use to resume from /pause. Reads the pause state, injects relevant memory context, and proposes the next concrete step. Pairs with /pause skill.
- Author
- ialameh ↗
- Repository
- sift-coder ↗
- Licence
- MIT
- Last repository change
- 03.06.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 03.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use to resume from /pause. Reads the pause state, injects relevant memory context, and proposes the next concrete step. Pairs with /pause skill.
Original author description
Use to resume from /pause. Reads the pause state, injects relevant memory context, and proposes the next concrete step. Pairs with /pause skill.
How it works
- Method
- Output shape
- Rules
- Anti-patterns
- When NOT to use
- Subagent dispatch
- Value over native CC
SKILL.md preview
---
name: continue
description: Use to resume from /pause. Reads the pause state, injects relevant memory context, and proposes the next concrete step. Pairs with /pause skill.
---
# continue
Resume from `/pause`. Inverse operation. Reads pause state, refreshes memory context, proposes next move.
## Method
1. **Locate pause.** User specifies `<id>` or "most recent".
2. **Load `pause-<id>.json`** from `.siftcoder/checkpoints/`.
3. **Memory refresh.** `mem_get { id: pause.memoryId }`. Also `mem_search` for activity since the pause (any progress someone else made? any new constraints?).
4. **Verify state.** Has the codebase changed since pause? `git log --since=<pause.createdAt>`. Major changes invalidate the dead-end list.
5. **Propose resume.** Summarise the pause + propose the next concrete step + confirm with user.
6. **Mark resumed.** Update memory: `kind: pause`, `status: resumed`.
## Output shape
```
Resuming: pause-<id> (from <ISO>)
Original open question: <pause.openQuestion>
Progress at pause:
✓ <item>
Hypothesis at pause: <pause.hypothesis>
Since pause (X days ago):
- <commits / activity>
- <new memory items>
Dead ends still relevant: <count>
Constraints still hold: <count>
Proposed next step: <pause.nextStep>
Confirm to proceed, or describe variant?
```
## Rules
- **Verify state.** Codebase may have moved; pause's hypothesis may be stale.
- **Propose, don't auto-execute.** User confirms before resuming.
- **Memory updated.** Pause status moves to `resumed`.
- **List dead ends prominently.** They're the highest-value part of pause memory.
## Anti-patterns
- Resuming on a stale hypothesis without verification
- Ignoring activity since pause
- Bypassing the user-confirm step
- Re-exploring dead ends because they weren't surfaced
## When NOT to use
- No prior `/pause` to resume from
- Pause was about an abandoned thread — `/dream` for fresh thinking
- Better to start fresh — sometimes the right call
## Subagent dispatch
- None for the load step
- Memory MCP for refresh
- `general-purpose` for the next step if it's well-defined
## Value over native CC
CC has no native pause/resume. The pair `/pause` + `/continue` provides explicit session-bridging. The structured resumption (with verification) IS the value.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · ialameh/sift-coder | 100 | MIT |
| bdfinst/agentic-dev-team | 100 | MIT |
| frostiks777/harness | 90 | MIT |
| tonydzi/second-brain-starter-kit | 90 | MIT |
| shakacode/agent-workflows | 86 | MIT |
Database snapshot: 13.11.2026 · package version 06057f12a3fe (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90safe-resume
Use when the user says "safe resume", "resume from pause", "pick up where we left off", "continue the paused work", or when a session start hook reports a /dev:safe-pause state for this session. Also use when a fresh session is asked to continue and a RESUME.md exists for it. - 100pause-and-resume
Cooperatively pause unfinished work in the current session, leave a precise continuation checkpoint, and resume from it when the user later says continue. Use only when the user explicitly requests this pause workflow. Do not use for crashes, app shutdown, new-session handoffs,… - 90loom-pickup
Use when resuming work or getting up to speed on a Loom task — "pickup", "continue", "what were we doing", "get back to". Reads the project board, recent git history, CLAUDE.md, and (if relevant) your living resume doc to brief the current state and a concrete next step. - 90pause
Use when you need the Codex Copilot equivalent of Claude Copilot /pause: preserve current work state in tc and memory before context switching. - 100pause-writer-before-shared-file-edit
编辑会被并行会话/自动机制改写的文件(技能 description、记忆索引、台账、evolution 状态)时的防竞态流程:先证明有并发写入方(mtime+字节数)→ 官方 CLI 暂停(evolution.js pause,不手写 control.json)→ 暂停后重新扫描再动手 → 扫描红当「暂定」,复跑一次再判 → 改完 resume 并记录基线。触发词:并发写入、并行会话改了我的文件、description 被回滚、悬空引用假红、mtime/size 变了、evolution pause/resume。 - 90session
Starts or resumes a work session at the lowest context cost. Reads the state file, logs any new request in the owner's words, reads only what the task touches, then proposes a short plan before any code. Use at the start of every session, after /clear or a compaction, or when…