Create structured meeting preparation documents. Pulls context from previous transcripts and conversations in the contact's folder to build a comprehensive briefing with talking points, open threads, and suggested agenda.
Generate a structured preparation document for an upcoming meeting or call. Pulls context from previous interactions stored in the contact's folder.
Standalone skill -- works with any vault that uses a _contacts/ directory containing contact folders (e.g. _contacts/firstname-lastname/).
Integration: Output files follow the YYMMDD-{strings.filename_keywords.preparation}-*.md naming convention (förberedelse in Swedish, preparation in English), which /daily-dashboard picks up automatically.
Contact name (required): Name of the person. Matched using the name resolution algorithm:
_contacts/*/_meta.yaml for display_name or aliases matches_contacts/:
david matches _contacts/david-ekberg/ (partial match on first name)erik sandberg matches _contacts/erik-sandberg/bob l matches _contacts/bob-lindgren/Date (optional): When the meeting is. Default: today.
today or no argument -> current datetomorrow -> next dayYYMMDD -> specific date (e.g. 260220)/preparation david -> David's folder, today's date
/preparation david tomorrow -> David's folder, tomorrow
/preparation erik sandberg 260219 -> Erik Sandberg's folder, specific date
/preparation bob l 260220 -> Bob Lindgren's folder, Feb 20
Before writing or modifying any preparation file, check the file's target meeting date:
Meeting date is today or in the future -> proceed normally
Meeting date is in the past -> refuse with this message:
This prep file is for a past meeting (YYMMDD). Mid-meeting or post-meeting notes belong in the transcript file. Use
/transcriptor/opsto capture them. To override, pass--force.
Rationale: preparation files must be frozen at meeting time. Mutating a prep doc with mid-meeting updates destroys the trace and contaminates the document. Live notes belong in the transcript file, which is the canonical post-meeting record.
The --force override exists for legitimate fix-ups (e.g., correcting a typo found post-meeting) but should be rare.
Find the matching folder inside _contacts/ at the vault root using the name resolution algorithm.
Resolution order:
_contacts/*/_meta.yaml files for display_name or aliases matchWhen match found:
_meta.yaml exists, use display_name for document headings and filenames_meta.yaml, derive display name from folder name (title-case, hyphen -> space)If no match found:
_contacts/firstname-lastname/_meta.yaml with display_name and any aliasesCreating _meta.yaml (optional but recommended):