handoff

Writes a YAML-frontmatter handoff file to /tmp/<descriptive-slug>-handoff.md for cross-session task resumption.

4|1|Updated Mar 11, 2026

Search Tags:#session continuity #agent handoff #workflow state #git operations #change safety #marker tracking

Ready to run

npx skills add https://github.com/jcdendrite/claude-config --skill handoff-jcdendrite

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/jcdendrite/claude-config/tree/main/claude/.claude/skills/handoff
Command: npx skills add https://github.com/jcdendrite/claude-config --skill handoff-jcdendrite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents losing critical continuity when an agent session ends and a new agent must resume the same work safely and consistently.

Core Features & Use Cases

Writes a cross-session handoff artifact to a deterministic location so the next session can reconstruct intent and progress without guessing.
Captures operational state including goal, status, files modified, active gates/markers, and deferred questions to reduce errors and duplicated effort.
Builds an explicit safety boundary by separating reversible next steps from irreversible/shared-state actions requiring engineer confirmation.

Quick Start

Ask your agent to use the handoff skill to write a handoff file to /tmp/<descriptive-slug>-handoff.md for your current work.

Frequently Asked Questions about handoff

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

FAQPage Schema

How do I preserve agent session context when pausing a multi-step Claude Code workflow?▼

Cross-session agent continuity is maintained by emitting a YAML-frontmatter-defined handoff artifact to a deterministic file location. This template includes mandatory sections for goal, status, next step, pending authorizations, files modified, active gates, open questions, and a precise resume command.

What is the best way to track modified files and workflow state for agent handoff?▼

Tracking modified files and workflow state requires generating a handoff artifact with dedicated sections for files modified and active gates. This builds an explicit safety boundary by separating reversible next steps from irreversible shared-state actions requiring engineer confirmation.

How do I resume a paused Claude Code task safely across a new agent session?▼

Safe task resumption relies on reading the handoff artifact's precise resume command and status section. The next agent reconstructs intent and progress from the deterministic file, ensuring execution continues safely without missing deferred questions or active gates.

Can I separate reversible next steps from irreversible git operations during agent handoff?▼

The handoff artifact separates reversible next steps from irreversible shared-state actions in its pending authorization section. This explicit safety boundary ensures engineer confirmation is captured for dangerous git operations before the next session resumes.

Do I need any external dependencies to write a cross-session handoff artifact?▼

No external dependencies are required to write a cross-session handoff artifact. The skill operates independently to emit a YAML-frontmatter-defined markdown template to /tmp/<descriptive-slug>-handoff.md, capturing all necessary operational state for agent continuity.