resume-work
Skill102 starsChanged 8 days agoMITView on GitHub
Resume work from previous session with full context restoration
5 other projects use a version of this.
Adopted by
Most recently taken up by
- 0xdeafcafe/skillstheir own version, first seen Nov 8, 2026
- marinvch/Cortextheir own version, first seen Nov 1, 2026
- nexus-a1/claude-skillstheir own version, first seen Oct 17, 2026
- bendyworks/claude-skillstheir own version, first seen Oct 13, 2026
- DanielOnPurpose/danielonpurpose-skillstheir own version, first seen Jul 27, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- bendyworks/claude-skills★ 1same name
- marinvch/Cortex★ 1same name
- nexus-a1/claude-skills★ 1same name
- 0xdeafcafe/skills★ 0same name
- DanielOnPurpose/danielonpurpose-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository88 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- templates/copilot-instructions.mdCopilot instructions
- add-backlogSkill
- add-phaseSkill
- add-testsSkill
- add-todoSkill
- ai-integration-phaseSkill
- analyze-dependenciesSkill
- audit-fixSkill
- audit-milestoneSkill
- audit-uatSkill
- autonomousSkill
- check-todosSkill
- cleanupSkill
- code-review-fixSkill
- code-reviewSkill
- complete-milestoneSkill
- debugSkill
- discuss-phaseSkill
- docs-updateSkill
- doSkill
- eval-reviewSkill
- execute-phaseSkill
- exploreSkill
- extract-learningsSkill
- fastSkill
- forensicsSkill
- from-gsd2Skill
- graphifySkill
- healthSkill
- helpSkill
- importSkill
- inboxSkill
- ingest-docsSkill
- insert-phaseSkill
- intelSkill
- join-discordSkill
- list-phase-assumptionsSkill
- list-workspacesSkill
- managerSkill
- map-codebaseSkill
- milestone-summarySkill
- mvp-phaseSkill
- new-dddSkill
- new-milestoneSkill
- new-projectSkill
- new-workspaceSkill
- nextSkill
- noteSkill
- pause-workSkill
- plan-milestone-gapsSkill
- plan-phaseSkill
- plant-seedSkill
- pr-branchSkill
- profile-userSkill
- progressSkill
- quickSkill
- reapply-patchesSkill
- reconcileSkill
- remember-accessSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Check for .planning/HANDOFF.json via Read tool.
- Very specific: line 22
Read .planning/STATE.md to restore the big-picture project position.
- Very specific: line 39
If task was mid-execute: offer /gsd:execute-phase with the current phase.
- Very specific: line 40
If phase is at plan boundary: offer /gsd:plan-phase or /gsd:execute-phase for the next phase.
- Distinctive: line 41
If there are uncommitted files that look in-progress: call attention to them before offering continuation.
- Distinctive: line 44
After routing — once steps 1-5 have completed without error — remove the handoff file:
- Distinctive: line 50
If the command is unavailable for any reason, fall back to direct removal:
- Distinctive: line 55
Do not abort the resume if cleanup fails — it's hygiene, not correctness.
- Very specific: line 61
If HANDOFF.json is absent in step 1, skip everything — don't attempt to clean up what isn't there.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<objective>
Restore complete project context from a previous session. Handle manual-pause (`/gsd:pause-work`) and auto-compact (PreCompact hook) handoffs identically.
</objective><process>- Detect handoff state.
Check for
.planning/HANDOFF.jsonvia Read tool. If missing, the session has no handoff — announce "No handoff found" and proceed to normal/gsd:progressrouting. - Load STATE.md.
Read
.planning/STATE.mdto restore the big-picture project position. If missing, reconstruct from.planning/ROADMAP.mdand the latest phase directory's SUMMARY.md files; if reconstruction fails, surface the error and stop. - Read the handoff.
Parse
.planning/HANDOFF.json. Extract phase, plan, task, status, source, uncommitted_files, decisions, context_notes, next_action. Per HANDOFF schema, all fields are always present (empty arrays / null for unset). - Present project status.
Emit a compact status block covering:
- Milestone + percent complete (from STATE.md frontmatter
progress.percent). - Current phase name and number.
- Plan / task position from the handoff.
- Handoff source (manual-pause vs auto-compact) and timestamp.
- Top 3 decisions and any blockers from the handoff.
- Uncommitted files summary.
- The
next_actionstring verbatim — it's the resumption hint.
- Milestone + percent complete (from STATE.md frontmatter
- Route to the next action.
Offer 1-3 concrete options based on handoff state. Common patterns:
- If task was mid-execute: offer
/gsd:execute-phasewith the current phase. - If phase is at plan boundary: offer
/gsd:plan-phaseor/gsd:execute-phasefor the next phase. - If there are uncommitted files that look in-progress: call attention to them before offering continuation.
- If task was mid-execute: offer
Clean up the handoff (LIFE-01). After routing — once steps 1-5 have completed without error — remove the handoff file:
node "${CLAUDE_PLUGIN_ROOT:-$(ls -d "$HOME/.claude/plugins/cache/gsd-plugin/gsd/"*/ 2>/dev/null|sort -V|tail -1)}/bin/gsd-tools.cjs" checkpoint --clearIf the command is unavailable for any reason, fall back to direct removal:
rm -f .planning/HANDOFF.jsonDo not abort the resume if cleanup fails — it's hygiene, not correctness. The next session's SessionStart will overwrite a stale handoff anyway (per D-05 from Phase 4: latest snapshot wins).
</process><rules>
- Step 6 runs **last**, after all context is loaded and the user has been shown status. A failed/aborted resume (steps 1-5 error out) leaves HANDOFF.json on disk for recovery (per D-08).
- If `HANDOFF.json` is absent in step 1, skip everything — don't attempt to clean up what isn't there. `checkpoint --clear` is idempotent but unnecessary work.
- The skill is the single owner of HANDOFF.json deletion. The SessionStart hook must NOT delete — it only detects (per D-10).
</rules>Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.