document-handoff

Generate a self-contained project handoff package with workfolder, session evidence, and HTML memo.

18|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/dachent/skills --skill document-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document-handoff
Source: https://github.com/dachent/skills/tree/main/document-handoff
Command: npx skills add https://github.com/dachent/skills --skill document-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill solves the problem of project continuity and knowledge loss by creating a self-contained, structured archive of a project's state, history, and evidence, allowing any agent to resume work immediately.

Core Features & Use Cases

  • Comprehensive Archiving: Captures project files, session transcripts, and technical context into a single, browsable package.
  • Agent Cold-Start: Generates a dark-mode HTML memo and citation index that enables new agents to understand the project history without re-reading raw logs.
  • Use Case: Use this skill when handing off a complex development project to a new team member or agent to ensure they have full visibility into technical decisions, open questions, and previous session evidence.

Quick Start

Use the document-handoff skill to create a project archive package for the current directory.

Frequently Asked Questions about document-handoff

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

FAQPage Schema
How does project handoff archiving work for Claude Code and Codex agent sessions?

Project handoff archiving works by running a multi-phase pipeline that discovers project files, extracts session transcripts, and synthesizes a structured HTML memo with a citation index, enabling any new agent to resume work immediately.

How do I create a self-contained project archive for agent cold-start continuation?

You create a self-contained project archive by executing the handoff skill in your current directory, which automatically curates a workfolder, captures multi-harness session evidence, and generates a browsable package for cold-start continuation.

What is included in an automated project handoff package?

An automated project handoff package includes a curated workfolder of project files, multi-harness session transcripts, a structured dark-mode HTML memo, and a technical citation index for full visibility into previous decisions.

Does the project handoff skill require Node.js to generate session archives?

Yes, the project handoff skill requires Node.js installed in your environment to execute its discovery, session extraction, and synthesis pipeline for generating comprehensive project archives.

What's the best way to archive project state and technical context for a new team member?

The best way to archive project state is to use a structured handoff package that captures technical context, open questions, and session evidence into a single browsable format, preventing knowledge loss during team transitions.

When should I avoid using automated project handoff packages?

You should avoid using automated project handoff packages for trivial or single-session tasks where the overhead of generating a curated workfolder and HTML memo outweighs the benefit of structured archiving and session extraction.