handoff

Create temporary handoff documents and propose permanent knowledge updates in a shared Obsidian vault.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/TylerSimons1127/vibe --skill handoff-tylersimons1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/TylerSimons1127/vibe/tree/main/skills/handoff
Command: npx skills add https://github.com/TylerSimons1127/vibe --skill handoff-tylersimons1127

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working across sessions or with multiple agents, project context gets lost. This Skill captures session progress as temporary handoff documents and manages long-term knowledge updates in a shared Obsidian vault, so work can resume without re-explaining everything. ## Core Features & Use Cases - Temporary Handoff Docs: Generate structured handoff files with session goals, work done, current status, and next steps, organized by project and date. - Handoff Loading: Search and summarize existing handoffs for a project via the load subcommand, with optional date filtering and INDEX.md support. - Permanent Knowledge Updates: Propose section-level patches to long-term docs (architecture, debugging workflows) with confirmation-gated application via --permanent and --apply. - Use Case: After a long debugging session, run /handoff myproject --log to produce a discardable handoff doc plus a detailed work log, then propose updates to the permanent architecture notes for review. ## Quick Start Ask the agent to create a handoff for your project, for example by saying: create a handoff document for the payments project summarizing today's session.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I create a project handoff document?▼

Invoke /handoff <project> with optional flags like --new, --update, or --log. The agent searches for an existing handoff for that project, asks whether to update or create one, and confirms the resolved file path before writing.

How do I load an existing handoff note?▼

Use /handoff load <project> with an optional --date YYYY-MM-DD filter. The agent searches the project's handoff folder, prefers INDEX.md if present, and returns matching paths with a short bullet summary of each file.

Where are handoff files stored in the Obsidian vault?▼

Temporary handoffs live under $HOME/.openclaw/shared/handoff/<project>/<YYYY-MM-DD>/, while permanent knowledge docs live under $HOME/.openclaw/shared/knowledge/<project>/. Each project keeps an INDEX.md pointing to recent handoffs.

Does the handoff skill write files without confirmation?▼

No. Before any write or edit, the agent must state the resolved absolute paths and ask for confirmation. Permanent doc updates additionally require a proposed patch review plus the explicit --apply flag.

What subcommands does the handoff command support?▼

Only two forms are supported in v1: the default /handoff <project> [options] and /handoff load <project> [--date]. Any other token treated as a subcommand is rejected with an explanation of the supported forms.

What is the difference between a handoff doc and a work log?▼

A handoff doc is a temporary, discardable summary with goal, work done, status, and next steps. A work log, generated only with --log, records commands, outputs, files changed, and decisions without duplicating the handoff overview.