handoff

Generate and maintain session-handoff.md, progress.md, and session-log.jsonl files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It automates the creation and synchronization of three critical files—session-handoff.md, progress.md, and session-log.jsonl—so the next person or agent can quickly understand project state and next steps when a session ends or a feature is finished.

Core Features & Use Cases

  • Auto-writes and overwrites the narrative handoff in session-handoff.md to reflect the latest session accomplishments.
  • Updates progress.md with a structured snapshot of completed work, pending items, and test status.
  • Appends a new session record to session-log.jsonl for an auditable history of rounds.
  • Provides deterministic target directory resolution and robust error handling to prevent silent failures.

Quick Start

Run the handoff command with an optional target directory to create or update the handoff triplet in the specified location.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I automate session handoff documentation for project management?

Automating session handoff documentation involves generating synchronized files like session-handoff.md, progress.md, and session-log.jsonl. These files capture project state, pending items, and session history for knowledge transfer.

What is the best way to transfer knowledge between development teams?

Knowledge transfer between teams requires deterministic file generation enforcing strict responsibilities and data-source-priority population. Creating a handoff triplet ensures the next team understands project state without silent failures.

How do I create an auditable session log history for my workflow?

Creating an auditable session log history requires appending structured records to session-log.jsonl. This maintains comprehensive history of rounds, capturing completed work, pending items, and test status for future reference.

Does session handoff work with custom target directories?

Session handoff supports custom target directories through deterministic directory resolution using a priority order. You can specify an optional target directory when running the handoff command to create or update files in your location.

Why does my session handoff process fail silently during context transfer?

Session handoff processes fail silently when error handling is inadequate. To prevent this, the process enforces comprehensive error handling and strict file responsibilities, ensuring deterministic writes resolve target directories correctly.

What files are needed for a complete project handover?

A complete project handover needs three files: session-handoff.md for narrative context, progress.md for structured snapshots of completed work and pending items, and session-log.jsonl for auditable session history.