メニュー
Structured context brief and claim transfer for thread handoff between agents. Use when the user says "/session:thread:handoff", "/thread:handoff", "hand off this thread", "transfer thread to", "pass this to another agent", "handoff", or "take over thread".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Session dashboard showing thread timeline, agent roster, and commit counts. Use when the user says "/session:dashboard", "show dashboard", "session overview", "session summary", "what's happening in this session", or "agent activity".
Write a reflective debrief for a session thread. Use when closing a thread, after "/session:debrief", "/debrief", "write a debrief", "debrief this thread", or when session:thread:land invokes it after the done verdict passes.
Read all session debriefs, synthesize patterns, and produce a retrospective. Use when the user says "/session:retro", "retrospective", "session retro", "what patterns do we see", "synthesize debriefs", or "review all debriefs".
Manage sessions, threads, and session wiring. Use when the user mentions sessions, threads, plans, reviews, claims, debriefs, or session sync/doctor. Also triggered by natural language like "create a thread", "what threads are open", "close this thread", "show me the session", "sync the session", "check session health", "claim the frontend thread", "lock the plan", "add a task", or "what's the session status".
Perform a real closeout audit for the thread-scoped task and, when requested, land it through commit, push, and CI. Use when the user says "/session:thread:land", "are you done", "can we close this", "is anything still open", "wrap this session up", or wants to end the thread without losing unfinished work, buried follow-ups, or useful loose ends.
| name | session:thread:handoff |
| description | Structured context brief and claim transfer for thread handoff between agents. Use when the user says "/session:thread:handoff", "/thread:handoff", "hand off this thread", "transfer thread to", "pass this to another agent", "handoff", or "take over thread". |
| argument-hint | <thread-slug> [to <agent-name>] |
Create a structured handoff brief for a thread and transfer the claim to another agent.
<thread-slug> is required, to <agent-name> is optional.~/.claude/skills/session/scripts/session.sh thread show <slug> to get thread state.tasks.md — note completed vs remaining items.plan.md or done.plan.*.md if they exist — note the approach.thread claim check <slug>.Write a concise handoff to stdout (do NOT create a file):
## Thread Handoff: <slug>
**From:** <current claimer or "unclaimed">
**To:** <target agent or "next available">
**Generated:** <ISO timestamp>
### Status
<1-2 sentences on where things stand>
### Completed
<checked items from tasks.md>
### Remaining
<unchecked items from tasks.md>
### Key Context
<important decisions, constraints, or gotchas from plan/tasks/reviews>
### Files
<list of thread files with their status>
If to <agent-name> was specified:
thread claim release <slug>thread claim set <slug> --agent <agent-name>If no target agent specified, just output the brief without transferring.
If the thread doesn't exist, say so and list available threads via thread list.