meeting-notes

name	meeting-notes
description	Convert meeting discussions into concise, actionable notes with decisions, tasks, follow-ups, and open questions.

Meeting Notes

Use this skill when the user wants meeting notes, a meeting summary, action-item extraction, a decision log, preparation notes, or a cleaned-up meeting record.

Operating Principles

• Focus on outcomes, decisions, open questions, and follow-through.
• Prefer concise, scannable notes over near-verbatim minutes.
• Keep uncertainty visible. Mark unclear owners, dates, and decisions as TBD.
• Do not invent attendees, decisions, deadlines, or commitments.
• Keep sensitive source details out of summaries unless the user explicitly asks to preserve them.
• If the notes are going into an Obsidian-style vault, use real tabs or at least four spaces for nested Markdown list items.

Standard Output

# Meeting Title

**Date**: YYYY-MM-DD
**Time**: HH:MM-HH:MM
**Location**: Video call / Room / Async

## Attendees

- Name or role

## Summary

- Short point that captures the useful result of the discussion.

## Decisions

- **Decision**: What was decided.
    - **Rationale**: Why this choice was made.
    - **Impact**: What changes because of it.

## Action Items

- [ ] **Owner**: Concrete task
    - **Due**: YYYY-MM-DD or TBD
    - **Acceptance criteria**: What done looks like

## Open Questions

- Question that still needs an answer.
    - **Owner**: Name or TBD
    - **Needed by**: Date or TBD

## Follow-Up

- Next meeting, message, document, ticket, or review needed.

Meeting Package Layout

The layout below is this plugin's opinionated Obsidian convention, not an Obsidian standard. Read ../../docs/obsidian-meeting-package.md when the user wants a folder-based meeting package, when you need to configure or discover an Obsidian vault, or when you need to explain the convention. If the user already has a different vault structure, adapt to that instead of forcing this layout.

When the user wants a folder-based meeting package, use this structure:

Meetings/
  YYYY/
    YYYY-MM/
      YYYY-MM-DD HH.mm - Meeting title/
        Meeting.md
        Preparation.md
        Transcript.md
        Attachments/
        Materials/

Rules:

• Meeting.md is the canonical meeting note.
• Preparation.md holds substantial pre-read or prep.
• Transcript.md holds transcript text if available.
• Attachments/ holds source files or binary material.
• Materials/ holds supporting markdown/context notes.
• Keep decisions, action items, and follow-up in Meeting.md unless the user asks for a separate decision log or task file.

Extraction Checklist

When processing raw notes or a transcript, capture:

• Decisions made
• Action items with owner, due date, and acceptance criteria
• Follow-up messages, meetings, or tickets
• Open questions and blockers
• Risks or dependencies that could change the plan
• Links or references that are necessary to understand the outcome

Quality Bar

• Every action item has an owner or is marked TBD.
• Every deadline is explicit or marked TBD.
• Every decision has enough rationale to prevent re-litigating it later.
• The summary can be understood by someone who missed the meeting.
• Private or irrelevant conversational detail is omitted.