debrief

Extract memories from end-of-session conversations and update profile files.

69|7|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/TaylorHuston/local-life-manager --skill debrief
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debrief
Source: https://github.com/TaylorHuston/local-life-manager/tree/main/.claude/skills/debrief
Command: npx skills add https://github.com/TaylorHuston/local-life-manager --skill debrief

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill collects and analyzes end-of-session conversations to extract memories and surface profile updates.

Core Features & Use Cases

  • Memory extraction: Identify memory-worthy moments across preferences, corrections, and personal context to improve future interactions.
  • Profile maintenance: Generate targeted updates to about-taylor.md and CLAUDE.md to reflect new insights.
  • Debrief execution: Save memories to .claude/memories and update index.json for long-term personalization.

Quick Start

Execute the debrief routine at the end of a session to extract memories and propose updates. Then review and approve the suggested memories, and confirm any profile or workflow updates. File operations are performed on .claude/memories, CLAUDE.md, and about-taylor.md as part of the debrief process.

Frequently Asked Questions about debrief

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

FAQPage Schema
How do I extract memories from Claude Code sessions for long-term personalization?

To extract memories from Claude Code sessions, run a debrief routine at the end of your session that analyzes conversations to identify memory-worthy moments, preferences, and corrections. It saves these entries to your .claude/memories directory and updates index.json for long-term personalization.

How do I update CLAUDE.md and profile files based on session insights?

Updating CLAUDE.md and profile files based on session insights is handled by a debrief process that generates targeted suggestions for about-taylor.md and CLAUDE.md. You execute the routine at the end of a session, then review and approve the proposed profile and workflow updates.

What is end-of-session debriefing in knowledge management?

End-of-session debriefing in knowledge management is the process of collecting and analyzing conversation data to extract memories and surface profile updates. It identifies preferences, corrections, and personal context across sessions to improve future AI interactions and maintain continuity.

Can I use journaling to maintain a memory index for Claude interactions?

Yes, you can use journaling to maintain a memory index for Claude interactions. The debrief routine writes extracted memories to the .claude/memories vault and updates index.json, creating a structured journal that preserves context and personalization data for future sessions.

Does the debrief routine require any external dependencies to run file operations?

No, the debrief routine requires no external dependencies to run file operations. It uses native file operation tools including Read, Write, Edit, Glob, and Bash(date:*) to read from and write to memory vaults and existing profile files without needing additional packages.

When should I run a session debrief to extract memories?

You should run a session debrief to extract memories at the end of long Claude Code sessions. Applying the routine after extensive interactions ensures the system captures meaningful preferences, corrections, and context updates while the conversation data is still available for analysis.