brain-meetinglisted

# Meetings Two jobs with the same subject and opposite directions. Prep reads and writes nothing. Debrief writes a note and everything that note owes. Resolve the vault as `${CLAUDE_PLUGIN_ROOT}/STANDARD.md` §7 describes. The `meeting` schema is §2.3, `person` is §2.4, and the sections are §4. ## Prep — read only Given who and what: 1. Read each attendee's `person` note: `## Facts`, the last few `## Interactions`, and every open `## Follow-ups` item. 2. Read the `project` note if the meeting has one — `## Now` and the most recent `## Decisions`. 3. Read the last one or two meetings with these people. Their `## Actions` are the highest-value lines in the vault right now: an action you owe and have not done is what you want to know before walking in, not after. Brief in this order: **what you owe** (open follow-ups and unfinished actions), **where things stand**, **who these people are**, **what is unresolved**. Cite the note behind each block. Write nothing during prep. Prep that files things is prep the user stops trusting to be cheap. ## Debrief — write the note and its links Given what happened, in whatever form the user hands it over: 1. **Write the meeting note** at `meetings/YYYY-MM-DD-<slug>.md`, with the §2.3 frontmatter: `title`, `timestamp` of when the meeting *happened*, `attendees` as vault-relative paths to `person` notes, `project` if there is one, `tags` if they help. Sections `## Notes`, `## Decisions`, `## Actions`. 2. **Create a