meeting-scribelisted

# Meeting Scribe ## What this does Reads a meeting transcript and a folder of entity files you already keep (people, organizations, other meetings), then produces three things: one dated meeting note, one appended mention line on each entity file the transcript actually names, and a recap email drafted for a human to review — never sent. It never guesses who "sounds like" a tracked entity. A name either matches a file, or it becomes a proposed new entity for you to confirm, or it's ambiguous and gets flagged with every candidate. This is the "brain" idea in miniature: instead of a summary you read once and lose, each entity file grows a small, sourced mention timeline over time. Run it after every meeting and the timeline compounds. Inspired by USV's Meeting Scribe agent: https://blog.usv.com/meet-the-agents — USV built it for VC deal logs (portfolio companies, founders, co-investors). This is our own generic version, not their code: any team that keeps files on people, organizations, or projects can point this at a transcript and get the same shape of output. ## When to use it Use this when you want a per-entity mention history, not a meeting-format memo. If what you actually want is the team's standard circulate-ready notes (Commentary / Observations / To-Dos, or your own frozen template) with carry-forward of open action items across meetings, use `meeting-memo` instead — see [`../meeting-memo/SKILL.md`](../meeting-memo/SKILL.md). The two are complementary: run `meet