1. Read Session Log

Read the session log file completely:

• Parse frontmatter metadata (issue, duration, dates)
• Read entire conversation thread
• Identify key sections (if marked)
• Note file changes and operations

2. Analyze Conversation

Extract the following information:

Main Accomplishments

What was actually completed during this session?

• Features implemented
• Bugs fixed
• Refactorings completed
• Documentation written
• Tests added

Key Decisions Made

What technical decisions were made and why?

• Architecture choices with rationale
• Library/framework selections
• Design pattern choices
• Trade-offs considered
• Alternatives discussed

Learnings & Insights

What was learned during this session?

• New techniques discovered
• Gotchas and pitfalls encountered
• Best practices identified
• Performance insights
• Security considerations

Files Changed

Categorize file changes:

• New files created
• Files modified
• Files deleted
• Configuration changes
• Documentation updates

Issues Encountered

What problems arose and how were they solved?

• Errors and error messages
• Debugging approaches
• Solutions applied
• Workarounds used
• Root causes identified

Follow-up Items

What still needs to be done?

• TODO items mentioned
• Unresolved questions
• Future improvements
• Testing gaps
• Documentation needs

3. Generate Summary

Create structured markdown summary with these sections:

---
session_id: [from log]
issue_number: [from log]
issue_title: [from log]
date: [from log]
duration: [from log]
summary_generated: [timestamp]
---

# Session Summary: [Issue Title]

## Overview
[2-3 sentence high-level summary of what this session accomplished]

## Key Accomplishments
- [Concrete achievement 1]
- [Concrete achievement 2]
- [Concrete achievement 3]

## Technical Decisions
### [Decision 1 Topic]
**Decision**: [What was decided]
**Rationale**: [Why this approach]
**Alternatives Considered**: [Other options]

### [Decision 2 Topic]
...

## Learnings & Insights
- **[Learning 1]**: [Description and context]
- **[Learning 2]**: [Description and context]
- **[Learning 3]**: [Description and context]

## Files Changed
### New Files
- `path/to/file1.ts` - [Purpose]
- `path/to/file2.ts` - [Purpose]

### Modified Files
- `path/to/file3.ts` - [What changed]
- `path/to/file4.ts` - [What changed]

### Configuration
- `config/file.json` - [What changed]

## Issues Encountered & Solutions
### [Issue 1 Title]
**Problem**: [Description]
**Solution**: [How it was resolved]
**Root Cause**: [Why it happened]

### [Issue 2 Title]
...

## Follow-up Items
- [ ] [TODO item 1]
- [ ] [TODO item 2]
- [ ] [Unresolved question]

## References
- Issue: #[issue_number]
- Session Log: [link to full log]
- Duration: [X hours Y minutes]
- Status: [completed/in-progress/blocked]

4. Save Summary

Write summary to output path:

• If separate_paths enabled: Save to cloud_summaries_path
• Otherwise: Save alongside session log with -summary.md suffix
• Ensure proper permissions and directory structure