handover

Capture end-of-session context into a dated notes/inbox.md handover.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/derrybirkett/shulkerbox --skill handover-derrybirkett
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handover
Source: https://github.com/derrybirkett/shulkerbox/tree/main/skills/core/handover
Command: npx skills add https://github.com/derrybirkett/shulkerbox --skill handover-derrybirkett

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The handover skill prevents the next session from wasting time re-explaining what happened by capturing the current state, next steps, blockers, and pending decisions in a structured inbox entry.

Core Features & Use Cases

  • Priority-scored work inventory: Organizes items into 🔴 URGENT, 🟡 IN PROGRESS, 🟢 READY, 🔵 WAITING, and ❓ DECISIONS with explicit priority/effort/clarity signals.
  • Inbox-ready handover output: Writes a dated section to notes/inbox.md that includes summaries, context, and file paths so another person (or the model) can resume efficiently.
  • Pickup guidance hooks: Produces a mental pickup script that identifies what to surface first and what context/agent persona to load for continuation.

Use case: You finish a feature implementation that is 80% complete, hit a testing gap, and are waiting on a review decision; the next session starts immediately with the correct next action and the right context.

Quick Start

Use the handover skill by telling your AI to run the end-of-session handover and update notes/inbox.md so the next session can resume without repeating background.

Frequently Asked Questions about handover

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

FAQPage Schema
How do I capture end-of-session context for seamless pickup in the next conversation?

To capture end-of-session context, use a handover process that surfaces blockers, pending decisions, and next steps, then writes a structured notes inbox entry so work resumes seamlessly without re-explaining background.

What is the best way to organize a task inventory by urgency and waiting state?

Organizing a task inventory by urgency and waiting state involves categorizing items into URGENT, IN PROGRESS, READY, WAITING, and DECISIONS, tagging actions with priority, effort, and clarity signals for structured pickup.

How do I prepare a structured handover when wrapping up partially completed projects?

Preparing a structured handover for partially completed projects requires capturing the current state, surfacing testing gaps or blockers, and producing a dated notes/inbox.md file with context, file paths, and a mental pickup script.

Can I route next-session actions and decisions using priority and effort signals?

Yes, you can route next-session actions by tagging items with priority, effort, and clarity signals, which organizes the work inventory and identifies what context or agent persona to load for continuation.

Does the handover approach work for tracking blockers and pending review decisions?

Yes, the handover approach works for tracking blockers and pending review decisions by explicitly surfacing them in a dedicated DECISIONS or WAITING category within the notes inbox output for immediate next-session visibility.

What are the limitations of using a notes inbox file for session-end handover?

A limitation of using a notes inbox file for session-end handover is that it requires manual initiation to capture context, meaning if you forget to run the wrap-up process, the next session still lacks the structured task inventory and pickup guidance.