handoff

Append structured progress logs to plan docs and push git commits before context clearing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents losing valuable in-session work when you need to run /clear or compact by capturing a durable checkpoint that can be resumed later.

Core Features & Use Cases

  • Durable progress checkpoint: Appends a structured progress log entry to an existing plan doc so the next session has continuity.
  • Commit + push for persistence: Commits only the updated plan document and pushes it (when available) to make the state survive window resets.
  • Resume-block output for next session: Prints a resume block specifically designed to be consumed by /primer, enabling fast, low-friction continuation.
  • Context-preserving workflow: Detects the correct plan doc or asks the user when ambiguous, and avoids running destructive actions like /clear itself.

Quick Start

Run: /handoff docs/my-feature-plan.md right before you clear your context to save progress for /primer to resume.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I save agent session context before clearing the conversation window?

To save agent session context before clearing, append a structured progress log entry to a target plan doc and commit it to a git repo, creating a durable checkpoint that preserves ongoing work. The process also emits a resume block for the next session.

What is a context checkpoint in long agentic workflows?

A context checkpoint in long agentic workflows is a durable record of in-session progress appended to a plan doc. It allows work to be resumed across windows, machines, or days after context is lost or cleared.

Do I need a git repository to save progress before context compaction?

You do not strictly need a git repository to save progress before context compaction, but having one allows the updated plan document to be committed and pushed. This makes the state survive window resets and machine changes.

How do I resume a task across different machines after clearing context?

To resume a task across different machines after clearing context, use the /primer-compatible resume block emitted by the checkpoint process. This block is designed for fast, low-friction continuation of your ongoing work.

Does the handoff Skill run /clear automatically after saving the plan doc?

The handoff Skill does not run /clear automatically after saving the plan doc. It avoids running destructive actions itself, meaning you must manually clear the context after the checkpoint is successfully created.