Vibe Handoff

Move active work to another session or agent with enough context to continue, without copying the whole conversation or leaking sensitive data.

Rules

• Write handoff prose in the user's language; keep paths, commands, code, IDs,

status labels, and quotes unchanged.

• Keep required template headings, field labels, tables, and status values

exactly as shown for validator compatibility; localize placeholder prose and all human-readable explanatory content to the user's language or the source artifact's primary language.

• Prefer artifact pointers over copied content.
• Include only context needed for the next agent to act.
• State the objective, current state, decisions, changed files, validation,

blockers, and next recommended skill.

• Mark sensitive or private material. Do not copy secrets, credentials, private

customer data, production records, or local-only tokens into the handoff.

• Be honest about uncertainty and failed validation.
• Use HITL only when human review or permission is required before continuing.

Workflow

1. Identify The Handoff Target

Determine:

• Target agent or session, if known.
• Objective to continue.
• Next workflow step, such as vibe-spec, vibe-review, vibe-plan,

vibe-test, vibe-commit, vibe-prototype, or implementation.

• Whether human review is needed before the next step.

2. Gather Minimal Context

Read current artifacts and local state as needed:

1. Related spec, review, plan, prototype report, test evidence, or commit

readiness report.

1. git status --short and focused diffs when code changed.
2. Commands already run and their outcomes.
3. Open blockers, permissions, credentials, external services, or sandbox

limits.

Do not summarize files the next agent can open directly unless the summary changes what to do next.

3. Write The Handoff

Use [references/handoff-template.md](references/handoff-template.md) for saved handoff artifacts. Prefer features/<slug>/handoff.md or a task-specific handoff path. In OpenSpec mode, use the user-specified change/path or the directory containing a related artifact as the current change directory; ask if neither identifies it. Save handoff.md there, updating an existing file only when explicitly requested. Record the change ID and current artifact path; do not move or archive the change.

Validate saved handoffs with:

python3 skills/vibe-handoff/scripts/validate_handoff.py path/to/handoff.md

4. Finish With A Clear Next Step

The handoff should make the next action obvious:

• what to read first;
• what to do next;
• what not to touch;
• what validation is still required;
• when to ask the user.

Output

When creating a handoff, report:

• Handoff file path.
• Target agent or session.
• Next recommended skill or action.
• Validation result.
• Any blockers or HITL needs.

Skill Signature

Always end the final response with:

Vibe Skill Signature
Skill: vibe-handoff
Status: Completed | Passed | Failed | Blocked | Partial
Next: concise next workflow step