/handoff

Make it your own.

In Claude Code, use the slash command and add your context. In Codex, select handoff from the just-vibe skill picker, then send the same brief.

Version 0.11.0 also supports /jv handoff, /just-vibe handoff and /jv:handoff in Claude. See shortcut setup and context examples.

What the agent does

1. Reconstruct the original objective, constraints and accepted decisions.
2. Summarize verified state, separating proposed from completed work, and document blockers.
3. Give actionable continuation steps with the files or artifacts the next step needs.
4. All changes are owned by the user. Add no agent/model self-attribution, AI-generated signature, badge, or agent Co-authored-by trailer to commits, PRs, comments, release notes or messages. Use the existing user Git identity; preserve legitimate human attribution and required third-party notices.

Inputs

• task, intended recipient/session, and optional output path.

Optional context: scope, references, constraints, successCriteria, environment, mode, budget.

Scope

Reads

Produce a self-contained handoff; creating tasks, sending messages, or assigning ownership is separate.

Writes

No source changes in inspect/plan. Save only requested planning artifacts. A separately requested repair uses the relevant implementation workflow.

Mode

Plan; task, intended recipient/session, and optional output path.

Prerequisites

Resolve the user brief and inspect the relevant project or supplied evidence. External capabilities are optional unless the selected action actually needs them.

Expected output

• Self-contained handoff brief with the goal, constraints, file links, commands already run with results, blockers and the continuation sequence; save when requested.

How the work is checked

• A reader needs no hidden conversation history; proposed changes are not described as completed.
• Review newly prepared commit/PR/message text, including template or hook additions, for agent self-attribution before submission; verify the resulting artifact when available. Do not silently rewrite existing history or remove human credits.

When to stop or clarify

• Exclude credentials and unnecessary personal details. Do not transmit the handoff without a sending instruction.

Handling missing context

Infer

Resolve the named files, existing scripts, current task and earlier corrections from the conversation and repository.

Assume

Use the narrowest interpretation that completes a reversible local task; state a consequential assumption once.

Ask

Ask when competing targets or incompatible success conditions would change the result; continue independent inspection first.

Technical guidance

Evidence

Resolve current objective, accepted constraints, completed artifacts, evidence and open decisions.

Method

Write a self-contained brief with exact paths/revisions and the next actionable step, distinguishing facts from proposals.

Pitfall

A conversational narrative without current state forces rediscovery; claiming unavailable checks passed misleads the next session.

Check

Verify links/identities and ensure a reader can continue without relying on hidden conversation context or secret values.

Situational decisions

When external action outcome is uncertain: Include its operation identity and reconciliation step rather than instructing a blind retry.

When saving the handoff is requested: Prefer memory_handoff or vault handoff --stdin (project scope by default; team scope for teammates, reviewed through Git); otherwise use the project established handoff file.

The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.

Keep exploring