Przejdź do treści
Biblioteka skilli
AI i agenci · Automatyzacja

handoff

/handoff

Przekazuje sesję lub linię pracy świeżemu agentowi w nowym panelu Herdr, by zwolnić kontekst albo zmienić model.

Repozytorium
herdr-fleet ↗
Licencja
MIT
Ostatnia zmiana repozytorium
10.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 10.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Przekazuje sesję lub linię pracy świeżemu agentowi w nowym panelu Herdr, by zwolnić kontekst albo zmienić model.

Argumenty

/handoff [self | PANE] [account] [model]
Oryginalny opis (EN)

Hand this session, or a lane, to a fresh agent in a new Herdr pane — to free context, change model, or move to another remuda account. Writes a handoff file (or resumes the same session on another account), starts the successor with a one-line pointer, and confirms that it works. Use when the user says hand off, handoff, continue in a new pane, or switch account or model for this work.

Jak działa

  1. Choose the method
  2. Self
  3. Lane
Sekcje z nagłówków SKILL.md, w oryginale · 53 linii, 887 słów
Podgląd SKILL.md
---
name: handoff
description: Hand this session, or a lane, to a fresh agent in a new Herdr pane — to free context, change model, or move to another remuda account. Writes a handoff file (or resumes the same session on another account), starts the successor with a one-line pointer, and confirms that it works. Use when the user says hand off, handoff, continue in a new pane, or switch account or model for this work.
argument-hint: "[self | PANE] [account] [model]"
allowed-tools:
  - Read
  - Write
  - Edit
  - Bash(python3 "${CLAUDE_PLUGIN_ROOT}/scripts/fleet" *)
  - Bash(python3 ${CLAUDE_PLUGIN_ROOT}/scripts/fleet *)
  - Bash(herdr pane read *)
  - Bash(herdr pane get *)
  - Bash(git status*)
  - Bash(git log *)
---

# Hand off

- **Self** (the default): this session moves to a new pane.
- **Lane**: you orchestrate, and you move a lane's agent. The arguments name the pane or the lane.

First run `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/fleet" conventions` for placement, model and account rules. In plain mode no account changes, but a handoff still frees context or changes the model.

## Choose the method

| Reason | Method |
|---|---|
| Context is large, noisy or compacted | Handoff file, then a fresh session. |
| Only the account changes, the context is healthy, and the agent is Claude | Resume: `spawn --resume <session id> --account <account>`. The new pane forks this conversation on the new account. If that account cannot see the transcript, `spawn` refuses: use a handoff file. |
| The model or effort changes | Either one. `--resume` with `--model` or `--effort` keeps the history. |

Find a session id with `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/fleet" status --json` (field `session_id`; your own row has `self: true`).

## Self

1. Run `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/fleet" prep --handoff`. It returns `handoff_path`, `lane`, `fleet_md` and `pane_role`. Run `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/fleet" orch show --json` too: `self` is true when you are the project's registered orchestrator.
2. If you orchestrate, bring PROJECT.md up to date: decisions (each a ruling and its reason in one line, never a record of a merge, a review round, a push or a cleanup: the event log and git keep those), follow-ups, the user's rules. Add follow-ups with `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/fleet" follow-up add "<text>"`, and close finished ones with `follow-up done <ID>`, not by hand. The handoff file then needs only what is in flight. If `fleet_md` is set and you orchestrate that fleet the old way, bring FLEET.md up to date instead: lane table, decisions, next actions.
3. Unless you resume: write the handoff file at `handoff_path` from the HANDOFF template in `${CLAUDE_PLUGIN_ROOT}/skills/fleet/references/templates.md`. A stranger must be able to continue from it: goal, state, exact next steps, decisions with reasons, the user's rules from this conversation, commands, what not to redo, open questions. Never copy a secret; name where it lives.
4. Start the successor beside this pane:
   ```bash
   python3 "${CLAUDE_PLUGIN_ROOT}/scripts/fleet" spawn --split auto --name <label> [--role <pane_role>] \
     [--account <account>] [--model <model>] [--effort <effort>] [--permission-mode <mode>] --accept-trust \
     --prompt "Read <handoff_path> and continue the work it describes. You replace pane <your pane id>."
   ```
   To resume instead: `spawn --split auto --name <label> --account <account> --accept-trust --resume <your session id> --prompt "You now run on <account> in a new pane. Continue where this conversation stopped."`
   If you orchestrate, pass `--role orchestrator`, name your orch in the prompt ("You take over orch <name> of project <project>."), and end it with "Then run `fleet orch show --orch <name>` and `fleet digest --orch <name>`, and load the fleet:fleet skill.": the successor starts before step 6 moves the registration, so its first session start gets no project re-brief. Folder trust is kept per account, so another account can stop at the trust dialog; `--accept-trust` answers it, which is right here because this session already works in that folder.
