Handoff
Personal agent skills for Paper-first UI prototyping and design engineering.
npx -y skills add olzn/skills --skill handoffAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Compact the current conversation into a handoff document another session or agent can resume from. Use when wrapping up with unfinished work, when context is getting long, or when the user says "hand this off", "write a handoff", or "save state for the next session". Produces a single Markdown file at a durable, harness-agnostic path and reports it. Does NOT continue the work itself; it only captures state so a fresh session can.
SKILL.md
2.1 KB, as published. Nobody here has run it
Handoff
A handoff is a single Markdown document that lets a fresh session, on any agent or harness, resume this work without re-reading the whole conversation. Capture the current state and the next move, not a transcript.
What to capture
Keep it short and skimmable. Include only what the next session actually needs:
- Goal — what we are trying to achieve, in a sentence or two.
- State — what is done, what is in progress, what has not been started.
- Next step — the single most concrete thing to do next.
- Key decisions — choices already made and why, so they are not relitigated.
- Open questions and gotchas — blockers, risks, and anything surprising.
- Where to resume — the exact files, paths, commands, or URLs to pick up from.
Do not duplicate content already captured in other artefacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the document accordingly. Suggest the skills the next session should use, if any.
Saving the document
Save to a durable, harness-agnostic location, then report the full path back to the user so both they and the next session can open it:
dir="${HANDOFF_DIR:-$HOME/handoffs}"
mkdir -p "$dir"
path="$dir/handoff-$(date +%Y%m%d-%H%M%S).md"
echo "$path"
Write the document to that path and print it as the final step.
$HANDOFF_DIR lets any environment redirect handoffs without editing the skill.
The default keeps them out of your project repos, survives reboots and temp-directory
cleanup, and names them so they sort chronologically and are easy to find and grep.