handoff

Manages durable branch-scoped handoff artifacts for continuing work across sessions.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/nseng-ai/ns --skill handoff-nseng-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/nseng-ai/ns/tree/main/skills/incubating/handoff/handoff
Command: npx skills add https://github.com/nseng-ai/ns --skill handoff-nseng-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Work context is lost when a coding session ends, forcing you to reconstruct intent, decisions, and next steps from scratch. This Skill defines a durable, branch-scoped handoff artifact stored in Branch Memory so a future session can pick up exactly where you left off. ## Core Features & Use Cases - Shared lifecycle model: Defines the handoff vocabulary, storage contract (namespace handoff, key <slug>.md), and branch/list scoping that the step skills handoff-create and handoff-pickup rely on. - Admin and cleanup operations: Inspect, copy, move, delete individual handoffs, and garbage-collect handoffs whose local branch was deleted, via ns handoff commands or direct brmem storage operations. - Safety posture: Refuses collisions, overwrites, and destructive changes without explicit user intent, and prefers dry-run previews before mutation. - Use Case: Before ending a session mid-refactor, create a handoff artifact naming the continuation focus; days later, list handoffs across branches, pick up the slug, and resume with full context — then garbage-collect handoffs from deleted branches. ## Quick Start Ask the agent to list all handoffs across branches and pick up the one for your current task so you can resume the recorded next step.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I create a handoff to continue work in a later session?

Use the handoff-create step skill or run ns handoff create with an optional slug and branch. It writes a concise Markdown artifact into the handoff Branch Memory namespace keyed as <slug>.md, scoped to the branch that owns the continuation context.

How do I list and pick up an existing handoff?

Run ns handoff list with --branch or --all to see inventory, then use ns handoff pickup <slug> or the /ns:handoff:pickup command. Listing and pickup requests route through the handoff-pickup step skill, which presents the summary before you proceed.

How do I delete a handoff or clean up stale ones?

Delete one handoff by exact slug with ns handoff delete [--branch <branch>] [--yes] <slug>. For handoffs whose local branch was deleted, preview with ns handoff gc --dry-run and confirm before running with --force.

What is the difference between a handoff and in-session compaction?

A handoff is a durable, directed artifact stored in Branch Memory for a specific future continuation, surviving across sessions and branches. In-session compaction only summarizes the current conversation and stores nothing durable, so it cannot be picked up later.

When should I use brmem directly instead of ns handoff commands?

Use brmem --namespace handoff only for storage, recovery, or admin cases with no ns handoff helper, such as copying or moving one handoff between branches with --key-glob '<slug>.md'. Prefer the ns handoff command face whenever it exists.