handoff

Creates paste-ready context handoff prompts for transferring work slices to other agents or sessions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When splitting work across parallel agents, sessions, or git worktrees, context is easily lost or miscommunicated. This Skill packages the current workspace state, explicit decisions, and scope boundaries into a structured, agent-neutral prompt that another coding agent can pick up immediately. ## Core Features & Use Cases - Scoped context extraction: Gathers read-only git state (branch, status, diff stat) and explicit conversation decisions for a defined slice such as frontend, backend, QA, or migration. - Agent-neutral payload: Produces a Markdown handoff with goal, parent workspace state, assigned scope, decisions, constraints, first steps, and open questions, without assuming the receiver has any specific tooling. - Clipboard integration: Previews the payload in chat, then copies it using wl-copy, xclip, pbcopy, clip.exe, or clip, with a temp-file fallback for fragile shell quoting. - Use Case: You are mid-implementation and want a second agent to handle the QA slice. Ask for a QA handoff and receive a clipboard-ready prompt containing repo state, boundaries, and open questions. ## Quick Start Ask the agent to create a handoff for the frontend slice so another session can continue that work.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I hand off part of my coding work to another AI agent?▼

Define a clear slice such as frontend, backend, QA, or migration, then generate a handoff payload containing the goal, git branch and status, assigned scope, explicit decisions, and open questions. The payload is copied to your clipboard for pasting into the new session.

What should a context handoff prompt for a coding agent include?▼

Include the overall goal, parent workspace path and branch, working tree summary, diff stat, assigned scope boundaries, explicitly stated decisions, constraints, suggested first steps, and open questions. Avoid full diffs and unstated assumptions.

Does the handoff skill work with agents other than Claude Code?▼

Yes, the payload is agent-neutral and does not assume the receiver has Beislið, Claude Code, Codex, pi, or slash commands. It is plain Markdown that any coding agent can consume.

Can a handoff create a git worktree or branch automatically?▼

No, the handoff process is strictly read-only in the parent workspace except for clipboard copying. It never creates tickets, commits, branches, or worktrees; those steps must be done separately.

What happens if no clipboard tool is available for the handoff?▼

The skill checks for wl-copy, xclip, pbcopy, clip.exe, and clip in order. If none exist, it reports that copying failed and leaves the full payload printed in chat for manual copying.

When should I not use a handoff workflow?▼

Do not use it to resume the same work in the same session, to start a fresh ticket from a tracker, or to save long-term session memory. It is designed only for transferring a scoped slice to a separate agent or worktree.