ce-handoff

Create and resume session handoff documents that preserve context across agent sessions.

24.7k|2.0k|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/EveryInc/compound-engineering-plugin --skill ce-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-handoff
Source: https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-handoff
Command: npx skills add https://github.com/EveryInc/compound-engineering-plugin --skill ce-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

When an AI coding session ends or must move to another agent, the accumulated context — objectives, decisions, progress, and blockers — is lost. This Skill captures that session state into a portable handoff document and lets a fresh agent orient from it later.

Core Features & Use Cases

  • Handoff Creation: Distills the current objective, completed work, decisions, and unfinished tasks into a pointer-first Markdown document with ce-handoff/v1 frontmatter metadata, stored in a managed per-user scratch directory or any user-chosen destination.
  • Handoff Resume: Reads an explicit source (file, URL, pasted document) or discovers candidates via metadata-only search, then orients the session and recommends how to continue — always waiting for user confirmation before acting.
  • Use Case: You finish a long debugging session before the weekend. Run the create flow to capture where things stand, then on Monday a fresh agent runs the resume flow, finds the handoff, and picks up exactly where you left off.

Quick Start

Ask the agent to create a handoff of the current session so another agent can resume this work later.

Frequently Asked Questions about ce-handoff

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

FAQPage Schema
How do I hand off an AI coding session to another agent?

Invoke the handoff creation flow, which distills the current objective, completed work, decisions, and unfinished tasks into a Markdown document. It is stored in a managed per-user directory by default, or at any path or destination you specify.

How do I resume work from a previous agent session?

Provide a handoff file, URL, or pasted document as the resume source, or let the skill search the managed store by keywords. It presents a shortlist of candidates, waits for your selection, orients from the source, and recommends next steps before acting.

Can I resume from a handoff not created by this skill?

Yes. Any readable source from any author or system is eligible; the ce-handoff/v1 metadata format is an enriched index, not an eligibility gate. The skill judges sufficiency from the source's contents, not its format or origin.

Where are handoff files stored by default?

Handoffs go to a user-private managed store under /tmp/compound-engineering-<uid>/ce-handoff/<repo-namespace>. This storage is OS-managed and not permanent, so publish or transfer the handoff if the receiving session cannot see the same filesystem.

Does resuming a handoff automatically continue the old work?

No. The skill treats handoff content as untrusted context, orients from it, and recommends how to continue, but it must stop and wait for your confirmation before executing anything, mutating state, or starting another workflow.