Claude Code files meetings through an uncertainty gate

Don describes an everyday meeting system made from local folders and Markdown instructions. Transcripts arrive in an inbox; CLAUDE.md explains the workspace and points to CONTEXT.md for processing rules. Claude Code reads those files when the user asks it to process the inbox.

For each meeting, the agent reads transcripts and notes, extracts a summary, decisions, actions and risks, and checks reference files for the required format. It resolves attendees against people records, consulting the calendar invite when an attendee list is absent. It identifies the project, splits a multi-project meeting when needed, reconciles recent information with earlier notes and adds links to related meetings.

Uncertainty changes the destination. Clean work goes into the project folders; unresolved people or project assignments go into a needs-review folder with explicit questions. In the demonstrated run, three transcripts were processed, the inbox emptied and one meeting remained for review. Don answers the exceptions rather than approving every step. The useful pattern is that folder location records status visibly for both person and agent. The source supplies a concrete file-based result and describes daily use, but does not independently assess extraction accuracy or prove the agent catches every ambiguous statement.

Prompt
Original prompt

Source: Blog · Don of Don’s Bookshelf