handoff
/handoff
Pisze dokument przekazania, by inny agent lub nowa sesja mogła kontynuować pracę bez ponownego tłumaczenia.
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Pisze dokument przekazania, by inny agent lub nowa sesja mogła kontynuować pracę bez ponownego tłumaczenia.
Wyzwalacze z opisu
Argumenty
/handoff What will the next session be used for?
Oryginalny opis (EN)
Write a handoff document so another agent or a fresh session can continue this work. Use for "handoff", "hand this off", "write a handoff", "continue this in a new session" or "pass this to another agent". For deciding whether to compact or clear, use session-budget.
Jak działa
- Document structure
- Rules
Podgląd SKILL.md
---
name: handoff
description: Write a handoff document so another agent or a fresh session can continue this work. Use for "handoff", "hand this off", "write a handoff", "continue this in a new session" or "pass this to another agent". For deciding whether to compact or clear, use session-budget.
argument-hint: "What will the next session be used for?"
---
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Create a unique temporary directory with the platform's secure temp helper (for Node, `fs.mkdtempSync(path.join(os.tmpdir(), "handoff-"))`) and write `handoff.md` inside it. Report the absolute path.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
Preserve the actual receiving runtime and resolved role/model configuration under **Key context**. Do not inject orchestration defaults into an unrelated continuation. Writing a handoff does not launch a worker or change the active model.
When continuing a complete run, include its ledger and per-slice result paths
under **Pointers**, and preserve authorization, frozen gates, unresolved rulings,
and agent IDs needed to resume. The receiving Codex must verify agent liveness;
an ID from a previous session is not proof that a worker is still running.
## Document structure
The handoff is read by another agent, so its shape is fixed. Produce exactly these eight sections, in this order, with these headings verbatim. Lead with intent and next steps, not narrative history — a fresh agent should scan top to bottom and start working.
1. `# Handoff: <short title>` — one line naming the work.
2. `## Goal` — what the next session is trying to accomplish, in 1–2 sentences. If args were passed, this reflects them.
3. `## Current state` — what's done and working right now. Bullets, past tense.
4. `## Next steps` — the concrete actions to take next, ordered, each an imperative ("Wire up X", "Run Y"). The most important section: make it actionable from a cold start.
5. `## Open questions / blockers` — unresolved decisions, things waiting on someone, known risks.
6. `## Key context` — the non-obvious things: decisions made and why, gotchas, dead ends already ruled out. Skip anything a fresh agent could read straight from the code or the linked artifacts.
7. `## Pointers` — paths and URLs to the artifacts that hold the detail: PRDs, plans, ADRs, issues, branches, key files (`path:line`). Reference them; don't copy their contents in.
8. `## Suggested skills` — which skills the next session should use, if any, and for what.
## Rules
- Don't duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead — that's what **Pointers** is for.
- If a section has no real content, write `None.` under it rather than padding with filler or inventing items to fill space. An empty **Open questions** is fine; a fabricated one is not.
- Keep it tight. A handoff is a launchpad, not a transcript.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · borkweb/bork-ai | 90 | MIT |
| lumpen-mya/claude-handoff | 100 | MIT |
| generous-corp/pulp | 100 | MIT |
| Ovid/paad | 100 | MIT |
| Ovid/paad | 100 | MIT |
| Ovid/paad | 100 | MIT |
| webdevnerdstuff/claude-marketplace | 100 | MIT |
| terencebristol/terencebristol-toolkit | 100 | MIT |
| verkyyi/claude-fleet | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki f9c584324e30 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 1 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100session-handoff
Pakuje kontekst bieżącej sesji, by inny agent mógł kontynuować pracę bez zaczynania od zera. - 86handover
Pisze samodzielny prompt przekazania, aby nowa sesja Claude mogła kontynuować pracę, gdy kontekst się wyczerpuje. - 96write-handoff
Aktualizuje plik handoff.md zadania i zmienia jego status, żeby nowa sesja albo inna rola mogła kontynuować pracę. - 100document-handoff
Tworzy szczegółową dokumentację przekazania przed operacją /compact, żeby nowy agent ze świeżym kontekstem mógł płynnie kontynuować pracę, z opcjami --output i --linear-issue. - 100handoff-writer
Zamienia długą sesję w plik HANDOFF.md, by nowa sesja przejęła pracę bez czytania całej historii rozmowy. - 100session-handoff
Pisze lub aktualizuje plik handoff.md, by następny agent mógł dalej pracować: cel, postęp, próby i następne kroki.