ze-handoff

Summarizes selected spec and session state to generate precise edits with verification.

50|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/ze-software/ze --skill ze-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ze-handoff
Source: https://github.com/ze-software/ze/tree/main/.codex/skills/ze-handoff
Command: npx skills add https://github.com/ze-software/ze --skill ze-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines handoffs in the Ze repository by generating a concise continuation document that summarizes the current spec and state, and prescribes exact, non-destructive edits for the next session.

Core Features & Use Cases

  • Summarizes the active specification and progress to ensure continuity across sessions.
  • Outputs up to five precise edits with file locations and exact replacement or insertion instructions.
  • Provides a final verification command to confirm successful handoff after edits.

Quick Start

Read the current selected spec from tmp/session/selected-spec, summarize progress, and output up to five precise edits with exact changes, followed by a verification command.

Frequently Asked Questions about ze-handoff

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

FAQPage Schema
How do I create a session handoff with precise next edits for a coding project?

A session handoff summarizes the active spec and current state, then lists up to five precise file edits with exact replacements, concluding with a verification command to confirm deterministic continuity for the next session.

What is the best way to summarize session state for a fresh development handoff?

Summarizing session state for a fresh handoff involves reading the selected spec, documenting what has been done and what remains, and prescribing exact non-destructive edits to ensure the next session resumes work seamlessly.

How does spec summarization work for continuation documents across sessions?

Spec summarization for continuation documents works by reading the current session state, condensing the selected specification and progress, and outputting targeted file locations and exact edit instructions to guide the next session deterministically.

Can I generate exact file replacements and a verification command for my workflow handoff?

Yes, generating exact file replacements and a verification command for a workflow handoff produces up to five non-destructive edits with specific insertion instructions, followed by a final command to verify successful application.

Do I need a specific repository setup to use deterministic session management for handoffs?

Deterministic session management for handoffs requires reading the selected spec from a designated session path like tmp/session/selected-spec, ensuring the repository environment contains the necessary state files to generate accurate continuation documents.

When should I not use automated handoff generation with exact edits?

Automated handoff generation with exact edits should not be used when your session requires more than five precise file replacements, as the workflow is designed to output a maximum of five targeted edits to maintain non-destructive continuity.