meeting-note

name	meeting-note
description	Meeting note skill — scaffold a structured meeting page with cross-links

Meeting Note

Capture a substantive meeting as a structured wiki page.

When to invoke

Run this skill when the user says "meeting note", "log this meeting", "capture meeting", "after the meeting", or similar. Also triggered by /meeting-note.

Distinguish from short standups or one-line check-ins, which belong inline on the daily page. A standalone meeting page is appropriate when:

• The meeting has multiple decisions or action items.
• Attendees include external parties or stakeholders worth recording.
• Notes will be referenced later (e.g. vendor demos, planning sessions, design reviews).

Behavior

Step 1 — Gather meeting metadata

Ask the user for any details not already provided:

• Title — short, descriptive (e.g. "Q2 kickoff", "Klaviyo vendor demo").
• Date — defaults to today; ask only if the meeting was on a different day.
• Start / end time — optional but recommended for scheduling cross-references.
• Attendees — comma-separated names.
• Project — the related project slug, if any (e.g. storefront). Optional.

Step 2 — Create the meeting page

Run via Bash:

rubber-ducky page create meeting "<title>" \
  --date <YYYY-MM-DD> \
  --start <HH:MM> \
  --end <HH:MM> \
  --attendees "<comma-separated>" \
  --project <slug>

Omit any flags the user didn't supply. The CLI scaffolds the page at wiki/meetings/<date>-<slug>.md with frontmatter and standard body sections (Agenda, Notes, Decisions, Action items, Related).

Step 3 — Fill in the body

Edit the new page directly to capture meeting content under each section:

• Agenda — what was planned to discuss.
• Notes — what was actually said. Verbatim quotes for important moments.
• Decisions — what the group decided. One bullet per decision.
• Action items — - [ ] <task> per item, with assignee names. These should later become tasks: ask the user "Convert any of these to tasks?" If yes, run /new-ticket or rubber-ducky page create task for each.
• Related — wikilinks to related task pages, project pages, prior meetings.

Step 4 — Cross-link

If the meeting touches existing tasks, append a wikilink in each task's Activity log:

- Discussed in [[wiki/meetings/<date>-<slug>|<title>]]

If the meeting belongs to a project, append the meeting wikilink to the project's index page.

Step 5 — Update the daily page

Add a one-line entry to today's daily page so the meeting shows up in the temporal spine:

- **<HH:MM>–<HH:MM>** — [[wiki/meetings/<date>-<slug>|<title>]] — <one-line takeaway>

Output

A populated meeting page with all sections filled in (or marked TBD with a question), plus cross-links from related tasks and the daily page. Confirm where the page was saved and whether any action items should be promoted to tasks now.