foundation-meeting-recap

Name: foundation-meeting-recap
Author: product-on-purpose

486stars64forks

How to install foundation-meeting-recap?

product-on-purpose/pm-skills/foundation-meeting-recap

$npx -y skills add product-on-purpose/pm-skills --skill foundation-meeting-recap

Installs into the current project.

Summary

Produces a topic-segmented post-meeting summary for attendees with decisions highlighted and actions captured inline per topic (plus a consolidated action view at the end). Auto-populates topic skeleton from a sibling meeting-agenda when available and reconciles planned vs. actua

Files · 1

View on GitHub

SKILL.md

1	<!-- PM-Skills \| https://github.com/product-on-purpose/pm-skills \| Apache 2.0 -->
2	# Meeting Recap
3
4	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.
5
6	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.
7
8	This skill belongs to the Meeting Skills Family. It conforms to the [Meeting Skills Family Contract](../../docs/reference/skill-families/meeting-skills-contract.md).
9
10	## When to Use
11
12	- After any internal meeting that produces decisions or actions affecting attendees
13	- When a sibling `foundation-meeting-agenda` exists and needs reconciliation (planned vs. actual topics)
14	- When the team needs a topic-organized reference rather than a chronological transcript dump
15	- When inputs include a transcript (Zoom, Meet, Otter, Fireflies, Krisp MCP) or mixed notes and transcript
16
17	## When NOT to Use
18
19	- Setting the pre-meeting structure attendees will see (topics, owners, time boxes) before the meeting happens. Use `foundation-meeting-agenda`. recap summarizes what happened after a meeting; agenda sets expectations before it.
20	- Preparing the user's private strategic positioning before a meeting that matters. Use `foundation-meeting-brief`. recap is a shared post-meeting record; brief is pre-meeting tactical prep never shown to attendees.
21	- Communicating outcomes to non-attendees. Use `foundation-stakeholder-update`. recap assumes reader context; stakeholder-update translates to readers without it.
22	- Cross-meeting synthesis (patterns across multiple meetings). Use `foundation-meeting-synthesize`.
23	- Synthesizing user research interviews across participants, not one meeting's attendees. Use `discover-interview-synthesis`. recap organizes a single meeting by topic; interview-synthesis finds patterns across many research conversations.
24	- Live meeting note-taking. This skill consumes finished inputs; it does not transcribe live.
25
26	## Zero-friction execution
27
28	Per the family contract, this skill never blocks on interrogation. Default flow:
29
30	1. Read all provided inputs (transcript, notes, or hybrid) and note input quality upfront
31	2. Auto-discover related agenda via filename-prefix match on same-directory `*_{title}_agenda.md`
32	3. Run inference: meeting metadata from content, decisions from language markers, actions from imperative-future patterns, owners from attendee context
33	4. Present a brief inference summary and accept one-word `go` or corrections
34	5. Produce the recap
35
36	If invoked with `--go`, skip the inference summary. If the user provides all metadata upfront, no checkpoint appears.
37
38	## Fabrication prohibition
39
40	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.
41
42	## Ownership reconciliation threshold (v1.1.0)
43
44	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:
45
46	- All unassigned actions
47	- A suggested next step for each (who should probably own this based on topic context, flagged as inference)
48	- A recommended follow-up action (Slack thread, 15-min sync, async survey)
49
50	The shareable summary also leads with this flag when triggered: `⚠ Ownership reconciliation required: N of M actions lack owners.`
51
52	The `unassigned_action_ratio` frontmatter field (float 0.0-1.0) records the ratio for downstream tools.
53
54	Rationale: a recap with 60% ownerless actions is "non-fabricated" (per the prohibition above) but operationally broken. a pile of broken tickets. The

People who liked this also viewed

6 picks

Type

foundation-meeting-recap

486stars64forks

View on GitHub

How to install foundation-meeting-recap?

product-on-purpose/pm-skills/foundation-meeting-recap

$npx -y skills add product-on-purpose/pm-skills --skill foundation-meeting-recap

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	<!-- PM-Skills \| https://github.com/product-on-purpose/pm-skills \| Apache 2.0 -->
2	# Meeting Recap
3
4	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.
5
6	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.
7
8	This skill belongs to the Meeting Skills Family. It conforms to the [Meeting Skills Family Contract](../../docs/reference/skill-families/meeting-skills-contract.md).
9
10	## When to Use
11
12	- After any internal meeting that produces decisions or actions affecting attendees
13	- When a sibling `foundation-meeting-agenda` exists and needs reconciliation (planned vs. actual topics)
14	- When the team needs a topic-organized reference rather than a chronological transcript dump
15	- When inputs include a transcript (Zoom, Meet, Otter, Fireflies, Krisp MCP) or mixed notes and transcript
16
17	## When NOT to Use
18
19	- Setting the pre-meeting structure attendees will see (topics, owners, time boxes) before the meeting happens. Use `foundation-meeting-agenda`. recap summarizes what happened after a meeting; agenda sets expectations before it.
20	- Preparing the user's private strategic positioning before a meeting that matters. Use `foundation-meeting-brief`. recap is a shared post-meeting record; brief is pre-meeting tactical prep never shown to attendees.
21	- Communicating outcomes to non-attendees. Use `foundation-stakeholder-update`. recap assumes reader context; stakeholder-update translates to readers without it.
22	- Cross-meeting synthesis (patterns across multiple meetings). Use `foundation-meeting-synthesize`.
23	- Synthesizing user research interviews across participants, not one meeting's attendees. Use `discover-interview-synthesis`. recap organizes a single meeting by topic; interview-synthesis finds patterns across many research conversations.
24	- Live meeting note-taking. This skill consumes finished inputs; it does not transcribe live.
25
26	## Zero-friction execution
27
28	Per the family contract, this skill never blocks on interrogation. Default flow:
29
30	1. Read all provided inputs (transcript, notes, or hybrid) and note input quality upfront
31	2. Auto-discover related agenda via filename-prefix match on same-directory `*_{title}_agenda.md`
32	3. Run inference: meeting metadata from content, decisions from language markers, actions from imperative-future patterns, owners from attendee context
33	4. Present a brief inference summary and accept one-word `go` or corrections
34	5. Produce the recap
35
36	If invoked with `--go`, skip the inference summary. If the user provides all metadata upfront, no checkpoint appears.
37
38	## Fabrication prohibition
39
40	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.
41
42	## Ownership reconciliation threshold (v1.1.0)
43
44	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:
45
46	- All unassigned actions
47	- A suggested next step for each (who should probably own this based on topic context, flagged as inference)
48	- A recommended follow-up action (Slack thread, 15-min sync, async survey)
49
50	The shareable summary also leads with this flag when triggered: `⚠ Ownership reconciliation required: N of M actions lack owners.`
51
52	The `unassigned_action_ratio` frontmatter field (float 0.0-1.0) records the ratio for downstream tools.
53
54	Rationale: a recap with 60% ownerless actions is "non-fabricated" (per the prohibition above) but operationally broken. a pile of broken tickets. The

People who liked this also viewed

6 picks

Type