session-management

name	session-management
description	Use at the start or end of a working session, or when distilling learned facts into the memory vault. Defines the startup orientation protocol, end-of-session handoff note format, and knowledge pruning rules.

Session Management Skill

Session Start Protocol

1. Read memory/CLAUDE.md for orientation
2. Check memory/sessions/ for the most recent session handoff
3. Read the Next Action from the last session to understand where to pick up
4. Check memory/knowledge/_index.md for recently learned facts

Session End Protocol

1. Create a new session note from memory/sessions/_template.md
2. Name it YYYY-MM-DD-HHMM-<slug>.md — e.g. 2026-04-30-0916-skills-scaffolding.md
   • HHMM = session start time, 24h, no separator (lexicographic = chronological)
   • <slug> = short kebab-case topic (1–4 words) for scannability
   • No collision suffix needed; minute-precision is sufficient
3. Fill in all sections:
   • Active Focus: files/functions/features worked on
   • Decisions Made: technical choices accepted
   • Facts Learned: new codebase or environment discoveries
   • Open Blockers: unresolved issues
   • Next Action: explicit starting point for next session

Knowledge Distillation

After completing a session, review Facts Learned:

• If a fact is stable and not derivable from code: add it to memory/knowledge/
• If a fact updates existing knowledge: edit the relevant knowledge file
• If a fact is temporary or ephemeral: leave it only in the session note

Memory Pruning

Periodically (weekly or when vault feels cluttered):

• Archive sessions older than 30 days to memory/sessions/archive/
• Remove knowledge entries that are now derivable from code
• Update last_updated on any modified notes
• Check for orphan notes (no incoming links)