wrap

Save session wrap-up summaries to project memory as dated markdown files.

8|1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/JoeCP17/LLM-Dot-files --skill wrap-joecp17
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrap
Source: https://github.com/JoeCP17/LLM-Dot-files/tree/main/claude/skills/wrap
Command: npx skills add https://github.com/JoeCP17/LLM-Dot-files --skill wrap-joecp17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents losing valuable session context by turning a conversation wrap-up into a persistent memory you can reuse later.

Core Features & Use Cases

  • Session analysis and categorization: Captures completed work, in-progress items, discovered issues, decisions, and next steps.
  • Project-scoped memory persistence: Writes a dated session summary to a consistent file path inside your Claude projects memory.
  • Memory index and staleness maintenance: Updates MEMORY.md with the new session link and refreshes outdated memory files when facts change.

Quick Start

Use wrap when the conversation is ending or you say /wrap so the assistant records what you did and what to do next.

Frequently Asked Questions about wrap

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

FAQPage Schema
How do I save chat session progress and context before ending a conversation?

To save session progress, you can trigger a wrap-up to generate a structured markdown summary of completed work, in-progress items, decisions, and next steps. This summary is written to your project memory path for later reuse.

What is the best way to retain project context and prevent knowledge loss between chat sessions?

The best way to retain project context is creating a dated session markdown file that captures decisions and discovered issues. This file updates your project memory index to ensure the context persists across future assistant interactions.

How do I record completed work and next steps when wrapping up a project session?

Recording completed work and next steps involves analyzing the conversation to categorize outcomes. The process extracts finished tasks, pending items, and discovered issues, then saves them as a structured wrap-up summary to memory.

Does saving a session wrap-up automatically update the project memory index?

Yes, saving a session wrap-up automatically updates the MEMORY.md file with a link to the new session summary. It also refreshes any stale related memory files to maintain accurate project context.

Can I use session memory to track planning progress and discovered issues for ongoing projects?

Yes, you can use session memory to track planning progress by saving structured wrap-up summaries. These summaries capture discovered issues and in-progress items, writing them to a consistent project memory path for ongoing tracking.

What are the limitations of relying on session wrap-up summaries for knowledge retention?

A limitation of session wrap-up summaries is that knowledge retention depends on actively triggering the wrap-up before the conversation ends. If the session is closed without saving, the unsaved context and progress will be lost.