handoff

Capture session decisions, lessons, and open threads into MCP memories and a narrative log.

47|6|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/7xuanlu/wenlan --skill handoff-7xuanlu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/7xuanlu/wenlan/tree/main/plugin/skills/handoff
Command: npx skills add https://github.com/7xuanlu/wenlan --skill handoff-7xuanlu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-of-session debriefs that capture decisions, lessons, gotchas, and open threads. Writes a narrative session log to ~/.wenlan/sessions/ and stores granular memories via Wenlan MCP. Previews any unconfirmed captures from the current session before closing. Invoked as /handoff.

Core Features & Use Cases

  • End-of-session debrief. Three artifacts per pass: granular MCP captures, a narrative session log at ~/.wenlan/sessions/<YYYY-MM-DD-HHmm>-<slug>.md, and a project status md + json at ~/.wenlan/sessions/_status/.
  • Detect project context and last handoff time to anchor the session.
  • MCP-based capture pipeline with memory types (decision, lesson, gotcha, etc.) and an auto-generated session log.

Quick Start

Run the handoff command to finalize the session context and store artifacts.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I capture end-of-session decisions and open threads for my project?

It aggregates granular MCP captures, a narrative session log, and a per-project status update. This ensures all session decisions, lessons, and open threads are preserved as structured context for the next session.

What is the best way to log session context and project status updates?

The best way to log session context is by generating a narrative session log alongside a per-project status update. It aggregates decisions and lessons into structured MCP memories for future retrieval.

How does MCP memory storage work for journaling session decisions?

MCP memory storage captures session decisions by categorizing them into memory types like decision, lesson, and gotcha. These structured memories are then committed to the local Wenlan store for retrieval.

Can I use this handoff debrief to track lessons and gotchas across sessions?

Yes, you can use this handoff debrief to track lessons and gotchas across sessions. It detects project context and last handoff time to anchor the current session and surface previous context.

Do I need the Wenlan store to commit local session logs and memories?

You need the Wenlan store to commit local session logs and memories when available. The Skill writes outputs to the local sessions directory and updates per-project status files regardless of store availability.