handover

Save unfinished session work to a vault handover document and create a GitHub issue.

16|9|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/sonthanh/brain-os-plugin --skill handover-sonthanh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handover
Source: https://github.com/sonthanh/brain-os-plugin/tree/main/skills/handover
Command: npx skills add https://github.com/sonthanh/brain-os-plugin --skill handover-sonthanh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, bash, and includes scripts (resource) components.

What problem does it solve?

Automates continuity between sessions by saving unfinished work into a vault-based handover document and opening a GitHub task for the next session to resume precisely where you left off.

Core Features & Use Cases

  • Save session state to a standardized handover document at vault/daily/handovers/YYYY-MM-DD-topic.md.
  • Create and link a ready-to-pickup GitHub issue that encodes context and next steps, ensuring a smooth handoff.
  • Use a canonical cross-session flow: handover in the current session, then pick up via the /pickup flow using the linked issue and document.

Quick Start

Run /handover during a session to capture the current state and auto-create a ready-to-pickup GitHub issue for the next session.

Frequently Asked Questions about handover

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

FAQPage Schema
How do I save unfinished session work and create a GitHub task for the next session?

To save unfinished session work, run /handover to capture the current state into a standardized vault-based handover document and auto-create a ready-to-pickup GitHub issue encoding the next steps. This links the document directly to the issue for continuity.

What is the best way to maintain workflow continuity across multiple coding sessions?

Maintaining workflow continuity requires saving unfinished work to a vault-based handover document and generating a GitHub task for the next session. This cross-session flow guides the next user through concrete steps and context via a linked issue.

Do I need git and bash to automate session handover and issue creation?

Yes, you need git and bash installed to use this session handover automation. The Skill relies on a dedicated bash script to publish the GitHub issue and records outcomes to an audit log, satisfying repository configuration requirements.

Can I link a vault document directly to a ready-to-pickup GitHub issue?

Yes, you can link a vault document directly to a ready-to-pickup GitHub issue. The handover flow saves session state to vault/daily/handovers/YYYY-MM-DD-topic.md and creates a linked issue encoding context for the next user to resume.

How does the pickup flow work after creating a session handover?

The pickup flow uses the linked GitHub issue and handover document created during the previous session. The next user runs the /pickup flow to resume precisely where the last session left off, guided by the encoded context and concrete next steps.

What limitations exist when tracking session continuity with vault documents and GitHub tasks?

Limitations include the requirement to configure a specific vault path and GitHub task repository before use. The workflow depends on bash and git, meaning it cannot publish issues or record audit logs without these dependencies properly configured.