Hand this session to a teammate so it lands in their inbox with everything they need. Pins where the work stands and what is next, adds them as an owner, and sends them the brief. Use when work should continue under someone else, when a decision is theirs, or when asked to pass, hand over, or assign a session.
Installs into .claude/skills of the current project.
Are you the author of Cast Pass?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/codecast-sh-cast-pass)
---
name: cast-pass
description: Hand this session to a teammate so it lands in their inbox with everything they need. Pins where the work stands and what is next, adds them as an owner, and sends them the brief. Use when work should continue under someone else, when a decision is theirs, or when asked to pass, hand over, or assign a session.
argument-hint: "<member> [note]"
---
A session passed without a brief is a transcript the teammate has to read
from the top. The pin and the message are what make it a handoff.
## Pin
`cast state --status blocked` with a first line that stands alone for
someone who has not read the thread, then what is verified, what is open,
and `Next:` naming the first thing they should do. If the work is more than
an hour deep, write the handoff doc first (`/cast-handoff`) and put its
id in the pin.
## Own
```bash
cast own <member> # adds them; the session sits in both inboxes
cast own <session> <member> # a different session of yours
```
They get a notification, and the session surfaces under Needs Input in
their inbox with your name on it. Use `cast disown` on yourself only if the
work is entirely theirs now.
## Brief
`cast send` to this session's id is pointless; the teammate reads the pin.
When the note argument is given, or when the pass needs a reason the pin
does not carry, post it where they will see it: the bound task
(`cast task comment <id>`) or the team channel with their handle
(`cast chat send --channel <id> "@<handle> …"`), one message. If the task
should change assignee, `cast task update <id> --assignee <member>`.
When the work lives in uncommitted or unpushed changes, the transcript
alone leaves them without the files. Name the command that recreates this
tree on their machine, in the pin and the message:
`cast ws acquire <name> --from <this session's short id>` gives them a
worktree on this session's branch with its changes as uncommitted work.
It reads the snapshot this machine's daemon last pushed to the remote
(every few minutes while it runs), so the last few minutes of edits may
not be in it yet.
Then stop. The next move is theirs.
