handoff-update

Write a compact handoff-<topic>.md file with archive and checkpoint references.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/zjh08177/agent-harness --skill handoff-update-zjh08177
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff-update
Source: https://github.com/zjh08177/agent-harness/tree/main/skills/handoff-update
Command: npx skills add https://github.com/zjh08177/agent-harness --skill handoff-update-zjh08177

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically maintains a compact handoff file for active vault projects by writing a minimal handoff-<topic>.md.

Core Features & Use Cases

  • Overwrite-only handoff-<topic>.md to keep a concise pointer across sessions.
  • Auto-populates from session context, including latest archive and checkpoint references.
  • Uses a predefined template to ensure frontmatter and structured sections for continuity.
  • Respects the 100-line hard cap to keep the file tiny and review-friendly.
  • Supports cross-session continuity for rapid session resumes.

Quick Start

Run the handoff-update command within the vault project to generate or refresh handoff-<topic>.md.

Frequently Asked Questions about handoff-update

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

FAQPage Schema
How do I maintain concise vault handoff documentation across sessions?

To maintain concise vault handoff documentation across sessions, automatically generate a minimal handoff-<topic>.md file that overwrites previous content, ensuring continuity while preventing file growth beyond a 100-line limit.

What is the best way to sync project context when resuming a vault session?

Syncing project context when resuming a vault session is done by writing an overwrite-only handoff file auto-populated with the latest archive pointers and checkpoint references from the active project context.

How do I keep session handoff files under 100 lines automatically?

Keeping session handoff files under 100 lines is achieved through an overwrite-only operation that replaces the existing handoff-<topic>.md instead of appending, strictly respecting a predefined hard cap.

Does handoff-update work without external dependencies?

Yes, handoff-update works without external dependencies, operating entirely within the vault project to read active context and write structured frontmatter sections into the handoff markdown file.

Why use an overwrite-only file for cross-session workflow continuity?

Using an overwrite-only file for cross-session workflow continuity prevents unbounded log growth, keeping the handoff documentation compact, review-friendly, and consistently in-sync with current checkpoint references.