vv-handoff

Generates structured XML session handoff notes with automatic sensitive value redaction.

11|1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/osovv/vv-opencode --skill vv-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vv-handoff
Source: https://github.com/osovv/vv-opencode/tree/main/templates/skills/vv-handoff
Command: npx skills add https://github.com/osovv/vv-opencode --skill vv-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of losing critical session context when ending a work session, ensuring future agents or human collaborators can pick up work without redoing completed tasks or missing key decisions.

Core Features & Use Cases

  • Context-Only Capture: Only uses information already visible in the current session, with no access to hidden, compacted, or prior conversation history.
  • Automatic Sensitive Data Redaction: Replaces all tokens, API keys, passwords, and other sensitive values with [REDACTED] before writing the handoff note.
  • Standardized Artifact Placement: Writes the handoff note to a consistent, project-local .vvoc/handoff/ directory with collision-safe naming for existing folders.
  • Use Case: After finishing a session where you implemented a new user authentication flow, use this Skill to generate a handoff note that captures the original request, completed work, pending next steps, and redacted credentials for the next developer or agent working on the feature.

Quick Start

Use the vv-handoff skill to generate a structured handoff note for the current session's work.

Frequently Asked Questions about vv-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I preserve session context for agentic development handoffs?

You preserve session context for agentic development handoffs by capturing visible session information as structured XML handoff notes, ensuring future agents or developers can resume work without losing critical decisions or completed tasks.

What is the best way to redact sensitive data in project handoff notes?

Redacting sensitive data in project handoff notes is handled automatically by replacing all tokens, API keys, and passwords with [REDACTED] before the handoff note is written, ensuring no credentials are exposed in the preserved context.

How do I generate structured XML handoff notes for code review sessions?

Generating structured XML handoff notes for code review sessions involves applying an end-of-session workflow that extracts only visible in-session context, standardizing artifact placement in a project-local directory for future reference.

Does the handoff note workflow reconstruct hidden conversation history?

The handoff note workflow does not reconstruct hidden conversation history, as it strictly prohibits accessing hidden, compacted, or prior conversation logs and only retains information already visible in the current session.

Where are standardized handoff artifacts placed for project continuity?

Standardized handoff artifacts for project continuity are placed in a consistent, project-local .vvoc/handoff/ directory with collision-safe naming to prevent overwriting existing folders during end-of-session workflows.

Can I use session context capture for fresh context collection during work?

Session context capture is designed strictly for end-of-session workflows and prohibits fresh context collection, relying solely on the visible information present in the current session to generate the handoff note.