handoff
Use when managing a two-session handoff — inspecting, picking up, or reviewing a committed handoff package produced by a session=two scope run. The operator interface over the cross-environment handoff lifecycle (plan in one session, build in another, review back in the first). Trigger with /hyperflow:handoff, "list handoffs", "pick up the handoff", "review the handoff build".
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill handoff --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Handoff Operator interface for **two-session execution**: one session plans (`session=two` at the Step 0 gate), a second session in another environment builds, and the first session reviews. The lifecycle and package format are defined in [`../hyperflow/session-handoff.md`](../hyperflow/session-handoff.md); this skill is the thin set of verbs over it (mirrors how `/hyperflow:flush` fronts the de
What does the handoff skill do?
Use when managing a two-session handoff — inspecting, picking up, or reviewing a committed handoff package produced by a session=two scope run. The operator interface over the cross-environment handoff lifecycle (plan in one session, build in another, review back in the first). Trigger with /hyperflow:handoff, "list handoffs", "pick up the handoff", "review the handoff build".
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill handoff --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
