From pm-skills
Synthesizes patterns across multiple meeting recaps over time—tracks decision evolution, stakeholder position shifts, stalling threads, and contradictions. Produces timeline, themes, decision list, and follow-ups.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-skills:foundation-meeting-synthesizeThe 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 -->
Meeting synthesis is the archaeology skill for multi-meeting initiatives. It consumes a set of meeting recaps (and optionally raw notes) over a period, and surfaces patterns that no single meeting reveals: how decisions evolved, how stakeholder positions shifted, where threads are stalling, where contradictions have emerged.
Distinct from /discover-interview-synthesis: that skill works on user-research conversations with research-specific frameworks (jobs-to-be-done, buying insights). This skill works on internal org meetings with org-specific patterns (stakeholder alignment, decision evolution, project history).
This skill belongs to the Meeting Skills Family. It conforms to the Meeting Skills Family Contract.
foundation-meeting-recap instead.foundation-stakeholder-update./discover-interview-synthesis.Per the family contract, this skill never blocks on interrogation. Default flow:
go or correctionsIf invoked with --go, skip the inference summary. Format hints (board-prep, onboarding, retro-input, exec-brief) control output presentation without changing the underlying process.
When asked to create a meeting synthesis, follow these steps:
Load sources
Read all provided recap filenames or note files. Parse frontmatter to extract meeting metadata. Note per-source input quality (recap frontmatter's input_quality if available; otherwise assess from content).
Metadata source tracking (v1.1.0): for each recap, also note the meeting_type_source field (explicit | inferred | null). When synthesizing across mixed sources, the synthesis must document the mix explicitly in the Scope section: "meeting_type values: N explicit, M inferred, K null." This prevents non-reproducible results when filtering by meeting_type across a mix of confidence levels. If filtering by meeting_type, state whether the filter includes inferred values and how null values are handled.
Apply filters
If time range, topic, or stakeholder filter provided, narrow the source set before proceeding. Record the filter applied in frontmatter scope_filter.
Present go-mode inference summary Meeting count after filter, time range detected from source metadata, per-source input quality levels, scope filter description.
Build the plain-text timeline
Chronological order by meeting_date. Each entry shows date, meeting name, key decision or shift, and confidence or contradiction flag if applicable. Render as markdown (no binary images. must render everywhere).
Extract themes Cluster recurring topics across sources. For each theme, record description, sources where it appeared, and confidence marker tied to frequency ("appears in 5/5 meetings" → high; "appears in 2/5 meetings" → medium; "mentioned in 1 meeting" → low).
Track stakeholder positions For each named stakeholder across sources, record initial position → current position, alignment state (aligned / divergent / shifting), and key statements with dates. Flag confidence on each position based on whether it was direct-quoted or paraphrased.
Consolidate decisions Cross-meeting, sorted chronologically. Table format: Date | Decision | Context | Meeting | Confidence.
Separate decision evolution from unresolved contradictions (v1.1.0) Two distinct outputs, not one combined "contradictions" section:
⚠ emphasis.⚠ visual emphasis. For each:
The distinction matters because v1.0.0 conflated them, creating false-positive "contradictions" in exec contexts where the "contradiction" was actually intentional scope evolution.
Identify open items and stalled threads Topics surfacing 2+ times without resolution. When they last appeared.
Draft narrative summary 2-3 paragraphs: what happened, what changed, where we are, what is at stake. The "story" of the meeting set.
Prioritize follow-up suggestions
Apply format hint (if provided) One process generates the full synthesis data. The hint controls section ordering and truncation for the specific use case:
board-prep: lead with narrative + contradictions + prioritized follow-ups; shorter timelineonboarding: lead with narrative + stakeholder tracking; full timelineretro-input: lead with themes + stalled threads + meeting-quality aggregateexec-brief: TL;DR + top 3 items onlyRender TEMPLATE.md and validate
source_meetings list is non-emptytime_range.start ≤ time_range.endfoundation-meeting-recap. upstream: primary input source/discover-interview-synthesis. sibling pattern for user-research conversations (different domain)npx claudepluginhub product-on-purpose/pm-skills --plugin pm-skillsExtracts key decisions, takeaways, action items with DRIs, and open questions from meeting transcripts, notes, or Slack threads. Handles single meetings or weekly batches.
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.
Activate for: meeting prep, meeting synthesis, before the meeting, after the meeting, D/A/F/Q/R, meeting brief, stakeholder prep, meeting notes synthesis, meeting follow-up, meeting actions, meeting decisions, post-meeting notes, synthesise the meeting, what was decided in the meeting, meeting record. NOT for: situation briefs (use executive-brief), daily digest (use digest).