handoff

Creates zero-context cross-domain plans and orchestrates their delegated multi-phase execution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running or multi-domain work often fails when a new agent must continue without the original session's context, or when a complex plan needs coordinated execution without losing decision ownership. This Skill produces plans that stand alone and orchestrates their execution through delegated phases. ## Core Features & Use Cases - Zero-Context Plan Writing: Generates plans with self-contained Goal, Requirements, Boundary, Direction, and Context sections, including baseline SHAs, immutable inputs, and copy-pasteable environment commands. - Orchestrated Execution: Runs multi-phase plans via deterministic scripted execution, delegating reading, commands, tests, and file edits to subagents while retaining decision ownership. - Use Case: You need another agent to implement a cross-service refactor tomorrow. Use this Skill to write a plan capturing the repo root, branch, base/HEAD SHAs, exact commands already run, and per-phase acceptance criteria, so the next agent executes without rediscovering anything. ## Quick Start Use the handoff skill to write a zero-context plan for the multi-service migration so another agent can execute it without this session's context.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I write a plan another agent can execute without context?

Write a zero-context handoff plan with self-contained Goal, Requirements, Boundary, Direction, and Context sections. Include a Baseline with exact paths, branch, base/HEAD SHAs, commands already run, and immutable inputs so no step depends on unstated knowledge.

How do I orchestrate a multi-phase plan with subagents?

Act as orchestrator and decision maker: route each phase to the right subagent with complete context, delegate reading, commands, tests, and file edits, then check each phase's results against the plan's success criteria before starting the next phase.

What is the difference between handoff and handover?

Handoff creates or executes a portable cross-domain plan for another agent, while essential:handover persists the current coding session in continuation files. Use handover to pause a session and handoff to transfer plan ownership.

When should I not use a handoff plan?

Do not use it to persist a coding session for later continuation, or to do planned work inline when a step takes only a handful of tool calls. Execution is delegated; inline work is the narrow exception.

What evidence must a persisted handoff plan include?

It must record the repository root, active branch, base and HEAD commit SHAs, worktree status, tool versions, exact commands already run with outcomes, capability IDs of evidence-producing actors, and absolute paths to every source artifact.