5. Check the result: `ok: true`, with status `working` or a note that the prompt shows as sent. Read the new pane once to see that it reads the handoff or continues the work.
6. If you orchestrate, move the registration to the successor: `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/fleet" orch claim --pane <new pane_id> --replace`. The orch keeps its name, its lanes and its ORCH.md; the claim clears the recorded session. From then on, the SessionStart hook re-briefs the successor from the project home at each session start, not this pane, and the successor's first `digest` after the claim shows what happened since your last one and records its session, which lets the hook re-brief it after compaction without git. Until the claim, the successor's digest only reads. With an old FLEET.md, set its `Orchestrator:` line to the new `pane_id` instead.
7. Tell the user: the new pane, account, model and handoff file. Then stop. Do no more work here: two sessions in one checkout conflict. Do not close this pane; the user closes it (`/exit`).

## Lane

1. Choose a fresh token, for example `HANDOFF READY 1530` (the time now).
2. Ask the lane to write its handoff:
   ```bash
   python3 "${CLAUDE_PLUGIN_ROOT}/scripts/fleet" send <pane> --text "Stop at the next safe point and commit finished work. Write .fleet/HANDOFF.md from the HANDOFF template in ${CLAUDE_PLUGIN_ROOT}/skills/fleet/references/templates.md, end it with the line <token>, then stop."
   ```
3. Wait in the background: `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/fleet" watch <pane> --marker "<token>" --file .fleet/HANDOFF.md`.
4. Retire the old agent and keep the pane: `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/fleet" retire <pane>`.
5. Start the successor in the same pane:
   ```bash
   python3 "${CLAUDE_PLUGIN_ROOT}/scripts/fleet" spawn --pane <pane> --role impl --name <label> --agent <agent> \
     [--account <account>] [--model <model>] [--effort <effort>] [--permission-mode <mode>] --accept-trust \
     --prompt "Read .fleet/HANDOFF.md, then .fleet/BRIEF.md and .fleet/STATUS.md, and continue this lane."
   ```
   Account change only, with healthy context: skip steps 1 to 3. Note the lane's `session_id` from `status --json`, retire it, then `spawn --pane <pane> --role impl --account <account> --accept-trust --resume <session id> --prompt "Continue this lane from where you stopped."`.
6. Nothing to record by hand: the log holds the retire and the new spawn with its account and model, and `fleet board` shows the new pane. With an old FLEET.md, update the lane's row there: pane, account, model.

Wersje

RepozytoriumWynikLicencja
Ta strona · rubycatco/herdr-fleet100MIT
lumpen-mya/claude-handoff100MIT
generous-corp/pulp100MIT
Ovid/paad100MIT
Ovid/paad100MIT
Ovid/paad100MIT
webdevnerdstuff/claude-marketplace100MIT
terencebristol/terencebristol-toolkit100MIT
verkyyi/claude-fleet100MIT

Migawka bazy z 13.11.2026 · wersja paczki c4f054e4b81a (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100hand-over
    Przekazuje pracę sesji nowej sesji, zanim wypełni się kontekst: pisze notatkę z szablonu roli i może uruchomić następną sesję w nowej karcie.
  • 100auto-handoff
    Przekazuje bieżącą sesję nowemu agentowi: zapisuje plik przekazania, uruchamia następcę i sprawdza jego pierwszą odpowiedź.
  • 100accounts
    Pokazuje konta remudy, zużycie i konto każdego panelu agenta, a przy pracy wybiera konto wg reguł użytkownika.
  • 90adapt
    Przenosi bieżącą sesję do innego agenta w nowym panelu, po przekazaniu notatki, przed zamknięciem poprzedniego.
  • 100hand-over
    Przekazuje pracę bieżącej sesji świeżej sesji przed zapełnieniem kontekstu: pisze notatkę przekazania według szablonu roli, a z poleceniem „start” otwiera następcę w nowej karcie terminala, który przejmuje zadanie.
  • 100new
    Przekazuje bieżące zadanie nowej sesji Claude Code, zapisując dokument przekazania i uruchamiając sesję w aplikacji lub w terminalu.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.