session-handoff

Redirect handoff requests to the canonical session-end workflow.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/BryceEWatson/claude-global-skills --skill session-handoff-bryceewatson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-handoff
Source: https://github.com/BryceEWatson/claude-global-skills/tree/main/session-handoff
Command: npx skills add https://github.com/BryceEWatson/claude-global-skills --skill session-handoff-bryceewatson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mid-flight session work often lacks a clear, canonical end-state and handoff path, leading to fragmented records and lost continuity.

Core Features & Use Cases

  • Alias for session-end; routes in-flight handoffs to the canonical workflow.
  • Generates an evidence-grounded closing record and a ready-to-paste continuation prompt.
  • Ensures no duplicate logic is implemented; relies on session-end for all behavior.

Quick Start

Invoke the session-end skill to close out a mid-flight session and continue with the resumed work.

Frequently Asked Questions about session-handoff

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

FAQPage Schema
How do I handoff an in-flight session without losing continuity?

To handoff an in-flight session without losing continuity, this skill routes mid-flight requests to a canonical closing workflow, generating an evidence-grounded record and a ready-to-paste continuation prompt.

What is the best way to close a mid-flight session and preserve artifacts?

The best way to close a mid-flight session and preserve artifacts is to route the handoff to a canonical session-end workflow, which finalizes decisions and creates an evidence-grounded closing record for future continuation.

How do I generate a continuation prompt for a paused workflow?

You generate a continuation prompt for a paused workflow by delegating the in-flight session to a canonical session-end workflow, which produces a ready-to-paste prompt grounded in the session's evidence.

Does this workflow duplicate the session-end logic for closing records?

This workflow does not duplicate session-end logic for closing records; it acts as a lightweight alias that delegates all behavior to the canonical session-end workflow to preserve session integrity.

When do I need to use a handoff alias for an in-flight session?

You need to use a handoff alias for an in-flight session when mid-flight work lacks a clear canonical end-state and you must finalize decisions and artifacts to prevent fragmented records and lost continuity.