handover

Writes an end-of-session handover document covering completed work, decisions, and open TODOs.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/manusco/wolfgang --skill handover-manusco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handover
Source: https://github.com/manusco/wolfgang/tree/main/.cursor/skills/handover
Command: npx skills add https://github.com/manusco/wolfgang --skill handover-manusco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a work session ends, context about what was done, why decisions were made, and what remains unfinished is easily lost. This Skill captures that state in a structured handover document so the next session or teammate can resume work without re-discovery. ## Core Features & Use Cases - Session Summary: Records what was accomplished during the current work session. - Decision Log: Documents key decisions made and their rationale for future reference. - Open Items Tracking: Lists outstanding TODOs and backlog items so nothing is forgotten. - Use Case: Before ending a long coding or planning session, run the handover procedure to produce a document the next session (or a teammate) can read to pick up exactly where you left off. ## Quick Start Ask the assistant to run the handover procedure to write an end-of-session handover doc summarizing what was done, decisions made, and open TODOs.

Frequently Asked Questions about handover

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

FAQPage Schema
How do I create a session handover document?▼

Run the handover procedure, which reads the referenced procedure skill and writes a handover doc covering what was done, decisions made, open TODOs, and backlog items. The output follows the procedure's Definition of Done.

What should an end-of-session handover doc include?▼

A handover doc should include a summary of completed work, key decisions and their rationale, open TODOs, and backlog items. This skill structures exactly those sections so the next session can resume without lost context.

Does the handover skill work automatically at session end?▼

No, it must be invoked explicitly via the /handover command. The skill has model invocation disabled, so it only runs when the user triggers it, then routes to the procedure skill for execution.

What are the limitations of this handover skill?▼

This skill is only a router: it delegates all actual work to a separate procedure skill located at .agents/skills/ops/handover/SKILL.md. If that procedure file is missing, the handover cannot be executed.