← ClaudeAtlas

meeting-action-itemslisted

Turn meeting notes into cited decisions, owners, tickets.
wlkerwong-boop/family-ai-skills · ★ 0 · AI & Automation · score 76
Install: claude install-skill wlkerwong-boop/family-ai-skills
# Meeting Action Items Convert an existing transcript or notes set into accountable follow-through. `teams-meeting-pipeline` can retrieve Teams artifacts; this skill begins once notes/transcript content is available, from any source. ## When to Use - "Extract action items from this meeting." - "What did we decide and who owns what?" - "Draft the follow-up and create tickets." - "Reconcile these notes with the existing project board." Don't use for: retrieving meeting recordings or transcripts (use `teams-meeting-pipeline` or the relevant connector first). ## Procedure ### 1. Establish meeting evidence Use `read_file` on the provided notes/transcript files. Identify meeting title/date, participants, source files, transcript completeness, and whether speaker/time references exist. Done when missing portions and low-confidence transcription are stated. ### 2. Separate evidence types Extract into distinct lists: - decisions actually made - proposals not decided - explicit commitments - questions and blockers - risks and dependencies - facts/context Do not turn brainstorming into decisions. Done when each candidate item has a supporting quote, timestamp, page, or note reference when available. ### 3. Normalize action items For every commitment record: | Field | Rule | |---|---| | outcome | Concrete result, not a vague topic | | owner | Explicit named owner; otherwise `unresolved` | | due date | Explicit date or `unresolved`; never invent one | | dependency | What mus