meeting

Process meeting notes: $ARGUMENTS

IMPORTANT: Be direct

• Don't check if folders exist
• Don't search existing notes
• Just create and append

Step 0: Transcribe (if audio/video input)

If the user provides an audio or video file (.mp3, .mp4, .wav, .m4a, .webm, .ogg) or a URL (YouTube, Google Meet recording, etc.), transcribe it first using trx:

trx "$ARGUMENTS" --output json --fields text

This outputs the full transcript as text. Use that as the meeting content for the steps below.

If the user provides text directly, skip this step.

Flow

1. Create meeting note in 03_Garden/meetings/{YYYY-MM-DD}/{slug}.md:

   ---
   type: meeting
   created: {{date}}
   attendees:
     - "[[Person 1]]"
     - "[[Person 2]]"
   project:
   ---
   # {Meeting Title}
   
   ## Key Decisions
   -
   
   ## Insights
   -
   
   ## Action Items
   - [ ] @{person}: {task}
   
   ## Notes
   {summary of discussion}
   

2. Create corrected transcript in 03_Garden/meetings/{YYYY-MM-DD}/{slug}-transcript.md:

   • Fix common transcription errors (tool names, product names, technical terms)
   • Format as dialogue: **{Person 1}:** ... / **{Person 2}:** ...
   • Keep the natural spoken language as-is
   • Add [Pause], [Screen share], [Laughter] annotations where evident
   • Frontmatter:

   ---
   type: transcript
   created: {{date}}
   meeting: "[[{slug}]]"
   language: {detected language}
   coverage: {full (~Xmin) | partial (~Xmin of Ymin)}
   ---
   # Transcript: {Title} - {duration}
   

3. Create summary in 03_Garden/meetings/{YYYY-MM-DD}/{slug}-summary.md:

   • Written in first person reflecting on the conversation
   • Structured sections: Context, Key Topics, Learnings, Takeaways
   • Frontmatter:

   ---
   type: summary
   created: {{date}}
   meeting: "[[{slug}]]"
   ---
   

4. Create person notes for attendees not yet in 03_Garden/people/