---
name: handoff-context
description: Generate a portable conversation handoff blob that distills the important flow, decisions, facts, open questions, and next steps from the current conversation so it can seed a fresh conversation.
compatibility: Created for Zo Computer
metadata:
  author: rob.zo.computer
  version: "0.1"
---

# handoff-context

Create a single portable distillation of the **current conversation** that can be pasted into a brand new conversation to bring it up to speed fast.

## When to use

Use this skill when the user wants to:
- continue work in a fresh thread without re-explaining everything
- capture the important state of a long conversation
- hand off context between sessions
- summarize progress, decisions, constraints, and pending work in a reusable format

## Core behavior

When this skill is invoked, review the conversation **so far** and produce exactly one portable handoff block in a fenced code block.

The output should:
1. Capture only the important flow of the conversation
2. Preserve key facts, decisions, constraints, file paths, URLs, commands, and outputs that matter
3. Omit chatter, repetition, dead ends, and incidental detail
4. Be self-contained so a new conversation can continue effectively
5. Be generic — not tied to any one project or domain

## Output format

Always return a short intro line followed by a single fenced code block.

Preferred fence language: `text`

Structure the blob like this:

```text
HANDOFF CONTEXT

Goal:
- What the user is trying to accomplish

Current state:
- What has already been done
- What exists now
- What was learned or confirmed

Important facts:
- Key details, identifiers, file paths, URLs, decisions, constraints

Open questions / unresolved points:
- Anything still unclear or undecided

Next best steps:
1. Concrete next action
2. Next action after that

How to continue:
- Brief instruction to the next assistant on how to pick up the work
```

## Compression rules

- Prefer dense, high-signal bullets
- Keep chronology only where it matters for understanding
- Include exact file paths, route paths, IDs, env var names, and command names when important
- Include specific errors or blockers only if they still matter
- If there are multiple workstreams, group them clearly
- If there are no open questions, say `- None`
- If the conversation contains sensitive info, include only what is necessary for continuation

## Style rules

- Be concise but complete
- Do not narrate your own reasoning process
- Do not mention irrelevant tool chatter
- Do not wrap the handoff in extra explanation beyond a minimal intro line
- Do not output multiple alternative handoff blobs

## Success criterion

A new assistant should be able to read the blob alone and continue the work with minimal loss of context.

## Example invocation

Typical user requests that should trigger this skill:
- "make me a handoff blob"
- "distill this conversation so i can move to a new thread"
- "generate portable context for a fresh convo"
- "use handoff-context"