handoff

Generate structured handoff documentation with state snapshots and next actions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill solves the loss of context and momentum when transitioning between agent sessions, ensuring that a fresh agent can resume complex work without duplicating effort or reasoning against stale state.

Core Features & Use Cases

  • Canonical Handoff Drafting: Generates a standardized, human-readable narrative document that captures the state of the world, delivered work, and the next immediate action.
  • Queue Integration: Pushes handoff artifacts to the Maestro queue, making them discoverable and trackable for future sessions.
  • Use Case: When ending a multi-day development arc, use this skill to generate a handoff document that allows a new agent to pick up exactly where you left off, including git status, open PRs, and the specific next command to run.

Quick Start

Invoke the handoff skill to generate a fresh-session handoff document for the current project arc.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I maintain context when transitioning between agent sessions?

To maintain context when transitioning between agent sessions, generate structured handoff documentation that captures state snapshots, delivered work, and prioritized next actions for seamless pickup by a fresh agent.

What is session handoff documentation for development workflows?

Session handoff documentation is a standardized, human-readable narrative that records the current state of a project arc, completed work, and the specific next command to run, preventing duplicated effort across new contexts.

How do I resume a complex development arc without losing momentum?

You can resume a complex development arc by invoking a handoff skill to generate a resumable document detailing git status, open PRs, and immediate next actions, ensuring a new agent picks up exactly where the previous session left off.

Does handoff documentation integrate with task queue management?

Yes, handoff documentation integrates with the Maestro queue to push handoff artifacts, making them discoverable and trackable for future agent sessions to ensure seamless pickup and arc status tracking.

What are the limitations of relying on handoff documents for agent continuity?

Handoff documents are limited to the state snapshots and narratives captured at the end of a session, meaning any undocumented mid-session changes or uncommitted code states may not be reflected for the next agent.