meeting-notes
Meeting Notes
One skill for the full 1-1 and meeting-note lifecycle: prep → meeting → dictated or photographed notes → shareable learning document → next prep. The modes share one file convention, so each meeting's outputs become the next meeting's inputs.
Not every meeting is a meeting. A ToR or implementation-plan review cycle settles decisions in the margins of a document, and those need the same note, the same action tables and the same tracker row as a call would. That is the marginalia mode.
Mode selection
| Signal from Ane | Mode | Read |
|---|---|---|
| "I want to dictate", "debrief my meeting/1-1", spoken-style topic summaries | Dictated notes | references/dictation-mode.md |
| "prep my 1-1", "prepare my meeting with [manager]", "what do I owe Lena" | 1-1 prep | references/prep-mode.md |
| Image or scan paths + "draft notes from this photo/scan", handwritten notes | Handwritten notes (photo/scan) | references/photo-mode.md |
| A voice/video recording file, or a transcript (Teams .vtt/.docx, txt) | Recordings and transcripts | references/transcript-mode.md |
| A reviewed .docx whose decisions sit in comments: "the decisions are in the comments", "marginalia", "turn the review comments into notes" | Document marginalia | references/marginalia-mode.md |
| "learning document", "shareable summary of this meeting" + a finished note | Learning document | references/learning-document-mode.md |
Read only the reference file for the selected mode. If the mode is ambiguous, ask in one line; do not guess between prep and notes. Any other capture method (chat log, email thread as minutes, whiteboard photo) normalises to text and then follows references/transcript-mode.md from step 2, so every way a meeting gets captured has a route into the same note structure.