handoff
|
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace /tmp/handoff && cp -r /tmp/handoff/plugins/ai-agency/hyperflow/skills/handoff ~/.claude/skills/handoffSKILL.md
# 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 deferred-commit machinery). Packages live at `.hyperflow-handoff/<slug>/` (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 [<slug>]` 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 <slug>` — build side Thin alias for starting the second-session build: invoke `Skill` with `skill: dispatch` and `args: "<slug>"`. 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 <slug>` — planning side 1. Require `STATUS=built` (else: "handoff `<slug>` is `<status>` — nothing to review yet"). 2. Read `COMPLETION.md` → extract `Diff range = <base>..<head>`. 3. Invoke `Skill` with `skill: audit` and `args: "<base>..<head> level=3"` (`level=5` when 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. 4. 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. 5. Set `STATUS=reviewed` once the review is accepted. ### `complete <slug>` Mark the lifecycle done: set `STATUS=reviewed` (if not already) and archive the package to `.hyperflow-handoff/.archive/<slug>/`. Commit `chore(handoff): archive <slug>`. ## Resolution - Default `<slug>` = the most-recently-modified package when omitted from `status`/`pickup`/`review`. - A package whose `STATUS=planned` is a **build-side** task (run `pickup`); `built` is a **review-side** task (run `review`). The session-start hook surfaces the right verb automatically. ## Iron rules - **Never edit the build's commits.** `review` is 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 exact `git push -u origin <branch>`. - **No AI attribution** in any commit or package file. - Honors `handoff.*` config (`autoPush`, `remote`, `packageDir`). ## Doctrine Shared rules in [`../hyperflow/DOCTRINE.md`](../hyperflow/DOCTRINE.md). Package contract + templates in [`../hyperflow/session-handoff.md`](../hyperflow/session-handoff.md).
|
Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
Plan and scope a project — discovery, challenge assumptions, present S/M/L options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".
Knowledge engineer — architecture docs, ADRs, diagrams, changelogs, onboarding, and reports.