debrief

Automate end-of-session debrief by saving logs, project status, and MCP context.

47|6|Updated Apr 19, 2026

Search Tags:#workflow #handoff #ai-assistant #project-status #debrief #session-log #mcp-captures

Ready to run

npx skills add https://github.com/7xuanlu/wenlan --skill debrief-7xuanlu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debrief
Source: https://github.com/7xuanlu/wenlan/tree/main/plugin/skills/debrief
Command: npx skills add https://github.com/7xuanlu/wenlan --skill debrief-7xuanlu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-of-session handoffs can be inconsistent; this skill provides a symmetric, reliable debrief routine that writes a narrative session log, a current project status, and granular MCP captures.

Core Features & Use Cases

End-of-session log: saves the narrative session log to ~/.wenlan/sessions/ for future reference.
Project status update: records current progress to keep stakeholders aligned across conversations.
MCP captures: preserves granular MCP data to support recap and decision traceability.

Quick Start

Use /debrief at the end of a session to automatically save logs, update the project status, and capture MCP context.

Frequently Asked Questions about debrief

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

FAQPage Schema

How do I automate end-of-session handoffs with consistent logs and project status?▼

The debrief mechanism writes a narrative session log to the ~/.wenlan/sessions directory, updates current project status for stakeholders, and preserves granular MCP data to support recap and decision traceability across team or client sessions.

How do I capture MCP context for decision traceability during a project handoff?▼

Running an end-of-session debrief captures granular MCP data and writes it alongside a narrative session log and project status update, ensuring decision traceability and synchronized artifacts for your team handoff.

Do I need the /handoff flow to save session logs to ~/.wenlan/sessions?▼

Yes, the debrief routine requires integration with the /handoff flow to properly save session artifacts to ~/.wenlan/sessions and synchronize MCP captures with project status updates.

What is the best way to keep project status aligned across multiple client sessions?▼

Executing an end-of-session debrief is the best way to keep project status aligned, as it automatically records current progress, saves traceable session artifacts, and updates MCP context for consistent team or client handoffs.

When should I run a session debrief instead of manually updating project status?▼

You should run a session debrief during team or client sessions requiring a consistent handoff with traceable artifacts, as it standardizes the update process and synchronizes MCP captures automatically.