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.
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 |
| "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.
Shared rules (all modes)
Storage. Recurring 1-1 notes and preps live in C:/Users/AGasser/OneDrive/1. Ane's PROJECTS/Ane Plans/. Project-meeting notes live in the project folder Ane names. Naming: Meeting note - Ane-<counterpart> - YYYY-MM-DD.md and 1-1 prep - Ane-<counterpart> - YYYY-MM-DD.md. The .md is the source of truth; the .docx is generated from it, never dual-edited.