continue-claude-code-work
/continue-claude-code-work
Continues interrupted Claude Code work after local history is read and reconciled — reconstructs the original outcome, unfulfilled requests, and the next action. Use when given a Claude Code Session ID, asked to pick up prior Claude work, told a run was interrupted or compacted, or asked to take over without `claude --resume`. Not for Codex sessions (use continue-codex-work).
- Author
- daymade ↗
- Repository
- claude-code-skills ↗
- Licence
- MIT
- Last repository change
- 26.10.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 26.10.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
Continues interrupted Claude Code work after local history is read and reconciled — reconstructs the original outcome, unfulfilled requests, and the next action. Use when given a Claude Code Session ID, asked to pick up prior Claude work, told a run was interrupted or compacted, or asked to take over without `claude --resume`. Not for Codex sessions (use continue-codex-work).
Arguments
/continue-claude-code-work [session-id]
Original author description
Continues interrupted Claude Code work after local history is read and reconciled — reconstructs the original outcome, unfulfilled requests, and the next action. Use when given a Claude Code Session ID, asked to pick up prior Claude work, told a run was interrupted or compacted, or asked to take over without `claude --resume`. Not for Codex sessions (use continue-codex-work).
How it works
- Step 1: Obtain a verified read receipt
- Step 2: Rebuild the continuation contract
- Step 3: Reconcile with current reality
- Step 4: Execute the business task
- Step 5: Report against the contract
SKILL.md preview
--- name: continue-claude-code-work description: >- Continues interrupted Claude Code work after local history is read and reconciled — reconstructs the original outcome, unfulfilled requests, and the next action. Use when given a Claude Code Session ID, asked to pick up prior Claude work, told a run was interrupted or compacted, or asked to take over without `claude --resume`. Not for Codex sessions (use continue-codex-work). argument-hint: "[session-id]" --- # Continue Claude Code Work Continue means execute the still-unfinished business task. It does not mean summarize the transcript, perfect the history tool, or start a new experiment. ## Step 1: Obtain a verified read receipt Invoke `daymade-claude-code:read-claude-code-history` for the exact Session. Ask that Skill for a chronological evidence briefing, not separate “last user” and “last assistant” buckets. If the Session ID is unknown, use its search/inventory route first. Do not act until the receipt states: - exact Session ID and project; - sources and time coverage; - compaction and raw-chronology boundaries; - every retained human request, including queued prompts; - end reason, unresolved calls, files touched, and explicit gaps. If a clipped section could contain the objective or a correction, re-read it with the reader's full mode. If identity, ancestry, or authorship is unresolved, stop; continuing from a guessed Session is worse than asking for the missing evidence. ## Step 2: Rebuild the continuation contract Before the first project-changing tool call, write this compact internal contract from evidence. Do not invent a value to fill a blank. | Field | Evidence required | |---|---| | Original business outcome | Earliest still-governing human request, not a later implementation detail | | Current explicit request | Latest human request that is not merely “继续” | | Already completed | Independent current-state verification, not the old Agent's claim | | Still unfulfilled | Requested result with no completion evidence | | User corrections / do-not-repeat | Human messages that rejected a route, output, or assumption | | Proven assets and successful routes | Existing code, docs, Skills, outputs, or commands that previously worked | | Next direct action | One action whose success visibly reduces the unfulfilled business result | When the latest message is only “继续,” inherit the objective from the verified chronology. Never treat the cue itself as the specification. ## Step 3: Reconcile with current reality 1. Read the target project's current `AGENTS.md`/`CLAUDE.md` and authoritative project state; historical instructions may be stale. 2. Confirm the current cwd, branch, working tree, and relevant files. 3. Verify whether prior writes, commits, external operations, or background jobs actually landed. A transcript records attempts as well as successes. 4. Retrieve the proven asset or prior successful path before authoring a replacement. 5. If another process may still complete the same transiently failed work, verify its current result before duplicating it. ## Step 4: Execute the business task Take the next direct action from the contract and verify its result. Skill edits, review expansion, documentation systems, and infrastructure cleanup remain subordinate unless the user explicitly made one of them the business outcome or they are strictly required to unblock it. Before changing direction, ask mechanically: “If this succeeds, which original unfulfilled result becomes smaller?” If the answer is none, record it as a later proposal and return to the task. Do not run `claude --resume` or `claude --continue`. Do not overwrite unrelated working-tree changes. ## Step 5: Report against the contract - **Recovered goal**: Session and original business outcome. - **Executed**: actions and independent verification. - **Now complete**: contract rows that are actually closed. - **Remaining**: unfulfilled rows and exact blockers. - **Not repeated**: prior rejected routes deliberately avoided when relevant. Do not say “continued successfully” when only context extraction or a process step completed; the business result is the completion unit.
Versions
The database has no other skills named continue-claude-code-work.
Database snapshot: 13.11.2026 · package version 0944d18ba8f2 (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
- 90continue-codex-work
Continues interrupted Codex work only after read-codex-history verifies rollout identity and fork/compaction lineage — restores the original outcome, unfulfilled requests, and the next action. Use when given a Codex Session ID, asked to pick up a prior Codex run, told Codex was… - 86resume-claude
Continue work from a local Claude Code session in Muse Code. Use when the user asks to resume, continue, or recover unfinished Claude Code work, with or without a session ID or log path; call read_skill for bundled:resume-claude before reading its transcript. Explicit /import requests use import. - 100resume-claude-session
Use when the user asks Codex to continue, resume, or take over work from a Claude Code session by session name or session id (UUID or UUID prefix). Examples include "continue the claude session called feature-x" or "/resume-claude-session a3b5c9f2". Do not use for ordinary Codex… - 86resume-codex
Continue work from a local Codex session in Muse Code. Use when the user asks to resume, continue, or recover unfinished Codex work, with or without a session ID or log path; call read_skill for bundled:resume-codex before reading its transcript. Explicit /import requests use import. - 100resume-codex-session
Use when the user asks Claude to continue, resume, or take over work from a Codex session by session name or session id (UUID or UUID prefix). Examples include "continue the codex session called feature-x" or "/resume-codex-session 019dc08e". Do not use for ordinary Claude… - 100session-handoff
Continue a conversation from another coding agent's local session record, e.g. pick up a Codex or Claude (Claude Code / Claude Desktop) session after one platform's quota runs out, or when switching agents. Use when the user names a past conversation (title, session ID or record…