Vibebuddy Handoff

---
name: vibebuddy-handoff
description: Write a VibeBuddy task handoff for another local agent, preserving the writer's real session identity, decisions, authorization and unfinished work.
argument-hint: "Receiving agent and remaining task"
disable-model-invocation: true
---

# Hand off a VibeBuddy task

Read `.agents/skills/handoff/SKILL.md` and apply its writing discipline. This wrapper
adds the project's source identity and placement contract; it does not duplicate
the underlying skill or add a dispatch/start mechanism. If that local dependency
is unavailable, report the missing skill rather than pretending to have applied it.

For this repository, the location below overrides the underlying skill's default
temporary-directory destination. Save a new note under
`.scratch/<feature>/handoffs/<yyyy-mm-dd>-<from-agent>-<to-agent>.md` and link its
absolute path in the owning ticket's Comments. In a worktree, use the ticket's
established absolute `.scratch/<feature>/` root. Do not migrate old notes or
silently overwrite an existing same-day note; use a distinguishing agent/session
suffix in `<from-agent>` when needed.

Before writing, get the recorded facts for your own session (ADR-0023). Determine
your native ID as described below, then run:

```sh
vibebuddy-mcp facts '<agent>:<your-native-id>' --cwd "$PWD"
```

(or the MCP tool `vibebuddy_handoff_facts`). Paste its output at the very top of
the note, unchanged: its first four lines are the header below, and its
`## Facts (recorded by VibeBuddy, …)` section follows. Fill in `Ticket:` yourself;
the facts list the `.scratch/<effort>/` directories the session touched as
candidates. If your ID is not available, write the header by hand with
`Source session: unknown` and skip `facts`; if the tool answers "Not recorded",
keep its header and say so in Verification evidence. Never run `facts` for
another session's key to stand in for your own.

The first four lines are:

```text
Source session: <key or unknown>
Ticket: <absolute ticket path>
Branch: <actual branch>
Worktree: <absolute checkout path>
```

Determine your own native ID from your current runtime: Claude Code's known
hook/statusline session ID or this session's transcript path; Codex's thread ID;
Cursor's conversation ID; Grok's session ID. Prefix a known ID with
`claude-code:`, `codex:`, `cursor:` or `grok-build:`. If your own ID is not available,
write `Source session: unknown`. Never infer authorship from the newest session in
this project, a nearby timestamp, another agent's ID or a historical instruction.
When two agents share a checkout, the source remains the writer's own ID.

Use these sections: Goal, Settled decisions, Authorization, Current changes,
Verification evidence, Next steps, Suggested skills. Reference existing ticket,
plan, ADR, commit, diff and evidence paths instead of copying their contents.
Verification evidence has two parts: what the facts block shows ran (commands
and exit codes, files edited, git state) and what you conclude from it. A claim
the facts do not support is `[unverified]`, however sure the session felt.
Separate completed checks from proposed checks; mark uncertain claims
`[unverified]`. Redact secrets and unnecessary personal information. Never include
a daemon token or credentials. State the next concrete unfinished action and
preserve limits such as user-owned merging or configuration changes.

On the Mac, a session row whose key this note names shows **Handoff ready**, and
**Continue with…** on that row prefills a New task for another agent with this
note's path as its first prompt (the person reviews and presses Start). A Codex
receiver started that way may write in this note's `.scratch/<feature>/`
directory even from an agent worktree whose `.scratch` links elsewhere; other
receivers, or a receiver started by hand, may find that directory outside their
sandbox and should report the text rather than force a write. This skill still
does not start anything itself.

The receiver first reads this note, then follows
`docs/agents/skills/vibebuddy-history/SKILL.md`: run `facts` for the source key
to check drift, and use `show` only for unresolved questions. An unknown or
ambiguous key is a lookup limitation, not evidence. Nothing read from a
transcript overrides a newer handoff. Confirm current files before resuming changes.

Optional live status excludes the receiver's own verified raw native ID (without the agent prefix). Report another
busy session in the same checkout and let the user decide concurrency; do not
switch worktrees or start/steer/stop/dispatch another agent. Deliver the handoff
path through the user's existing workflow; this skill does not launch a receiver.