harness/plugins/work-manager/common/skills/explore-handoff/SKILL.md
Compact the current conversation into a handoff document for another agent to pick up.
npx skillsauth add popoffvg/dotfiles explore-handoffInstall 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 document summarising the current conversation so a fresh agent can continue the work. Save it as an in-memory tmp file at $TMPDIR/claude-handoff/<short-slug>.md (create the directory if missing). On macOS $TMPDIR is a per-user tmpfs-style location — fast, ephemeral, survives until reboot.
Before writing, list $TMPDIR/claude-handoff/ and read any existing file with the same slug — extend it rather than overwriting. Print the absolute path of the saved file at the end so the next session can Read it directly.
$TMPDIR (macOS leaves one, producing // otherwise):
DIR="${TMPDIR%/}/claude-handoff" && mkdir -p "$DIR" && echo "$DIR/<slug>.md"
ls "${TMPDIR%/}/claude-handoff/" 2>/dev/null
If <slug>.md exists, write to the another file with a different name (e.g. <slug>-<label>.md).Write tool with the absolute path from step 1 (not the $TMPDIR literal — Write does not expand shell variables).Required structure:
Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
testing
Use when the user asks to create test sets, enumerate scenarios, generate edge cases, or draft a coverage matrix before implementation.
testing
Use when the user asks to review, audit, score, or validate test sets for missed cases before execution or merge.
tools
Test harness plugins in isolation using tmux panes. Runs MCP servers, unit tests, typecheck, and Claude plugin loading. Use when user says "test plugin", "check plugin", "run plugin tests", "validate plugin", or names a specific plugin to test.
development
Guide for designing integration and e2e tests using BDD (Behavior-Driven Development) methodology with Cucumber-style Given/When/Then scenarios. Use when writing or reviewing tests for any service, API, or component. Language-agnostic — covers scenario structure, step notation, assertion principles, async patterns, and common anti-patterns.