Session → Meeting Log
When to invoke
- The user says "turn this session into a meeting log" or "archive today's discussion".
- The session is approaching the context limit and needs a written artifact.
- The user mentions "extract notes from
~/.claude/projects/.../*.jsonl".
- A long, multi-turn discussion is wrapping up before switching sessions.
Inputs
Locating the session file
- Default location:
~/.claude/projects/<encoded-project-path>/<sessionId>.jsonl
<encoded-project-path>: replace every / and . in the absolute path with -, e.g. /Users/alice/GitHub/MyOrg/my-project → -Users-alice-GitHub-MyOrg-my-project, and /Users/alice/.claude-mem/observer-sessions → -Users-alice--claude-mem-observer-sessions.<sessionId>: a UUID-like string, either supplied by the user or inferred from the most recent mtime in the directory.- If the user doesn't supply one, list the files in the directory, sort by mtime, and confirm the latest one.
JSONL structure
One JSON event per line; common type fields:
| type |
Content |
user |
User prompt, or a tool-execution result — a tool result is a user line whose message.content[] contains a {type: "tool_result", …} block and carries a top-level toolUseResult field. Filter these out before summarising; they are not human input. |
assistant |
Assistant response (incl. tool_use blocks) |
system, attachment, file-history-snapshot, … |
Harness metadata (queue state, mode, cost, permission state); skip anything that is not user/assistant. There is no top-level tool_result or summary type. |
Key fields: timestamp, message.content, message.role, uuid, parentUuid. Sub-agent transcripts live in a separate file, <sessionId>/subagents/agent-*.jsonl, not inline in the main log.
Output
Write to meetings/{YYYY-MM-DD}_{topic}.md:
# {YYYY-MM-DD} — {Topic}
Session id: `<sessionId>`
Mode: <e.g. AI Collaboration Mode (Leader/Developer)>
## Goal
<one-line statement of the session's goal>
## Timeline (milestones only)
- <milestone 1, e.g. "§How.3 round 1 accepted">
- <milestone 2, e.g. "Code Reviewer dispatch produced 7 BLOCKERs">
## Decisions
1. <decision 1>
2. <decision 2>
## Rejected alternatives
- <rejected option> — reason: <reason>
## Hand-offs
- <sub-agent dispatched / next session expected to ...>
## Open questions
- <open question 1>
## Next session
<one-line statement of the next session's intent>
Extraction rules
- No verbatim copying. Summarise decisions and their reasons; drop exploratory chatter, rhetoric, and repeated clarifications.
- Decisions: only items the user explicitly confirmed or the Leader explicitly ACCEPTed.
- Rejected alternatives: options that were discussed and turned down; include a one-line concrete reason.
- Hand-offs: list sub-agents dispatched in this session, or explicitly state what the next session should pick up.
- Open questions: items that didn't converge this session and need a decision next time.
- Don't record tool-call details (e.g. "Read foo.md / Edit bar.md"); only why something was read / changed and the result.
- Timeline keeps only milestones: e.g. "§How.3 round 1 accepted", "Code Reviewer dispatch produced 7 BLOCKERs".
- Never leak secrets: if the JSONL contains tokens / PEM / API keys, delete them, never copy into the meeting log (even if the file itself is private).
Verification checklist
- Filename format
YYYY-MM-DD_<topic-kebab>.md, date in local timezone.
- Contains the seven main sections: Goal / Timeline / Decisions / Rejected alternatives / Hand-offs / Open questions / Next session.
- Entries are summaries, never verbatim copies.
- No secrets / tokens / PII.
- If the session spans multiple days, add a phase tag to the topic (e.g.
kickoff / spec-phase / cr-round1).
Deviation considerations
- Session is too short (< 5 meaningful turns): a standalone log isn't necessarily warranted; append as an addendum to the previous log.
- Session was highly divergent: split into multiple topic-specific logs for the same day, named
{date}_{topic-a}.md / {date}_{topic-b}.md.
- Sub-agent internal exchanges: usually not included in the meeting log; only record the main agent's dispatch + summary of the returned result. They live in
<sessionId>/subagents/agent-*.jsonl, not the main session file, so this needs no filtering step of its own.
Related skills
methodology-pattern-extractor: meeting logs produced here are the input for methodology pattern extraction.backlog-routing-by-topic: open questions that can be classified can also be routed to the matching file's §Backlog.
1---2name: session-to-meeting-log3description: Read a Claude Code session JSONL log and produce a clean timeline-style meeting log at `meetings/{YYYY-MM-DD}_{topic}.md`. Invoke when the user asks "turn this session into a meeting log", "archive today's discussion", "extract a meeting record from jsonl", or when wrapping up a working session before context window rolls.4---56# Session → Meeting Log78## When to invoke910- The user says "turn this session into a meeting log" or "archive today's discussion".11- The session is approaching the context limit and needs a written artifact.12- The user mentions "extract notes from `~/.claude/projects/.../*.jsonl`".13- A long, multi-turn discussion is wrapping up before switching sessions.1415## Inputs1617### Locating the session file1819- Default location: `~/.claude/projects/<encoded-project-path>/<sessionId>.jsonl`20- `<encoded-project-path>`: replace every `/` and `.` in the absolute path with `-`, e.g. `/Users/alice/GitHub/MyOrg/my-project` → `-Users-alice-GitHub-MyOrg-my-project`, and `/Users/alice/.claude-mem/observer-sessions` → `-Users-alice--claude-mem-observer-sessions`.21- `<sessionId>`: a UUID-like string, either supplied by the user or inferred from the most recent mtime in the directory.22- If the user doesn't supply one, list the files in the directory, sort by mtime, and confirm the latest one.2324### JSONL structure2526One JSON event per line; common `type` fields:2728| type | Content |29|---|---|30| `user` | User prompt, **or** a tool-execution result — a tool result is a `user` line whose `message.content[]` contains a `{type: "tool_result", …}` block and carries a top-level `toolUseResult` field. Filter these out before summarising; they are not human input. |31| `assistant` | Assistant response (incl. tool_use blocks) |32| `system`, `attachment`, `file-history-snapshot`, … | Harness metadata (queue state, mode, cost, permission state); skip anything that is not `user`/`assistant`. There is no top-level `tool_result` or `summary` type. |3334Key fields: `timestamp`, `message.content`, `message.role`, `uuid`, `parentUuid`. Sub-agent transcripts live in a separate file, `<sessionId>/subagents/agent-*.jsonl`, not inline in the main log.3536## Output3738Write to `meetings/{YYYY-MM-DD}_{topic}.md`:3940```markdown41# {YYYY-MM-DD} — {Topic}4243Session id: `<sessionId>`44Mode: <e.g. AI Collaboration Mode (Leader/Developer)>4546## Goal47<one-line statement of the session's goal>4849## Timeline (milestones only)50- <milestone 1, e.g. "§How.3 round 1 accepted">51- <milestone 2, e.g. "Code Reviewer dispatch produced 7 BLOCKERs">5253## Decisions541. <decision 1>552. <decision 2>5657## Rejected alternatives58- <rejected option> — reason: <reason>5960## Hand-offs61- <sub-agent dispatched / next session expected to ...>6263## Open questions64- <open question 1>6566## Next session67<one-line statement of the next session's intent>68```6970### Extraction rules71721. **No verbatim copying.** Summarise decisions and their reasons; drop exploratory chatter, rhetoric, and repeated clarifications.732. **Decisions**: only items the user explicitly confirmed or the Leader explicitly ACCEPTed.743. **Rejected alternatives**: options that were discussed and turned down; include a one-line concrete reason.754. **Hand-offs**: list sub-agents dispatched in this session, or explicitly state what the next session should pick up.765. **Open questions**: items that didn't converge this session and need a decision next time.776. **Don't record tool-call details** (e.g. "Read foo.md / Edit bar.md"); only **why** something was read / changed and the **result**.787. **Timeline keeps only milestones**: e.g. "§How.3 round 1 accepted", "Code Reviewer dispatch produced 7 BLOCKERs".798. **Never leak secrets**: if the JSONL contains tokens / PEM / API keys, **delete them, never copy** into the meeting log (even if the file itself is private).8081## Verification checklist8283- Filename format `YYYY-MM-DD_<topic-kebab>.md`, date in local timezone.84- Contains the seven main sections: Goal / Timeline / Decisions / Rejected alternatives / Hand-offs / Open questions / Next session.85- Entries are summaries, never verbatim copies.86- No secrets / tokens / PII.87- If the session spans multiple days, add a phase tag to the topic (e.g. `kickoff` / `spec-phase` / `cr-round1`).8889## Deviation considerations9091- **Session is too short (< 5 meaningful turns)**: a standalone log isn't necessarily warranted; append as an addendum to the previous log.92- **Session was highly divergent**: split into multiple topic-specific logs for the same day, named `{date}_{topic-a}.md` / `{date}_{topic-b}.md`.93- **Sub-agent internal exchanges**: usually not included in the meeting log; only record the main agent's dispatch + summary of the returned result. They live in `<sessionId>/subagents/agent-*.jsonl`, not the main session file, so this needs no filtering step of its own.9495## Related skills9697- `methodology-pattern-extractor`: meeting logs produced here are the input for methodology pattern extraction.98- `backlog-routing-by-topic`: open questions that can be classified can also be routed to the matching file's §Backlog.
wei18