handoff

Generate a continue.md and update STATE.md and summary artifacts for cross-session handoffs.

Updated May 25, 2026
One-click install
npx skills add https://github.com/cmetech/otto-cli --skill handoff-cmetech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/cmetech/otto-cli/tree/main/src/resources/skills/handoff
Command: npx skills add https://github.com/cmetech/otto-cli --skill handoff-cmetech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prepare a clean cross-session handoff so the next agent (or you tomorrow) can pick up exactly where you left off. Writes a focused continue.md in the active slice directory and ensures STATE.md and summary artifacts are current. Use when asked to "hand off", "prepare handoff", "pause work", "bookmark this", "I'll come back to this later", before running out of context budget, or at the end of a long session with unfinished work. Closes the v1 /otto-pause-work parity gap.

Core Features & Use Cases

  • Creates a concise continue.md that captures the current state and next actionable steps for the next agent.
  • Keeps STATE.md and summary artifacts in sync to maintain an accurate trail across sessions.
  • Supports common handoff scenarios such as pauses, bookmarking, and end-of-session handoffs to reduce context reset time.

Quick Start

Run a handoff to create a clean continue.md and refresh STATE.md and summaries for the next agent.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I prepare a cross-session handoff for an AI agent?

A cross-session handoff captures current progress and next steps in a continue.md file while updating STATE.md and summaries. This ensures the next agent resumes work instantly without losing context.

What is the best way to bookmark work and pause an AI automation workflow?

To bookmark and pause an automation workflow, generate a focused continue.md in the active slice directory and sync milestone artifacts. This preserves the exact working state for a future session.

Do I need existing STATE.md files to run a handoff?

Yes, cross-session handoffs require an existing STATE.md, continue.md patterns, and an active slice directory. The tool updates these artifacts rather than creating them from scratch.

How does state management work when ending a long coding session?

State management at session end writes next actionable steps to continue.md and refreshes decision logs in the milestones directory. This creates an accurate trail for future you or the next agent.

Can I use handoff to prevent context budget exhaustion?

Yes, running a handoff before hitting context limits saves current state and summaries. It creates a clean breakpoint so a new agent can pick up exactly where the previous session stopped.