Meeting Action Item Tracker

Problem Addressed

After meetings, action items can be scattered across notes, discussion threads, and verbal assignments. Owners, deadlines, and follow-up responsibilities may become unclear. This skill is aimed at lightweight meeting follow-up: it turns unstructured meeting content into a trackable action-item list, rather than replacing a project-management system.

How It Works

Input can be meeting notes, transcript text, Markdown notes, or plain text. The skill identifies action-oriented statements containing verbs such as “own,” “follow up,” “complete,” or “submit,” then extracts the owner, deadline, and priority, such as P0, P1, or P2. The output is sorted by priority, flags uncertain items, and generates follow-up messages for DingTalk, WeCom, email, or SMS. For multiple meetings, it can merge tracked items and label the source meeting.

Boundaries

The skill does not invent action items and does not send reminders automatically; it only produces message drafts for manual sending. Owners may be inferred incorrectly and should be verified. It is not intended for large projects requiring Gantt charts, dependency tracking, or workflows, and it does not replace tools like Jira, Lark Projects, or Notion. For better results, provide complete meeting content, clear assignments, and explicit deadlines.