Przejdź do treści
Biblioteka skilli
Zarządzanie i produkt · Planowanie

handover

/handover

Przygotowuje przekazanie pracy innej osobie lub zespołowi: prawdziwy stan pozycji, decyzje z uzasadnieniem, pułapki, dostępy do przekazania, kontakty i pytania do odchodzącego zadane przed jego wyjściem.

Repozytorium
aiteamkit ↗
Licencja
MIT
Ostatnia zmiana repozytorium
24.10.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
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 24.10.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

Przygotowuje przekazanie pracy innej osobie lub zespołowi: prawdziwy stan pozycji, decyzje z uzasadnieniem, pułapki, dostępy do przekazania, kontakty i pytania do odchodzącego zadane przed jego wyjściem.

Wyzwalacze z opisu

handoverhand overbàn giaochuyển giao công việctakeoverleaving引き継ぎ引継ぎ資料

Argumenty

/handover [--from <name>] [--to <name>] [--scope <area>] [--phase|--offboard] [--lang <code>] [--out <path>]
Oryginalny opis (EN)

Hand work over to another person or team so nothing depends on the leaver's memory: the true state of each item, decisions and why they were made, the traps, the credentials and access to transfer, the contacts, and the questions only the leaver can answer, asked before they go. Use when a member leaves or rotates, when a phase ends, at a vendor-to-client handover, or before a long absence. Triggers on: "handover", "hand over", "bàn giao", "chuyển giao công việc", "takeover", "leaving", "引き継ぎ", "引継ぎ資料", "knowledge transfer", "offboarding", "/atk:handover".

Jak działa

  1. Scope
  2. Roles
  3. Invocation
  4. Workflow
  5. Output
  6. Ticket
  7. Definition of done
Sekcje z nagłówków SKILL.md, w oryginale · 101 linii, 718 słów
Podgląd SKILL.md
---
name: handover
description: >
  Hand work over to another person or team so nothing depends on the leaver's memory: the true state
  of each item, decisions and why they were made, the traps, the credentials and access to transfer,
  the contacts, and the questions only the leaver can answer, asked before they go.
  Use when a member leaves or rotates, when a phase ends, at a vendor-to-client handover, or before
  a long absence.
  Triggers on: "handover", "hand over", "bàn giao", "chuyển giao công việc", "takeover", "leaving",
  "引き継ぎ", "引継ぎ資料", "knowledge transfer", "offboarding", "/atk:handover".
argument-hint: "[--from <name>] [--to <name>] [--scope <area>] [--phase|--offboard] [--lang <code>] [--out <path>]"
---

# Work Handover (`atk:handover`)

Captures the part of a project that lives in one person's head. It is written while that person is
still available, and it is validated by the receiver reproducing something, not by the leaver
declaring it complete.

## Scope

Handles: inventorying the in-flight work with its true state, recording decisions and their reasons,
listing traps and workarounds, planning the access and credential transfer, naming contacts, and
extracting the knowledge that exists nowhere else.

Does NOT handle: transferring credentials itself, which is a human action through the team's secret
manager; onboarding the receiver onto the project (`atk:onboard`); or approving the handover.

## Roles

The leaver authors. The receiver validates and is the approver: a handover is accepted by the person
taking it, never by the person leaving. Tech Lead arbitrates gaps. PM owns access revocation. See
`shared/team-roles.md`.

## Invocation

```bash
/atk:handover --from An --to Binh   # Person to person handover
/atk:handover --scope payments      # Limit to one area or module
/atk:handover --phase               # End-of-phase handover between teams or vendors
/atk:handover --offboard            # Member leaving: adds access revocation and knowledge extraction
/atk:handover --lang vi             # Write in Vietnamese
/atk:handover --out <path>          # Override the default output path
```

## Workflow

```
[1. Inventory] -> [2. True state] -> [3. Decisions and traps] -> [4. Access] -> [5. Validate]
```

Before step 1, read `.atk/overrides/handover.md` when it exists, per rule 7 of `shared/team-roles.md`.
Then, before anything else, create this run's trace, `<docs root>/derived/traces/handover/<run-id>.md`:
read the kit's `shared/run-trace.md` and do what it says before the file, at each step, and at the close.

