Skip to content

TsukiNi22/ai-utils / skills/ai/continue-work

continue-work

Verified

Resume a task stopped with the pause skill at the user's next "continue" - reads the checkpoint of the project (~/.claude/pauses, checkpoint.sh of pause), checks it against the real state (git status and diff, the files, what still runs) and trusts the real state when they differ (the user may have changed things meanwhile), starts again what was stopped and is still needed, redoes the interrupted step from its start, then goes on with the next steps in order without redoing what is done and without a recap; closes the checkpoint when the task is over. Without a checkpoint it simply continues the current task of the conversation. Use whenever the user says "continue", "reprends", "on reprend", "vas-y continue", "resume", "go on", "/continue-work" after a pause, or opens a session in a project that has a checkpoint waiting.

FileKindSize
SKILL.mdskill md3.5 KB
requires.txtmarkdown28 B
---
name: continue-work
description: Resume a task stopped with the pause skill at the user's next "continue" - reads the checkpoint of the project (~/.claude/pauses, checkpoint.sh of pause), checks it against the real state (git status and diff, the files, what still runs) and trusts the real state when they differ (the user may have changed things meanwhile), starts again what was stopped and is still needed, redoes the interrupted step from its start, then goes on with the next steps in order without redoing what is done and without a recap; closes the checkpoint when the task is over. Without a checkpoint it simply continues the current task of the conversation. Use whenever the user says "continue", "reprends", "on reprend", "vas-y continue", "resume", "go on", "/continue-work" after a pause, or opens a session in a project that has a checkpoint waiting.
metadata:
  summary: 'Resumes at the next `continue` what `pause` stopped: reads the checkpoint of the project, checks it against the real state (git, files, what runs, the real state wins), restarts what is still needed, redoes the interrupted step, goes on with the next steps without redoing or recapping, closes the checkpoint at the end.'
---

# Continue: resume a paused task

`<name>` (a skill) = the folder of that skill: `~/.claude/skills/<name>` (setup.sh) or `${CLAUDE_SKILL_DIR}/../../*/<name>` (plugin of the marketplace).

The user says `continue` (or "reprends"...): go on with the task where it stopped, at once, without asking what to
do and without telling the whole story again.

## 1. Find where it stopped
```bash
bash <pause>/scripts/checkpoint.sh show       # the checkpoint of the current project, exit 1 when there is none
```
- A checkpoint: it is the plan. Several projects paused and the current folder is not one of them:
  `checkpoint.sh list`, take the one the conversation is about, else ask which one (`interactive-questions`).
- No checkpoint: a plain `continue` of the current task. Go on from the last step of the conversation (its todo
  list, the last message), nothing else of this skill applies.

## 2. Check it against what is there now
The checkpoint can be old: the user may have edited, committed, pulled or run things since.
- `\git status`, `\git log -3 --oneline`, `\git diff --stat`: compare with *State of the files* and the commit noted.
- The files of *Interrupted* and of the first *Next* steps: read them before editing.
- What was stopped: still stopped? (`pgrep -fa <command>`), a workflow run id to resume.
- A difference: **the real state wins**. A step the user did meanwhile is done; a change of theirs is kept (never
  overwritten, never reverted); a plan that no longer fits is adapted, said in one line. A contradiction that changes
  what to do (the goal itself moved, a decision undone): ask once, briefly (`interactive-questions`).

## 3. Resume
- Start again what was stopped and is still needed (the commands of *Stopped*, a workflow with its run id).
- The **interrupted** step: redo it from its start (its half-done part was finished or reverted by the pause).
- Then the **next** steps in order, under the same rules (git, language, style, confirmations) as before the pause.
- One line at the start at most (`Reprise : <step>.`), no recap of what was done.
- A new `pause` during the work: the `pause` skill again (the checkpoint is replaced).

## 4. Close
When the task is over (its last step done and verified): `bash <pause>/scripts/checkpoint.sh done` (moved to
`~/.claude/pauses/done/`, kept), then the usual final report of the task.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall