Imported from JoeCP17/LLM-Dot-files (claude/skills/wrap/SKILL.md). Install upstream with npx skills add JoeCP17/LLM-Dot-files --skill wrap. Copyright stays with the author.

Session Wrap-up

Analyze the current session and persist a concise summary to memory so the next conversation can pick up seamlessly.

Steps

1. Analyze the session

Classify everything discussed into:

• Completed work — implementations, fixes, deployments that are done
• In-progress work — started but not finished
• Discovered issues — bugs or problems that surfaced
• Decisions made — architecture/design choices and their rationale
• Next steps — what to do in the follow-up session

2. Write a memory file

Save to ~/.claude/projects/{project-path}/memory/session-{YYYY-MM-DD}-{topic}.md.

Use absolute dates (never "today"/"tomorrow") — relative dates become meaningless once the session ends. Keep it concise; git log covers code details, so focus on context and intent that aren't captured in commits.

---
name: {date} {topic} session summary
description: {one-line: what was done and how far it got}
type: project
---

## Session Summary ({date})

### Completed
- item

### In Progress
- item (current state)

### Decisions
- decision — **Why:** reasoning

### Next Steps
- [ ] follow-up task

3. Update MEMORY.md index

Add a link under ## Sessions. Create the section if it doesn't exist.

4. Update stale memories

If the session changed facts tracked in existing memory files (project status, decisions, etc.), update those files too — stale memories are worse than no memories.

5. Report