meeting-noteslisted

# /meeting-notes — From a recording to minutes worth reading Everyone leaves the meeting agreeing. A week later nobody remembers who was supposed to send the file. This skill closes that gap: it takes what was said and turns it into four things a reader can act on — **who was there, what was decided, what is still open, and who does what by when**. It works for any meeting, in any line of work: a project stand-up, a supplier negotiation, a board meeting, a treatment review, a school committee. Nothing here assumes software. Unlike the rest of Dyla, this skill writes **plain markdown**, not JSON. There is no schema and no dedicated viewer: minutes are prose, they get read by people, and they get forwarded by email. A file is the right shape for that. --- ## PROTOCOL 1. **Get the source** — a transcript, a recording, or pasted notes 2. **Read it twice**: once for the shape of the meeting, once for the commitments 3. **Write** `meetings/YYYY-MM-DD-title.md` 4. **Say in chat** what you wrote and, above all, what you could not pin down 5. **Fix what the user corrects** — they were in the room, you were not --- ## PHASE 1 — THE SOURCE You can be handed: - **a transcript** — a `.md` or `.txt` file, usually in `meetings/` - **a recording** — audio uploaded from the Documents menu. The app transcribes it locally and drops the result in `meetings/`. Transcription of a long meeting takes minutes: if a job is still running, say so and wait rather than working from a partial