meeting-note-taker v1.2.0

Guides you through structured meeting note capture and produces a formatted summary saved to your meeting notes directory.

Overview

The meeting-note-taker plugin provides a conversational agent that walks you through the full meeting note lifecycle:

1. Choose a subdirectory and filename (with smart defaults)
2. Set the meeting title
3. Enter your raw notes at your own pace
4. Let the agent analyze and structure the notes into a clean document
5. Auto-save to the configured meeting notes directory

The generated document always includes a header table and a prose summary (with Mermaid diagrams for any technical flows or topic maps). A Questions & Answers table and Actions checklist are added only when the notes actually contain that content.

Prerequisites

No additional installation is required. The plugin works with the VS Code Chat Plugin Marketplace out of the box.

To customize the meeting notes directory, set the MEETING_DIR environment variable before starting VS Code:

# Linux / macOS
export MEETING_DIR="$HOME/work/meeting-notes"

# Windows (PowerShell)
$env:MEETING_DIR = "C:\work\meeting-notes"

If MEETING_DIR is not set, the hook falls back to:

Hooks

Agents

Output Document Structure

The agent saves a .md file with this structure (conditional sections shown with ▸):

# Meeting Notes
| Date | Title | Noted By |

# Summary
<prose summary>
▸ Mermaid diagrams (sequence, flowchart, mindmap — when applicable)

▸ # Questions and Answers   (omitted if no questions found)
  | # | Question | Answer |

▸ # Actions                 (omitted if no actions found)
  - [ ] pending action
  - [x] completed during meeting

# Original Notes
<verbatim notes>

File Naming

All note files follow the pattern:

<prefix>-YYYY-MM-DD-HH-mm.md

Example: meeting-2026-04-16-14-30.md

The prefix defaults to meeting and the subdirectory defaults to general — both are configurable per session.

Configuration Reference

Author

Dimpletz