session-handoff

Capture session knowledge, dispatch artifacts to a 7-bucket taxonomy, and emit GitHub issues.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/wan-huiyan/context-baton --skill session-handoff-wan-huiyan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-handoff
Source: https://github.com/wan-huiyan/context-baton/tree/main/plugins/session-handoff
Command: npx skills add https://github.com/wan-huiyan/context-baton --skill session-handoff-wan-huiyan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, python, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the end-of-session knowledge capture and handoff process, ensuring that no context is lost and maintaining a single source of truth across a 7-bucket documentation taxonomy.

Core Features & Use Cases

  • Comprehensive Session Capture: Captures and organizes session knowledge, decisions, and artifacts.
  • 7-Bucket Documentation Dispatch: Distributes output to the appropriate bucket in a canonical documentation taxonomy.
  • Reverse Lint and Skill Freshness Audit: Checks for stale normative guidance and verifies skill freshness.
  • GitHub Issue Emission: Emits follow-up items as GitHub issues for actionable follow-ups.
  • Use Case: Ideal for wrapping up complex work sessions, consolidating parallel sessions, and ensuring that no knowledge is lost.

Quick Start

Use the session-handoff skill to wrap up the current session and generate the handoff document.

Frequently Asked Questions about session-handoff

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

FAQPage Schema
How do I automate session handoff and capture knowledge at the end of a work session?

To automate session handoff, use this Skill to capture session knowledge and dispatch artifacts to a 7-bucket documentation taxonomy. It organizes decisions and outputs, ensuring no context is lost during the wrap-up process.

What is the best way to track follow-up tasks from a complex work session in GitHub issues?

Tracking follow-up tasks via GitHub issues is handled by emitting actionable items directly from the captured session context. This Skill identifies open loops and generates GitHub issues for continuous workflow management.

Do I need Python and GitHub CLI to organize documentation into a taxonomy?

Yes, you need Python and the GitHub CLI (gh) installed to organize documentation into a taxonomy. The Skill relies on these dependencies along with git to execute scripts and perform reverse lints.

How does a 7-bucket documentation taxonomy work for consolidating parallel sessions?

A 7-bucket documentation taxonomy works by categorizing captured session artifacts into seven distinct buckets, providing a single source of truth. This structure is ideal for consolidating parallel sessions and maintaining organized knowledge.

Can I check for stale normative guidance and verify skill freshness during context capture?

Yes, you can check for stale normative guidance and verify skill freshness during context capture. The Skill performs reverse lints to audit existing documentation and ensure all guidance remains current.

When should I not use automated session wrap-up tools for knowledge management?

You should not use automated session wrap-up tools if your workflow lacks git or GitHub CLI integration. The Skill depends on these tools for artifact dispatch and issue emission, making it unsuitable for non-git environments.