Session Summary — Capture Session Progress

Analyze the current conversation and produce a structured summary.

Process

Step 1: Scan the Conversation

Review for:

1. Decisions made — architectural choices, tool selections, approach decisions
2. Changes applied — files modified, configs changed, services restarted
3. Problems solved — what was broken, root cause, fix
4. Open items — deferred work, unanswered questions, next steps
5. Facts learned — new environment/codebase/domain information
6. Rules established — new conventions, safety rules, policies

Step 2: Write the Summary

Write to memory/YYYY-MM-DD.md (today's date). If file exists, append with timestamp header.

## Session: HH:MM — Brief Topic

### Decisions
- Decision: rationale

### Changes
- `path/to/file`: what and why

### Issues
- Issue → resolution (or "OPEN")

### Key Facts
- Fact worth remembering

### Next Steps
- [ ] Action item

### Rules Established
- New rule: description (promote to MEMORY.md if durable)

Step 3: Promote Durable Facts

If any facts/rules will matter beyond today:

1. Check MEMORY.md for duplicates
2. Propose additions, wait for confirmation before writing

Rules

• Bullet points, not paragraphs
• Include file paths for changes
• ISO dates (YYYY-MM-DD), 24h time
• Omit empty sections
• If session was trivial, say so instead of generating empty template