Stats
Actions
Tags
From pm-skills
Generates topic-segmented meeting summaries with decisions highlighted and actions captured inline per topic plus consolidated action view. Auto-populates from sibling meeting-agenda and accepts transcripts from Zoom, Meet, Otter, Fireflies, Krisp MCP, or manual notes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-skills:foundation-meeting-recapThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
A meeting recap is a post-meeting topic-segmented summary produced for attendees and light distribution. It organizes content by topic rather than chronology, highlights decisions visually, and captures actions inline (with owner, due date, dependencies) per topic segment, plus a consolidated actions view at the end for scannability.
This skill absorbs what would otherwise be a separate "meeting-actions" skill. Actions in this family live alongside the context that makes them meaningful, not in a sibling artifact.
This skill belongs to the Meeting Skills Family. It conforms to the Meeting Skills Family Contract.
foundation-meeting-agenda exists and needs reconciliation (planned vs. actual topics)foundation-stakeholder-update. recap assumes reader context; stakeholder-update translates to readers without it.foundation-meeting-synthesize.discover-interview-synthesis. recap organizes a single meeting by topic; interview-synthesis finds patterns across many research conversations.Per the family contract, this skill never blocks on interrogation. Default flow:
*_{title}_agenda.mdgo or correctionsIf invoked with --go, skip the inference summary. If the user provides all metadata upfront, no checkpoint appears.
This skill never fabricates owners, decisions, or actions. When an action lacks an explicit owner, it is captured as [owner: unassigned, needs confirmation] not invented. When a decision is implicit ("it sounded like we decided X"), it is flagged with a confidence marker rather than stated as fact. Trust decay from fabrication is worse than the mild friction of flagging.
When the ratio of unassigned actions to total actions exceeds 0.3 (30%), OR when any high-priority action lacks an owner, the skill surfaces a dedicated ## ⚠ Ownership reconciliation required section at the top of the recap (above the topic segments) listing:
The shareable summary also leads with this flag when triggered: ⚠ Ownership reconciliation required: N of M actions lack owners.
The unassigned_action_ratio frontmatter field (float 0.0-1.0) records the ratio for downstream tools.
Rationale: a recap with 60% ownerless actions is "non-fabricated" (per the prohibition above) but operationally broken. a pile of broken tickets. The threshold makes this visible instead of silently shipping.
When asked to create a meeting recap, follow these steps:
Parse inputs and detect type Transcript (timestamped speaker-attributed lines), notes (bullet or prose), or hybrid. Note input quality upfront. transcript plus structured notes is high; scrappy bullets is low.
Auto-discover related agenda
Look in the same directory for a file matching the pattern {YYYY-MM-DD}_{HH-MMtimezone}_{title-slug}_agenda.md. If found, load it. its topic list is the recap's topic skeleton and its desired_outcomes drive the meeting-quality reconciliation.
Present go-mode inference summary
Show detected meeting date, title, attendees (if inferred), input quality assessment. Accept go or corrections.
Topic-segment the content
Per topic segment, extract
[owner: unassigned] and missing dates as [due: not specified]. Never invent.Consolidate actions by owner Regroup all actions under each owner. Enables single-owner scan ("what do I owe after this meeting?").
Reconcile agenda (if agenda loaded)
topics_planned: from agenda topic listtopics_hit: topics actually discussedtopics_skipped: planned but not discussed, with brief reasontopics_emerged: discussed but not on agendaAssess meeting quality signals
outcomes_achieved: N/M ratio of agenda desired_outcomes met (when agenda present)started_on_time / ended_on_time: from timestamps when available; skipped when notkey_attendees_present: flag if decision-makers were absentSurface next steps When we reconvene, what needs to happen on the critical path before that.
Render TEMPLATE.md and validate
attendees or is explicitly unassignedmeeting_quality.outcomes_achieved matches N/M pattern when populatedagenda_reconciliation fields present even when empty listsunassigned) + due date (or explicit not specified)foundation-meeting-agenda. upstream: provides topic skeleton and desired-outcomesfoundation-meeting-synthesize. downstream: consumes recaps for cross-meeting synthesisfoundation-stakeholder-update. downstream: translates recap outcomes to non-attendeesnpx claudepluginhub product-on-purpose/pm-skills --plugin pm-skillsConverts meeting notes, transcripts, or chat logs into structured minutes with decisions, action items, and open questions.
Extracts key decisions, takeaways, action items with DRIs, and open questions from meeting transcripts, notes, or Slack threads. Handles single meetings or weekly batches.
Generates structured Markdown meeting summaries from transcripts, recordings, or notes, including date, participants, topics, key points, decisions, action items table, and open issues.