wrapup

Session Summary (TL;DR)

Generates a summary of this session and saves it to the logs folder for future recall.

---

Before You Begin

If vault.yml exists, read it and extract:

• folders.logs as logs_folder (default: 07-logs)
• folders.agent as agent_folder (default: 05-agent)

Use these variables for all file paths in the steps below.

---

Step 1: Gather Checkpoint Context

1. Get today's date as YYYY-MM-DD. Extract YYYY and MM.
2. Glob [logs folder]/YYYY/MM/YYYY-MM-DD-checkpoint-*.md (also check yesterday's folder if session started before midnight : i.e., [logs folder]/YYYY/MM_PREV/YYYY-MM-DD_PREV-checkpoint-*.md for the prior calendar day)
3. Filter: keep only files where frontmatter field merged is absent or not true
4. If any found: read every file in the filtered list and extract its content. Every checkpoint must be fully incorporated during the review in Step 3 and reflected in the log written in Step 4 : not just used as background context. Checkpoints capture activity that may have been compressed out of current context; missing any of them means losing that history.
5. Store the list of found checkpoint paths for use in Step 5. Only paths that were read and incorporated go on this list.

If none found: continue normally.

---

Step 2: Determine Session File Name

1. Using the date from Step 1, extract YYYY and MM (zero-padded month).
2. List files in [logs folder]/YYYY/MM/ matching YYYY-MM-DD-session-*.md
3. The next session number = count of matches + 1 (zero-padded to 2 digits: 01, 02, etc.)
4. File name: [logs folder]/YYYY/MM/YYYY-MM-DD-session-NN.md

---

Step 3: Review the Session

Reflect on the conversation that just occurred. Identify:

• Main topic(s) : What did we work on?
• Key decisions made : Any choices, directions, or conclusions reached
• Insights or learnings : New understanding, patterns noticed, things discovered
• What worked / didn't work : Approaches or tools that helped, and anything that slowed us down or failed (omit if nothing notable)
• Action items : Tasks to do, things to follow up on
• Open questions : Unresolved questions or things to investigate

---

Step 4: Write the Session Log

If checkpoints were found in Step 1: do not write the session log until the content of every checkpoint file read in Step 1 is reflected in the sections below. All Key Decisions, Action Items, and Open Questions from checkpoints must appear explicitly : not summarized into a single line.

Create [logs folder]/YYYY/MM/YYYY-MM-DD-session-NN.md:

---
tags: [session-log]
date: YYYY-MM-DD
session: NN
---

# Session Summary : [Month DD, YYYY] (Session N)

## What We Worked On

[1-3 sentences describing the session's focus]

## Key Decisions

- [Decision 1]
- [Decision 2]

## Insights & Learnings

- [Insight 1]
- [Insight 2]

## What Worked / Didn't Work

- ✅ [Something that worked well]
- ❌ [Something that didn't work or slowed things down]

_Omit this section if the session had no notable friction or technique worth logging._

## Action Items

- [ ] [Action item 1] 📅 YYYY-MM-DD
- [ ] [Action item 2] 📅 YYYY-MM-DD

## Open Questions

- [Question or uncertainty to revisit]

## Related Notes

[[Link to relevant vault notes if applicable]]

---

Step 5: Mark Checkpoints as Merged

If the Step 1 checkpoint list is non-empty (i.e., at least one file was read and incorporated):

For each checkpoint file path stored in Step 1:

1. Read the file's frontmatter
2. Set merged: true : handle all variants:
   • merged: false → replace with merged: true
   • merged: null or bare merged: → replace with merged: true
   • key absent → add merged: true to frontmatter
3. Write the updated file

This prevents /wrapup from re-reading the same checkpoints in future sessions.

---

Step 6: Update MEMORY.md (If Warranted)

If this session produced an insight or pattern that should persist across all future sessions, add it to the "Key Learnings & Patterns" section of [agent folder]/MEMORY.md. Also update the updated: field in the frontmatter to today's date.

## Key Learnings & Patterns

- YYYY-MM-DD : [observation about the user's work patterns, preferences, or recurring themes]

Only add learnings that are genuinely useful long-term (not every session warrants this).

---

Step 7: Overflow to Agent Memory (Optional)

If a genuinely useful long-term insight emerged this session : a clear behavioral pattern, a strong user preference, or a non-obvious observation about how to work with this user : and it is too detailed for MEMORY.md, write it to [agent folder]/memory/YYYY-MM-DD-slug.md:

• Frontmatter: tags: [agent-memory], created: YYYY-MM-DD, source: /wrapup
• File naming: first note of day: YYYY-MM-DD-slug.md; if one already exists today: YYYY-MM-DD-02-slug.md, etc.
• Keep it to 1-3 sentences
• Only do this if the insight is genuinely useful long-term : do not overflow routine session details
• Use this step only when the insight was too detailed to include in [agent folder]/MEMORY.md (Step 6). Do not write the same insight to both [agent folder]/MEMORY.md and agent memory.

---

Step 8: Confirm

Say:

Session saved to [logs folder]/YYYY/MM/YYYY-MM-DD-session-NN.md.

[If action items]: I logged N action items : they'll appear in your Tasks view. [If MEMORY.md updated]: I also added a learning to [agent folder]/MEMORY.md.

Good session! See you next time.