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".
Allowed Tools
Provided by Plugin
hyperflow
Point it at a GitHub issue and get back a reviewed pull request. Hyperflow turns one AI coding session into a structured engineering pipeline: plan sharpens and decomposes the work, dispatch fans out parallel workers, and a domain specialist reviews every step — nothing ships unreviewed. 18 skills, 22 specialist reviewer and investigator agents, adaptive depth so a 5-line fix never triggers a deep run, and persistent per-project memory that lives in your repo and never leaves it. Runs on whatever model your session already uses — zero config, no API keys, no daemon. Works across Claude Code, Codex App/CLI, OpenCode, Grok, Antigravity, and Cursor.
Installation
This skill is included in the hyperflow plugin:
/plugin install hyperflow@claude-code-plugins-plus
Click to copy
Instructions
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; this skill is the thin set of verbs over it
(mirrors how /hyperflow:flush fronts the deferred-commit machinery).
Packages live at .hyperflow-handoff/ (committed, so they travel via git). STATUS (`planned → built →
reviewed`) is the single source of truth and decides which side of the handoff you are on.
Subcommands
list
Read-only. List every .hyperflow-handoff/*/ (excluding .archive/): slug · STATUS · on_complete · age. Group
by status so the user sees what is awaiting build vs awaiting review.
status []
Show the HANDOFF.md manifest + STATUS for one package (or all). When STATUS=built, also print the
COMPLETION.md diff range and commit count. Read-only.
pickup — build side
Thin alias for starting the second-session build: invoke Skill with skill: dispatch and args: ".
Dispatch's Step 1.0 rehydrates artefact/ into .hyperflow/, runs /hyperflow:scaffold if the cache is missing,
builds the batches, writes COMPLETION.md + STATUS=built, and then deploys or stops per on_complete.
review — planning side
- Require
STATUS=built(else: "handoffis— nothing to review yet"). - Read
COMPLETION.md→ extractDiff range =... - Invoke
Skillwithskill: auditandargs: "(.. level=3" level=5when the originating triage
flow in HANDOFF.md was scientific or security). The audit dispatches the matching domain specialist
reviewers over the second session's diff.
- On audit clean pass → fire the deploy gate (
AskUserQuestion—Run /hyperflow:deploy? Yes / No, binary, no
marker). On NEEDS_FIX → the audit fix-gate (Yes → /hyperflow:plan → /hyperflow:dispatch) handles it.
- Set
STATUS=reviewedonce the review is accepted.
complete
Mark the lifecycle done: set STATUS=reviewed (if not already) and archive the package to
.hyperflow-handoff/.archive/. Commit chore(handoff): archive .
Resolution
- Default
= the most-recently-modified package when omitted fromstatus/pickup/review. - A package whose
STATUS=plannedis a build-side task (runpickup);builtis a review-side task (run
review). The session-start hook surfaces the right verb automatically.
Iron rules
- Never edit the build's commits.
reviewis read-only over the diff range; fixes flow through the audit
fix-gate → scope → dispatch, never by amending the second session's commits.
- Never force-push; never
--no-verify. Auto-push failures surface the exactgit push -u origin. - No AI attribution in any commit or package file.
- Honors
handoff.*config (autoPush,remote,packageDir).
Doctrine
Shared rules in ../hyperflow/DOCTRINE.md. Package contract + templates in