Actions

Action Tracker

Maintain and query ./Meetings/ACTIONS.md, the single living list of every commitment across all meetings. This is what makes the plugin worth using: nothing falls through the cracks.

Uses the action-item format and ledger structure from the meeting-notes core skill and ${CLAUDE_PLUGIN_ROOT}/skills/meeting-notes/templates/ACTIONS.md.

The user's intent comes via $ARGUMENTS. Interpret it:

Maintaining the ledger

Reconcile (the dedup logic recap relies on)

When adding items, an action already exists if it has the same owner and substantially the same task (ignore wording differences, tense, trailing punctuation). When a match is found:

• Keep one line. Update the due date if the new mention has a newer/clearer one.
• If it was discussed again in a later meeting, update the · _Source_ suffix to the most recent meeting (or note "(re-raised)").

Never create a second line for the same real-world commitment.

Recompute status

Every time you touch the ledger, re-sort items into sections against today's date:

• 🔴 Overdue — due date is before today and not done.
• 🟡 Open — not done, due today or later, or (no date).
• ✅ Done — completed (keep the most recent ~20, archive older ones to the bottom or a ## Archive section so the file stays readable).

Update the _Last updated: <date>_ line at the top.

Marking done

When the user says an item is done:

• Change - [ ] to - [x], move it to ✅ Done, append · done <today>.
• Confirm in one line, and if it unblocks something obvious, mention it.

Output style

Be a scannable status board, not a wall of text. Lead with what's on fire:

🔴 Overdue (2)
  @You      Update billing spec        — due Jul 6   · Product Sync (Jun 29)
  @Sarah    Send pricing deck          — due Jul 3   · Product Sync (Jun 29)

🟡 Open (5) — @You: 2 · @Sarah: 1 · @Dev: 1 · @unassigned: 1
  ...

Tip: 1 item is still @unassigned — assign it with "/meeting-notes:actions" or tell me who owns it.

Always end by surfacing anything @unassigned or (no date) so the user can resolve it.