Skip to content
Skills Library
AI & agents · Writing

session-handoff

/session-handoff

Preserve progress, decisions, blockers, and continuation steps when work will continue in another agent session or agent. Use before a context reset, ownership transfer, or long pause; do not trigger for an ordinary final summary.

Licence
GPL-3.0
Last repository change
10.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
12
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.

Licence

GPL-3.0, otwarta.

What it does and when to use it

Preserve progress, decisions, blockers, and continuation steps when work will continue in another agent session or agent. Use before a context reset, ownership transfer, or long pause; do not trigger for an ordinary final summary.

Original author description

Preserve progress, decisions, blockers, and continuation steps when work will continue in another agent session or agent. Use before a context reset, ownership transfer, or long pause; do not trigger for an ordinary final summary.

How it works

  1. Workflow
  2. Handoff Format
  3. Guardrails
Original SKILL.md headings · 55 lines, 287 words
SKILL.md preview
---
name: session-handoff
description: Preserve progress, decisions, blockers, and continuation steps when work will continue in another agent session or agent. Use before a context reset, ownership transfer, or long pause; do not trigger for an ordinary final summary.
metadata:
  blacktower-pack: core
  blacktower-kind: workflow
  blacktower-tier: core
  blacktower-capabilities: session continuation,context reset,ownership transfer,progress handoff,continuation record
  author: blacktower
  version: '2.0'
---

# Session Handoff

Create a compact, evidence-backed continuation record. Use the repository's
existing handoff convention; otherwise prefer `.blacktower/handoff.md`, unless
the user requests another location.

## Workflow

1. Re-read the goal, current plan, `git status`, recent commits, and relevant
   verification output.
2. Distinguish finished work from work merely attempted or discussed.
3. Record decisions and their reasons, especially choices not evident in code.
4. Name blockers, open questions, risky assumptions, and unrelated dirty files.
5. Give the next session the smallest safe continuation sequence with exact
   paths and commands.
6. On resume, verify the handoff against current repository state before acting.

## Handoff Format

```markdown
# Handoff: <task>

Date:
Branch and worktree:
Status: in-progress | blocked | ready-for-review

## Goal and scope
## Completed and verified
## Remaining work
## Decisions and rationale
## Blockers, risks, and open questions
## Key files and unrelated changes
## Exact continuation steps
```

Keep the handoff scannable. Include file paths, symbols, command outcomes, and
test status; omit conversational history that does not affect continuation.
Point to existing specs, issues, plans and artifacts instead of copying them.
Name the relevant skills and canonical source paths for the next task; do not
assume another client exposes the same Skill tool or integrations.

For longer-running context systems, load the relevant material in
`references/context-management/` and the optional templates in
`templates/context-network/`. Do not create a context network for a short,
single-session task.

## Guardrails

- Never claim tests passed when they were not run or did not complete.
- Preserve user-owned dirty changes and identify them explicitly.
- Do not include secrets, personal data, tokens, or transient credentials.
- A handoff is not a substitute for committing finished work when the user has
  requested a commit.
Files in this package (12)
  • LICENSE 1 KB
  • SKILL.md 2 KB
  • notices/blacktower-mit.md 1 KB
  • references/context-management.md 1 KB
  • references/context-management/context-driven-development.md 3 KB
  • references/context-management/context-network.md 9 KB
  • references/context-management/context-retrospective.md 2 KB
  • templates/context-network/decisions.md 2 KB
  • templates/context-network/discovery-file.md 2 KB
  • templates/context-network/glossary.md 1 KB
  • templates/context-network/node-template.md 2 KB
  • templates/context-network/status.md 1 KB

Versions

RepositoryScoreLicence
This page · PatrickFanella/generic-skills-legacy100GPL-3.0
iuliandita/skills100MIT
cardene777/agent-shuriken100MIT
mcorbett51090/ravenclaude100MIT
upex-galaxy/agentic-qa-boilerplate100MIT
adobe/spectrum-web-components100Apache-2.0
FrancoStino/opencode-skills-collection100MIT
h2xd/skills100MIT
davila7/claude-code-templates100MIT

Database snapshot: 13.11.2026 · package version d4e809aafd6b (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 82handoff
    Summarize the current conversation into a file so another session (or agent) can continue the work with little context. Use when the chat got long, a topic closed, or the person says "handoff", "let's move to a new session" or "save the state so I can continue later".
  • 90handoff
    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.
  • 100handoff
    Compact the current session into a handoff document so another agent or fresh session can continue the work. Use when user asks to hand off, transfer context, continue in another session, start a parallel agent, or preserve only the next-useful context instead of using /compact.
  • 100handoff
    Compact the current conversation into a handoff document so another agent or future session can continue the work without losing context. Use when ending a session, switching tasks, the context is getting long, or user says handoff, wrap up, save progress, or "continue this later".
  • 100session-handoff-prompt
    Create a concise continuation prompt that a fresh agent session can paste in to resume a long or degraded session. Use when the user asks for a handoff prompt, restart prompt, continuation prompt, context transfer, fresh-session resume, or a compact summary for opening a new…
  • 86handoff
    Write or update a HANDOFF.md so a fresh agent can continue this work. Use when the user says "handoff", "compact this", "context is full", or "/clear and continue".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.