### 1. Inventory

Gather from the tracker, open branches and pull requests, uncommitted work, review queue, scheduled
jobs owned by the leaver, recurring duties, and any environment or service where they are the only
admin. Search git history for files only this person has touched: those are the risk.

### 2. True state, not ticket state

For each item: what is actually done, what looks done but is not, what is blocked and by whom, and
what the next concrete step is. Ticket status is evidence, not truth. Where they disagree, record
both and say which is real.

### 3. Decisions and traps

Record decisions whose reason is not in the code: why a library was chosen, why an obvious approach
failed, what a client agreed verbally. Then the traps: the fragile deploy step, the flaky test and
what actually causes it, the service that must be restarted in an order, the data that looks wrong
but is not.

Interview for what only this person knows. Ask, one at a time: what would break if you were
unreachable tomorrow, what do you check that nobody asked you to check, what would you warn your
replacement about in the first hour.

### 4. Access and duties

List every account, credential, key, and duty to transfer, with the path in the secret manager and
the person who approves the transfer. Never paste a secret into the document. Add the revocation
checklist with dates under `--offboard`, and name who takes each recurring duty.

### 5. Validate

The receiver runs the environment, opens one in-flight item, and follows one runbook, then signs.
Unanswered questions stay in the document as `OPEN` with the person who must now answer them.

## Output

Written to `docs/records/handover/<date>-<from>-to-<to>.md` per `shared/artifact-paths.md`. Sections: front
matter, scope, work inventory with true state, decisions, traps, access and duties, contacts, open
questions, and the receiver's validation checklist.

Putting it where the team can see it is `atk:git`, which follows the artifact section of
`shared/finalize-steps.md`: the branch, the commit, and the judgement about whether this one belongs
in a pull request for its approver to read. Whether it is committed at all is the persistence group
it falls into, per `shared/artifact-paths.md`.

## Ticket

Follow `shared/ticket-adapters.md`. Reassign in-flight tickets only after the receiver accepts, and
link the handover from each.

## Definition of done

- [ ] Every in-flight item states its true state, not only its ticket status.
- [ ] Files touched by only the leaver are identified and covered.
- [ ] No secret value appears in the document, only its location and approver.
- [ ] Every recurring duty has a new named owner.
- [ ] The receiver validated by running something, and signed as approver.
Pliki w paczce (2)
  • SKILL.md 5 KB
  • evals/trigger_evals.json 2 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · lamngockhuong/aiteamkit100MIT
adobe/skills100Apache-2.0
zambodotdev/zambo-skills100MIT
OzturkArda/claude-session-cap100MIT
lilly-logic-labs/lll-skills90MIT
tenaciousduck/ai-studio-website-skill90MIT
randommonicle/claude-skills90Apache-2.0
eai-org/agent-toolkit90MIT
Open-RUA/uni-robot-agent90MIT

Migawka bazy z 13.11.2026 · wersja paczki 9a18a8ce9b5c (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

  • 90client-exit-and-handover-pack
    Przygotowuje profesjonalne przekazanie odchodzącego klienta: kompletne pliki, bez wstrzymywania dostępu i bez niedomkniętych spraw.
  • 100work-handover
    Generuje pełną dokumentację przekazania na koniec sesji, przy długiej przerwie lub przekazaniu pracy innej osobie.
  • 100knowledge-transfer
    Prowadzi przekazanie wiedzy o projekcie: eksport (analiza projektu i pamięci agentów, archiwum handover.zip z dokumentem wdrożeniowym, przefiltrowanymi pamięciami i manifestem pominięć) oraz import u nowej osoby.
  • 100resumable-handover
    Przygotowuje wersjonowany dokument przekazania pracy z jednym konkretnym punktem wznowienia dla osoby przejmującej.
  • 90onboarding-and-offboarding
    Projektuje doświadczenie wejścia i odejścia z firmy: gotowość pierwszego dnia, dojście do produktywności, przejęcie wiedzy i czyste odejścia.
  • 86project-handover
    Przekazuje raporty projektu i zadania do przeglądu między wykonawcą a recenzentem przez lokalną księgę przekazań.

Uwagi i zgłoszenia

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