handover

Persists work stream state and updates the global overview so sessions can pause and resume.

4|1|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/alvis/.agents --skill handover-alvis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handover
Source: https://github.com/alvis/.agents/tree/main/plugins/essential/skills/handover
Command: npx skills add https://github.com/alvis/.agents --skill handover-alvis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running AI coding sessions lose context when they end. This Skill writes the current state of every work stream to disk in a centralized .state/ directory, so a later session can resume exactly where the work paused without relying on chat history. ## Core Features & Use Cases - State persistence: Rewrites each selected stream's state.md with tasks, decisions, blockers, evidence, and a ## Continuation section naming the next owner, next action, and source anchor. - Global overview upsert: Updates .state/overview.md with one row per stream, preserving all other rows byte-for-byte. - Decision consultation: Routes unresolved material decisions to the user with research or deferral options before pausing. - Use Case: Before ending a coding session mid-feature, run the handover to record task progress, uncommitted changes, and the exact next step; a later session uses the companion takeover skill to resume from those files. ## Quick Start Pause my current work by running the handover skill so all work stream state is saved to disk for a later session to resume.

Frequently Asked Questions about handover

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

FAQPage Schema
How do I pause an AI coding session and resume it later?

Run the handover skill before ending the session. It rewrites each work stream's state.md with a Continuation section naming the next task, owner, and action, then updates the global overview. A later session resumes from those on-disk files using the takeover skill.

How do I save work progress across multiple git worktrees?

Handover writes all state to the default source tree's centralized .state/ directory, so every worktree and workspace shares one view. Each stream records its checkout location, letting a resume switch working directories when needed.

Does handover commit or push my changes to git?

No. Handover only writes state files under .state/works/ and the global overview.md. It explicitly does not perform git history, push, PR, build, test, or deployment work, and it never assumes .state/ is committed.

What happens to uncommitted changes when pausing work?

Handover records exactly what is uncommitted, including staged and unstaged changes, untracked files, and the current revision. The stream remains fully resumable even when relevant changes exist only in the working copy.

When should I not use the handover skill?

Do not use it to execute implementation, reviews, or promotion of artifacts to docs/; it only records continuity for a pause. Also, only the main agent may run it because it writes working state and reconciles the global overview.