Agent skill · Workflow & Productivity

foundation-meeting-brief

Produces a private strategic preparation document for the user before a meeting that matters. Captures stakes, stakeholder positions and reads, ranked desired outcomes, key messages, anticipated questions with prepared responses, risks and tensions, specific asks, and success signals. Distinct from meeting-agenda because this artifact is not shared with attendees; it is the user's personal tactical prep for meetings where positioning matters.

product-on-purposegithub.com/product-on-purposeGitHub ↗
claude-codecodexApache-2.0
Install
npx skills add product-on-purpose/pm-skills --skill foundation-meeting-brief --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 5
SKILL.md size: 7 KB
Bundled scripts: none
Version: 1.0.1
Declared author: product-on-purpose
Path: skills/foundation-meeting-brief/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 518
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # Meeting Brief A meeting brief is the user's private strategic preparation document for a meeting where context, stakes, or positioning matter. It captures what the user needs to know, what they want to accomplish, who they are engaging with, and how to navigate the conversation. This is strategic prep, not meeting structure, which keeps it distinct from a meeting agenda. This skill belongs to the Meeting Skills Family. It conforms to the [Meeting Skills Family Contract](../../docs/reference/skill-families/meeting-skills-contract.md). ## When to Use - Walking into a stakeholder review, exec briefing, or negotiation-adjacent conversation - First meeting with a new stakeholder where relationship calibration matters - A meeting where the user needs something from others (capacity commitment, decision, approval) - Any conversation where specific positioning, messaging, or risk navigation is required ## When NOT to Use - Preparing the agenda attendees will see. Use `foundation-meeting-agenda` instead. - Post-meeting summarization. Use `foundation-meeting-recap`. - The meeting is low-stakes and well-trodde

What's inside
Steps it walks through
  1. When to Use
  2. When NOT to Use
  3. Zero-friction execution
  4. Anti-meeting check
  5. Instructions
  6. Quality Checklist
  7. See also
Ships with 4 files
  • HISTORY.md
  • evals/trigger-fixtures.json
  • references/EXAMPLE.md
  • references/TEMPLATE.md
More from pm-skills
All skills →
About this skill
What does the foundation-meeting-brief skill do?

Produces a private strategic preparation document for the user before a meeting that matters. Captures stakes, stakeholder positions and reads, ranked desired outcomes, key messages, anticipated questions with prepared responses, risks and tensions, specific asks, and success signals. Distinct from meeting-agenda because this artifact is not shared with attendees; it is the user's personal tactical prep for meetings where positioning matters.

How do I install it?

Run `npx skills add product-on-purpose/pm-skills --skill foundation-meeting-brief --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From product-on-purpose/pm-skills, a repository with 518 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going