ln-handoff

Capture in-progress conversation artifacts and session states into a portable handoff document.

7|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/hashintel/brunch --skill ln-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-handoff
Source: https://github.com/hashintel/brunch/tree/main/.agents/skills/ln-handoff
Command: npx skills add https://github.com/hashintel/brunch --skill ln-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill enables capturing ephemeral chat and workspace states into a portable handoff document before they are lost or integrated into permanent records.

Core Features & Use Cases

  • State Capture: Identifies active and in-progress phases, including scope cards, plan drafts, and review findings from ongoing conversations.
  • In-flight Artifact Collection: Reproduces volatile but critical artifacts such as scope, design outputs, and investigative evidence in full fidelity.
  • Use Case: When a session is ending unexpectedly, this Skill summarizes current work to facilitate seamless resumption without losing context or redoing investigations.

Quick Start

Invoke this Skill at the end of a session to generate a comprehensive handoff document summarizing ongoing work and in-progress artifacts.

Frequently Asked Questions about ln-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture in-progress conversation state before a session ends?

To capture in-progress conversation state, invoke this Skill at the end of a session to generate a structured handoff document. It identifies active phases, scope drafts, and review findings to ensure seamless work continuation without losing context.

What is the best way to preserve volatile artifacts during collaborative debugging?

The best way to preserve volatile artifacts during collaborative debugging is using state capture to reproduce design outputs and investigative evidence in full fidelity. This prevents critical evidence from being lost when an unexpected session termination occurs.

Can I use a state capture handoff for iterative design workflows?

Yes, you can use a state capture handoff for iterative design workflows. It explicitly supports preserving plan drafts and design outputs, ensuring all decisions and artifacts are saved for context transfer and future reference across sessions.

How do I transfer scope cards and review findings for workflow continuation?

You transfer scope cards and review findings by triggering the handoff generation process. It compiles in-flight artifacts from your ongoing conversation into a portable document for seamless resumption of your research or design work.

When do I need to generate a structured handoff document?

You need to generate a structured handoff document when a session is ending unexpectedly or when transitioning tasks. It summarizes your current work, preventing the loss of ephemeral chat and workspace states before they are integrated into permanent records.

Does the handoff document include in-flight artifact collection?

Yes, the handoff document includes in-flight artifact collection. It reproduces volatile but critical artifacts such as scope, design outputs, and investigative evidence in full fidelity to ensure comprehensive context transfer.