plugins/handoff/skills/save/SKILL.md
Save a task handoff file to the shared network drive. This skill should be used when the user runs /handoff:save.
npx skillsauth add l3digital-net/claude-code-plugins saveInstall 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.
Write a handoff file to /mnt/share/instructions/ so work can be resumed on a different machine.
Run the context gathering script:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/gather-context.sh [--description "<user-provided-slug>"]
Parse the JSON output. Use the git state and working directory as the machine context. The filename field provides the generated filename. Also use the conversation context: what task was being worked on, what has been completed, what remains.
Write to /mnt/share/instructions/<filename> using this structure:
# Handoff: [brief task title]
**Saved:** [YYYY-MM-DD HH:MM]
**Machine:** [hostname]
**Working directory:** [full path]
**Branch:** [git branch, if applicable]
## Task Summary
[2-3 sentences: what is the overall goal of this work]
## Work Completed
[Bullet list of what was accomplished in this session]
## Current State
[Where things stand right now: what's running, what's changed, what's been committed vs uncommitted]
## Next Steps
[Numbered list of what needs to happen next, in order. Be specific about which machine, which commands, which files. This is the handoff — the person reading this should be able to pick up exactly where you left off.]
## Context
[Any additional context that would be lost between sessions: error messages encountered, decisions made and why, things that were tried and didn't work, credentials or paths referenced]
Write the content concisely but completely. The reader is Claude Code on a different machine with no conversation history.
Report the full path of the saved file:
Saved: /mnt/share/instructions/<filename>
development
Use when you're stuck or missing current information mid-task - the same command/API/approach failed twice, an error looks like a changed or deprecated API, or you need the current version of something, a fact from after your training cutoff, or to verify something you cannot confirm from the code in context. Starts with a cheap inline lookup and only escalates to a full research sweep if that fails. Do not use for routine pre-emptive checks before ordinary library work - for deliberate research, use /qdev:research.
documentation
Update Outline wiki documentation with implementation-level details from the current session by dispatching the up-docs-propagate-wiki sub-agent. This skill should be used when the user runs /up-docs:wiki.
documentation
Update repository documentation (README.md, docs/, CLAUDE.md) based on session changes by dispatching the up-docs-propagate-repo sub-agent. This skill should be used when the user runs /up-docs:repo.
documentation
Update Notion pages with strategic and organizational context from the current session by dispatching the up-docs-propagate-notion sub-agent. This skill should be used when the user runs /up-docs:notion.