Skip to content
Beta Multi-model support (OpenAI, Gemini, and more) launching soon.
RBA RBA Skills

action-item-tracker

Installable Ships in meeting-to-action — or copy the raw skill below.
Open Claude.ai

Paste into Claude Code, Claude.ai, the desktop app, or the browser extension — ⌘/Ctrl+V.

ExperimentalNo security review

Action Item Tracker

Extract, structure, and validate every action item from a meeting record. Produce a complete action register that is Jira-ready, email-ready, and stakeholder-legible. Surface gaps — missing owners, missing due dates, vague action language — before they become delivery problems.

When this skill applies

  • User has a normalized meeting record and wants a complete action register
  • User pastes notes and asks "what did we commit to?" or "pull the action items"
  • Prior to writing a follow-up email — the action register feeds meeting-followup-draft
  • Prior to pushing to Jira — the action register feeds jira-confluence-push
  • At the start of a meeting to review whether prior actions were completed

Skip when: the user wants only decisions (use decision-log-builder); the user wants to push immediately without reviewing the register first (warn them and offer to review first).

Workflow

Step 1 — Extract action candidates

Read the provided record. Flag every item tagged [ACTION] (from meeting-transcript-parse) or any sentence that:

  • Assigns a task to a named person ("John will...", "The team needs to...")
  • Is a self-assignment ("I'll send...", "Let me check and follow up...")
  • Contains a commitment verb: will, shall, needs to, is responsible for, to action, to follow up, to confirm, to share, to schedule, to send, to review, to update
  • Is stated as a next step in a numbered list ("Next steps: 1. X by Y")

Do not include decisions as actions — "we decided to use Sitecore XM Cloud" is a decision, not an action, unless it spawned a task ("Sarah will initiate the XM Cloud trial account request").

Step 2 — Enrich each action

For every action candidate:

Field Source If absent
Action ID Sequential: ACT-<NNN> Auto-assign
Action description Verbatim or lightly clarified Must be specific and verb-led — see language standards below
Owner name Named person from the meeting If ambiguous, flag [OWNER TBD]
Owner role Role of the named person Extract from attendee list
Owner org RBA / Client / Vendor Extract from attendee list
Due date Stated in the meeting If absent, infer from sprint calendar or flag [DATE TBD]
Priority Inferred from discussion context Default Normal; escalate to High if blocking a milestone
Source Meeting segment where it was raised Segment label
Related decision DEC-NNN if this action implements a decision Cross-reference if decision log is available
Status Open / In Progress / Complete / Blocked Default Open for new actions
Jira issue key Populated by jira-confluence-push after push Leave blank until pushed
Notes Any context needed for the owner Extract from discussion; keep brief

Step 3 — Validate action language

Weak action language creates follow-up debt. Apply these fixes before returning the register:

Weak Strong
"Look into X" "Research X and report findings to Y by [date]"
"Handle the X thing" "Complete X deliverable and share with team by [date]"
"Follow up on X" "Email [role] to confirm X by [date]"
"Try to get X done" "Deliver X by [date]"
"Someone should check..." Flag [OWNER TBD] — do not assign to a phantom owner

Flag every action that required language strengthening so the user can validate the intent was preserved.

Step 4 — Validate owner coverage

Cross-check every action owner against the attendee list:

  • If an action is assigned to someone not in the meeting (e.g., "Ask Sarah to..."), flag [NOT IN MEETING — confirm assignment]
  • If a single person owns more than 40% of all actions, surface a load-balance warning
  • If an action has no owner, flag [OWNER TBD] and prompt the user to assign before the follow-up email goes out

Step 5 — Check against prior register (if provided)

If --prior-register @file-path is provided:

  1. Read the prior register
  2. Match prior open actions by description similarity (not ID, as IDs may not exist)
  3. For each prior open action: mark as Carried Forward, Complete (if evidence in this meeting), or Blocked (if flagged in this meeting)
  4. Present a "Prior action status" table before the new actions

Step 6 — Output the action register

Produce in the format(s) requested (--output markdown|csv|both). Default is markdown. See templates.md for exact formats.

Apply these ordering rules to the markdown table:

  1. High priority actions first
  2. Within same priority: sort by due date ascending
  3. [DATE TBD] actions appear after dated actions
  4. [OWNER TBD] actions appear last

Step 7 — Self-check

  • Every action is specific and verb-led
  • Every action has an owner (name or [OWNER TBD] flag)
  • Every action has a due date (or [DATE TBD] flag)
  • Load-balance warnings are surfaced if one owner has > 40% of actions
  • Actions assigned to non-attendees are flagged
  • The register is ready to paste into a follow-up email or hand to jira-confluence-push

Action language standards

Good action descriptions follow this pattern:

[Verb] [specific object] [and deliver/share/confirm to whom] by [date]

Examples from RBA delivery contexts:

  • "Share updated project timeline with client stakeholders by 2026-06-04"
  • "Create Sitecore XM Cloud environment provisioning ticket in Jira by end of day Friday"
  • "Schedule architecture review with platform team for week of 2026-06-09"
  • "Review and approve content migration runbook before sprint 8 kick-off"
  • "Confirm Azure subscription limits with client IT lead by 2026-06-03"

Reference files

  • templates.md — markdown table template, CSV template, prior-action status table template
Technical details
Plugin
meeting-to-action
Author
Dakota Smith
Skill name
action-item-tracker
Maturity
experimental
Security review
No security review
Owners
  • delivery
Argument hint
[paste normalized record or @file-path] [--prior-register @file-path] [--output markdown|csv|both] [--sprint <sprint-number>]
Allowed tools
  • Read
  • Write
  • Glob
Source
plugins/meeting-to-action/skills/action-item-tracker/SKILL.md

Edit this skill on GitHub — opens GitHub's web editor. No git knowledge needed.