handoff-create

Create a directed Markdown handoff artifact for a future session continuation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a work session ends mid-task, the next session often lacks the context needed to resume correctly. This Skill captures durable, directed work context — intent, current state, decisions, and next steps — as a stored Markdown handoff artifact tied to a git branch, so a future session, agent, or teammate can pick up exactly where things left off. ## Core Features & Use Cases - Directed handoff creation: Composes a concise Markdown artifact with a canonical structure (Context, Current State, Decisions, Next Steps, Investigation Sources) focused on a specific continuation goal. - Semantic slug derivation: Derives a normalized, collision-checked slug from the artifact content via the ns handoff create command, with support for explicit user-supplied slugs. - Branch-scoped storage: Stores the artifact in Branch Memory under the handoff namespace on a confirmed git branch, with collision protection and recovery-only raw brmem fallback. - Use Case: Before ending a coding session with unfinished review feedback, ask the agent to create a handoff; it records what was done, what remains, and which files to inspect, then stores it on the current branch for the next session to resume. ## Quick Start Ask the agent to create a handoff for the current branch describing what the next session should continue, for example: create a handoff so a future session can finish addressing the review feedback on this branch.

Frequently Asked Questions about handoff-create

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

FAQPage Schema
How do I create a handoff for a future session?

Ask the agent to create a handoff and state what the future session should continue. The skill composes a Markdown artifact with context, current state, decisions, and next steps, then stores it on the confirmed git branch using ns handoff create.

How do I resume work from a stored handoff?

Resuming from an existing handoff is handled by the companion handoff-pickup skill, not handoff-create. Lifecycle operations like copy, move, or delete belong to the handoff umbrella skill.

What information does a handoff artifact contain?

Each handoff contains a continuation focus, context, current state, decisions and findings, concrete next steps, investigation sources such as session logs and related files, and useful commands or locators. It stays terse and self-contained.

What happens if a handoff with the same slug already exists?

The ns handoff create command refuses to overwrite an existing artifact by default and reports a collision. Creation stops unless the user explicitly asks to replace the existing handoff.

What should not be stored in a handoff?

Do not store secrets, credentials, binary data, generated build output, or large logs in a handoff. Store paths to useful logs and files instead of copying their contents into the artifact.