skills/resume-work/SKILL.md
Resume work from previous session with full context restoration
npx skillsauth add jnuyens/gsd-plugin gsd:resume-workInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Detect handoff state.
Check for .planning/HANDOFF.json via Read tool. If missing, the session has no handoff — announce "No handoff found" and proceed to normal /gsd:progress routing.
Load STATE.md.
Read .planning/STATE.md to restore the big-picture project position. If missing, reconstruct from .planning/ROADMAP.md and 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:
progress.percent).next_action string verbatim — it's the resumption hint.Route to the next action. Offer 1-3 concrete options based on handoff state. Common patterns:
/gsd:execute-phase with the current phase./gsd:plan-phase or /gsd:execute-phase for the next phase.Clean up the handoff (LIFE-01). After routing — once steps 1-5 have completed without error — remove the handoff file:
node "${CLAUDE_PLUGIN_ROOT:-$HOME/.claude/plugins/cache/gsd-plugin/current}/bin/gsd-tools.cjs" checkpoint --clear
If the command is unavailable for any reason, fall back to direct removal:
rm -f .planning/HANDOFF.json
Do 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).
testing
Capture or review how this project connects to external systems (GitHub, AWS, npm, SSH, etc.) so future sessions know the auth recipe. Auto-detection hook logs candidate captures to an inbox; this skill promotes them to permanent recipes in `.planning/AUTH-RECIPES.md` and optionally to user-global memory at `~/.claude/auth-recipes/`.
tools
Initialize a new project using Documentation-Driven Development. Research, then write user-facing docs (SPEC.md) as the spec, then user validates docs, then phases derive from doc sections. Best for CLIs, libraries, SDKs, APIs, plugin systems, anything with a well-defined user-facing surface.
tools
Plan an MVP-mode phase — captures an "As a / I want to / So that" user story, runs SPIDR splitting, then delegates to plan-phase
testing
Extract decisions, lessons, patterns, and surprises from completed phase artifacts