session-dispatch

Generates pasteable work orders that hand unfinished builds or investigations to another Claude Code session.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/hacker-cb/claude-code-plugins --skill session-dispatch-hacker-cb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-dispatch
Source: https://github.com/hacker-cb/claude-code-plugins/tree/main/plugins/hcb-dev/skills/session-dispatch
Command: npx skills add https://github.com/hacker-cb/claude-code-plugins --skill session-dispatch-hacker-cb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a session encounters work it will not do itself, this Skill turns that work into a complete, self-contained order the user can paste into a fresh Claude Code session, so the receiving session has every decision, coordinate, and constraint it needs without any shared context. ## Core Features & Use Cases - Structured order template: Fills every slot of the shared order anatomy — settled facts, base pin, process to run, completion mode, merge authority, decision forks, and return format — so nothing is left ambiguous for the receiver. - Dispatch vs. handoff discrimination: Distinguishes unfinished work (dispatch) from finished work (session-handoff) and from wave-fanned batches (wave-dispatch), routing each to the right mechanism. - Return acceptance protocol: Defines what a valid return looks like and records the dispatched tag so the originating session can match and verify the answer when it arrives. - Use Case: You are mid-session and realize a bug fix belongs in a separate checkout. Invoke the skill to produce a pasteable order naming the base pin, the implementation-workflow to run, the merge authority, and exactly what the receiving session must report back. ## Quick Start Ask the assistant to dispatch the pending fix to another session using the session-dispatch skill, producing a pasteable order block.

Frequently Asked Questions about session-dispatch

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

FAQPage Schema
How do I hand off unfinished work to another Claude Code session?▼

Use session-dispatch to generate a pasteable order containing the ask, settled facts, base pin, the process to run, merge authority, and the expected return format. Paste the block into the new session, which then executes the work independently.

What is the difference between session-dispatch and session-handoff?▼

Session-dispatch is for work that is not yet done and must be executed by the receiving session. Session-handoff is for work already finished that another session only needs to receive. The discriminator is whether the work is complete.

Can I dispatch a question to another session?▼

No. Questions are answered in the current session by a subagent or workflow, never dispatched. Dispatch is reserved for executable work — a build or an investigation whose deliverable is recorded tracker state or a verdict.

When should I use wave-dispatch instead of session-dispatch?▼

Use wave-dispatch when a batch is fanned out of a coordinating master session, by chip or pasted wave order. Session-dispatch covers standalone orders written outside any wave, carried by the user to a fresh session.

What must a return from a dispatched order contain?▼

A return carries the order's tag on its first line, premises that did not survive, the deliverable in the terms asked, the decision at each fork, and what is left undone and why, plus branch, change request, and issue states.