handoff

Record session context notes with blockers and next steps to the brain.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/sanskarbasnet/fstack --skill handoff-sanskarbasnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/sanskarbasnet/fstack/tree/main/handoff
Command: npx skills add https://github.com/sanskarbasnet/fstack --skill handoff-sanskarbasnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams lose context when stepping away from work. This Skill writes a structured handoff note to the brain, capturing what you're doing, what's blocking you, and what should happen next.

Core Features & Use Cases

  • Auto handoff on SessionEnd — fires lightly when there are uncommitted changes.
  • Rich handoff — explicit handoff via /handoff captures: Note, Blocker, Next step, and optional target agent.
  • Brain sync visibility — handoffs surface in the next synchronization cycle for the intended recipient.

Quick Start

Run /handoff with a concise note to record your current state, blockers, and next steps.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I capture session context before stepping away to prevent lost work?

To capture session context before stepping away, record a structured handoff note to the brain. This preserves your current work, blockers, and next steps, ensuring the next agent receives the context during synchronization.

What is the best way to document blockers and next steps for a team collaboration workflow?

The best way to document blockers for team collaboration is using a structured handoff format. It explicitly records the note, blocker, next-step, and an optional destination agent to sync context efficiently.

Can I automatically save work context when a session ends?

Yes, you can automatically save work context when a session ends. The auto-handoff feature fires lightly at SessionEnd to preserve context, particularly when there are uncommitted changes.

How do I trigger an explicit handoff with my current notes and blockers?

Trigger an explicit handoff by running the /handoff command with a concise note. This manually captures your current state, blockers, next steps, and targets a specific agent if needed.

Does the handoff note surface automatically for the next agent in the workflow?

Yes, the handoff note surfaces automatically for the next agent in the workflow. Recorded handoffs appear in the next brain synchronization cycle for the intended recipient.

Are there limitations to the auto-handoff feature during session end?

A limitation of the auto-handoff feature is that it fires lightly at session end, primarily triggering only when uncommitted changes are detected, rather than capturing a full context summary.