session-handoff
/session-handoff
Przygotowuje podsumowanie zakończenia sesji w czacie: decyzje, zmiany, kluczowe pliki, weryfikację i otwarte pytania.
- Autor
- mtoyloy ↗
- Repozytorium
- toyloy-architecture ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 26.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 26.10.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
Przygotowuje podsumowanie zakończenia sesji w czacie: decyzje, zmiany, kluczowe pliki, weryfikację i otwarte pytania.
Wyzwalacze z opisu
Oryginalny opis (EN)
Use when the user says "session handoff", "wrap up session", "hand off", "handoff summary", or wants a structured end-of-session summary before clearing context. Produces a chat-only handoff covering decisions, shipped changes, key files, running state, verification steps, deferrals, and open questions so a fresh agent can continue seamlessly.
Jak działa
- When to invoke
- How to produce the summary
- Output template - use exactly this structure, every time
- Hard rules
- Anti-patterns - do not do these
Podgląd SKILL.md
--- name: session-handoff description: Use when the user says "session handoff", "wrap up session", "hand off", "handoff summary", or wants a structured end-of-session summary before clearing context. Produces a chat-only handoff covering decisions, shipped changes, key files, running state, verification steps, deferrals, and open questions so a fresh agent can continue seamlessly. --- # Session Handoff Produce a repeatable end-of-session summary so the user can `/clear` and start a fresh agent without losing continuity. The next agent should be able to pick up by reading this summary alone. This is a **context-handoff artifact**, not a status report. The audience is a future instance of you, not a stakeholder. ## When to invoke User says: "session handoff", "wrap up session", "hand off", "handoff summary", "let us wrap up", "summarize before I clear", or any near-equivalent. Also invoke proactively if the user says they are about to `/clear` without having run it yet. ## How to produce the summary 1. **Review the full conversation**, not just the last few turns. Handoffs miss things when they only summarize recent context. 2. **Pull state from these sources (in order):** - Plan files referenced this session (check the plans folder if a plan was mentioned). - TodoWrite state - any in-progress or pending tasks. - Background processes you started with `run_in_background` - shell IDs are load-bearing for the next agent. - Files created or modified this session - you know what you touched; do not grep to re-discover. - Memory files written or updated (the project's memory folder). - Unresolved questions - things you asked the user that never got a clear answer, or things the user asked that got deflected. 3. **Do NOT audit the filesystem.** This is synthesis of what happened in THIS session. No `git log`, no broad `Glob` sweeps. If you did not touch it this session, it does not belong here. 4. **Produce the output in chat, then save a copy.** Append the same handoff to `handoffs/YYYY-MM-DD.md` (today's date; create the file if missing, otherwise add to the end under a `---` divider with the time). This is what the executive assistant agent reads. Do not update memory. ## Output template - use exactly this structure, every time ``` # Session Handoff - <one-line title of what this session was about> ## Where it started <2-3 sentences: what the user asked for, key framing or constraints that emerged> ## Decisions locked + what shipped - <decision or change> - <why, and where it lives (absolute path if a file)> - ... ## Key files for next session - `<absolute path>` - <why the next agent should read this first> - Plan file: `<path>` (if a plan drove the session) - Memory files touched: `<paths>` (if any) ## Running state - Background processes: <shell IDs + what they are + how to kill> - or "none" - Dev servers / ports: <url + port> - or "none" - Open worktrees / branches: <paths> - or "none" ## Verification - how to confirm things still work - `<command>` - <expected outcome> - ... ## Deferred + open questions - Deferred: <item> - <why pushed to later> - Open: <question needing the user's input> - <context> ## Pick up here <1-2 sentences: the single most likely next action for a fresh agent> ``` ## Hard rules 1. **Chat output plus one saved copy** in `handoffs/`. No other files. Never update memory from this skill. 2. **Never invent state.** If a section has nothing to report, write "none" - do not omit the section. Structure stability is the whole point. 3. **Absolute paths always.** The next agent may have a different working directory. 4. **If a plan file drove the session, name it first** in "Key files" so the next agent reads it before anything else. 5. **No emojis, no hype, no "great job" summaries.** Terse and concrete - paths, commands, shell IDs, decisions. Match the tone of a seasoned engineer handing off at end-of-shift. 6. **Background process IDs are critical.** If you started any `run_in_background` shells, their IDs must appear in "Running state" with the kill command - the next agent cannot find them otherwise. ## Anti-patterns - do not do these - Summarizing the last 3 turns and calling it a handoff. - Listing files by relative path. - Skipping the "Running state" section because "nothing is running" - write "none" instead. - Writing the summary anywhere other than `handoffs/YYYY-MM-DD.md`. - Adding a "what went well / what went poorly" retrospective. This is not a retro. - Recommending next steps beyond the single "Pick up here" line. The next agent decides; you just hand off.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · mtoyloy/toyloy-architecture | 100 | MIT |
| iuliandita/skills | 100 | MIT |
| cardene777/agent-shuriken | 100 | MIT |
| mcorbett51090/ravenclaude | 100 | MIT |
| upex-galaxy/agentic-qa-boilerplate | 100 | MIT |
| adobe/spectrum-web-components | 100 | Apache-2.0 |
| FrancoStino/opencode-skills-collection | 100 | MIT |
| h2xd/skills | 100 | MIT |
| davila7/claude-code-templates | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki a4be9442c57c (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
- 100fresh-start-handoff
Pisze kompletne przekazanie, żeby pracę można było kontynuować w nowym czacie: cele, decyzje, ograniczenia i otwarte pytania. - 100handoff
Czyta albo zapisuje dokument przekazania projektu: zapis opisuje zbudowane elementy i otwarte pytania, a odczyt wczytuje dokument i wskazane pliki na początku sesji. - 90handoff
Pisze dokument przekazania, by inny agent lub nowa sesja mogła kontynuować pracę bez ponownego tłumaczenia. - 90handoff
Kompaktuje bieżącą rozmowę w samodzielny opis dla nowego agenta: wykonane prace, pozostałe zadania i kluczowe decyzje. - 100context-summary
Tworzy zwięzłe podsumowanie sesji do wklejenia w nowej rozmowie, żeby kontynuować pracę bez ponoszenia kosztu całego czatu. - 100handoff
Zapisuje stan pracy przy końcu sesji: sprawdza stan repozytorium, ukrywa sekrety i spisuje cel, decyzje, pytania oraz kolejne działania.