Skip to content
Agentmart
Submit a tool

foundation-meeting-brief

Produces a private strategic preparation document for the user before a meeting that matters.

Skill by product-on-purpose

IndexedApache-2.0★ 758
Write a review

Chalk Labs

Need help deploying foundation-meeting-brief?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/product-on-purpose-foundation-meeting-brief

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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.

Use cases: documents, productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/foundation-meeting-brief

What's inside

Skill name
foundation-meeting-brief
Description
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.
License
Apache-2.0
Metadata
author: product-on-purpose · updated: 2026-07-04 · version: 1.1.0 · category: meeting · classification: foundation
Instructions
125 lines in SKILL.md · view on GitHub

Files (5)

  • HISTORY.md
  • SKILL.md
  • trigger-fixtures.json · evals/
  • EXAMPLE.md · references/
  • TEMPLATE.md · references/

SKILL.md (first lines)

<!-- 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](../../site/src/content/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-trodden (recurring team sync, standup). A brief is overhead for these; the agenda alone is sufficient.

## Zero-friction execution

Per the family contract, this skill never blocks on interrogation. Default flow:

1. Read all provided inputs (topic, attendees, prior recaps, stakeholder summaries, user's primary ask)
2. Auto-discover related artifacts via `project` or `topics` frontmatter match
3. Run inference on missing values (stakeholder positions from prior recaps, primary ask from topic, top-3 goals from meeting type)
4. Present a brief inference summary and accept one-word `go` or corrections
5. Produce the brief

If invoked with `--go`, skip the inference summary. If the user provides all values upfront, no checkpoint appears.

The skill runs on inferred stakeholder positions with low-confidence flags when no stakeholder summaries are provided; it does not block on missing inputs.

## Anti-meeting check

This skill opens with the shared anti-meeting check. see [`foundation-meeting-agenda`](../foundation-meeting-agenda/SKILL.md) for the full check.

**v1.1.0**: the check requires a positive synchronous-value statement (tradeoff to discuss, conflict to resolve, co-creation, relationship-building, or blocker escalation). Brief-prep scenarios most often pass because they typically involve navigating stakeholder positions or negotiation dynamics. which qualify as "conflict to resolve" or "relationship-building." But the check still runs, and if no synchronous value is named, the skill recommends the async alternative before producing a brief.

**Load-bearing inference gates** (v1.1.0): when stakeholder positions, primary ask, or decision-maker attribution are inferred below-high confidence, flag in the go-mode summary with `⚠`. The brief's tactical guidance depends on these; silent acceptance of weak inferences creates risky advice. See family contract "Zero-friction execution" section.

## Instructions

When asked to create a meeting brief, follow these steps:

1. **Run anti-meeting check**
   Apply the trigger patterns. If matched, propose async alternative and await override.

2. **Parse and load inputs**
   Read the topic. Load any `@file` references. Auto-discover related artifacts: prior recaps on same topic (same `project`/`topics` frontmatter), stakeholder summaries from `/discover-stakeholder-summary` outputs, related project docs.

3. **Infer missing values**
   Apply these rules:

   | Value | Inferred from | Confidence |
   |-------|---------------|------------|
   | Stakeholder positions | Prior recap language, stakeholder summary content | High if recap cites direct quote; medium if position in 2+ sources; low otherwise |
   | Stakes per attendee | Role plus topic-ownership cues | Always flag inferences |
   | Top 3 goals | User's primary ask plus meeting type | Offer as ranked strawman in go-mode |
   | Anticipated questions | Stakeholder position analysis plus typical-by-role objections | Flag as inferred |
   | Risks / tensions | Conflict patterns in prior recaps | High if prior recap flagged contradiction |

4. **Present go-mode inference summary**
   Show the inferred stakeholder positions, primary ask, top-3 goals. Accept `go` or corrections.

5. **Build the background section**
   Relevant history, prior decisions, recent developments. Cross-reference prior recaps by filename when available.

6. **Do per-stakeholder analysis**
   For each key attendee: position on topic, stakes (what they win or lose), likely concerns, relationship state (strong / neutral / strained), tactical notes (how to engage).

7. **Rank desired outcomes**
   Must achieve / should achieve / nice to achieve. Force the tradeoff explicitly.

8. **Draft key messages**
   In priority order, phrased for delivery. Not bullet points to read; phrased as you would say them.

9. **Anticipate questions and responses**
   Table format: Q | prepared response. Aim for the three questions the user is most likely to get.

10. **Identify risks and tensions**
    With explicit mitigations. Flag anything that could derail the meeting.

11. **Specify asks**
    What the user needs from specific people by name. Not generic "get alignment" but "ask alex to commit eng capacity for Q2 by Thursday."

12. **Define success signals**
    How the user knows in the moment that the meeting went well. Behavioral cues, not just outcome markers.

13. **Render TEMPLATE.md and validate**
    - `visibility: private` default
    - Stakeholder list has minimum fields (name, position) when present
    - Primary ask is non-empty (use "alignment" or "information gathering" if no specific ask)

## Project Memory Contract

Active only when `.claude/pm-skills.local.md` exists. With no file, ignore this section entirely
and behave exactly as described above.

- **Reads:** `active_initiative` and recent `decision` artifacts, so the brief can state the current position without you re-supplying it.
- **Writes:** nothing. The brief is preparation; the recap is what becomes durable.
- **Posture:** propose the entry and wait for confirmation before writing, unless
  `memory_auto_append: true` is set, in which case append and echo what was written.

This complements the family's filename-based chaining rather than replacing it: filenames still locate the sibling artifacts of one meeting, while project memory carries the durable product context across meetings.
## Quality Checklist

- [ ] Anti-meeting check was applied and recorded
- [ ] `visibility: private` default applied
- [ ] Background section cross-references prior recaps when available
- [ ] Every key stakeholder has a position, stakes, concerns, relationship state entry (with confidence markers on inferred fields)
- [ ] Desired outcomes are ranked (must / should / nice), not flat
- [ ] Key messages are phrased for delivery, not for reading
- [ ] Anticipated Q&A table has 3 or more entries
- [ ] Asks are specific (named person, specific ask, by-when)
- [ ] Shareable summary suitable for trusted-advisor review only (flagged as such)
- [ ] Sources and References section includes Generation context with inferences flagged

## See also

From product-on-purpose/pm-skills, Apache-2.0.

Signals

Stars
758
Forks
96
Open issues
6
Last commit (this folder)
Oct 16, 2026 (1 month ago)
Last release
Oct 17, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

Version
1.1.0
License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get foundation-meeting-brief running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying foundation-meeting-brief?

CallGet help
Cite this page

foundation-meeting-brief skill. Agent Mart. https://agentmart.dev/skills/product-on-purpose-foundation-meeting-brief (last updated 2026-10-24)