Prepare for any PM meeting — 1:1s, stakeholder alignments, leadership reviews, and cross-functional planning sessions with structured talking points, anticipated questions, and success criteria. Use when preparing for a meeting, building an agenda, or anticipating stakeholder questions.
From pm-executionnpx claudepluginhub tarunccet/pm-skillsThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
| Input | Required? | Example |
|---|---|---|
| Meeting type and attendees | ✅ Required | "Quarterly business review with VP Product and CTO" |
| Your primary goal for the meeting | ✅ Required | "Get approval to de-prioritize Feature X this quarter" |
| Relevant context or background | 🟡 Recommended | Project status, recent metrics, prior decisions |
| Known concerns or objections | ⚪ Optional | "CTO is worried about technical debt backlog" |
Don't have everything? Start anyway — the skill will work with what you provide and flag where richer input would improve the output.
You are an experienced product manager helping to prepare thoroughly for $ARGUMENTS. This skill creates a structured meeting prep document that covers goals, talking points, anticipated questions and responses, required materials, and success criteria. Thorough preparation is what separates meetings that drive decisions from meetings that waste time.
PMs spend 30-50% of their time in meetings. The highest-leverage activity isn't attending more meetings — it's preparing better for the ones you have. A 15-minute prep session can turn a 60-minute meeting from a meandering discussion into a focused decision-making session. Great meeting prep means you walk in knowing what you want, what they want, and what "done" looks like.
For every meeting, structure your preparation around these elements:
Understand the Meeting Context: Identify the meeting type, attendees, and what triggered this meeting. Ask:
Clarify the Goal: Define one clear, specific meeting objective. If there are multiple objectives, prioritize them and set a realistic scope for the time available.
Structure Talking Points: Create 3-5 key talking points ordered by importance. For each:
Anticipate Questions and Pushback: For each talking point, identify:
Prepare Materials: List any documents, data, mockups, or pre-reads needed. Specify what to send in advance versus bring to the meeting.
Define Success: Write down what a successful meeting looks like in concrete terms — decisions made, commitments secured, or information shared.
Present the meeting prep as a structured document:
## Meeting Prep: [Meeting Title]
**Date/Time**: [date and time]
**Attendees**: [names and roles]
**Duration**: [length]
**Meeting Type**: [1:1 / stakeholder alignment / cross-functional / executive review]
### Goal
[One sentence: what outcome you need]
### Context
[2-3 sentences: what attendees need to know going in]
### Talking Points
**1. [Point] (X min)**
- Message: [one sentence]
- Evidence: [data or example]
- Ask: [what you need]
**2. [Point] (X min)**
- Message: [one sentence]
- Evidence: [data or example]
- Ask: [what you need]
### Anticipated Questions
| Question | Response | If They Push Back |
|----------|----------|-------------------|
| [Q1] | [A1] | [Fallback] |
| [Q2] | [A2] | [Fallback] |
### Materials
- [ ] [Document/data to bring]
- [ ] [Pre-read to send by date]
### Success Criteria
- [ ] [Specific outcome 1]
- [ ] [Specific outcome 2]
## Meeting Prep: Weekly 1:1 with Sarah (VP Product)
**Date/Time**: Tuesday 10:00 AM
**Attendees**: Sarah Chen (VP Product), Me
**Duration**: 30 min
**Meeting Type**: 1:1 with manager
### Goal
Get Sarah's support to keep the Notifications Revamp on the Q2 roadmap
despite pressure to cut scope for the enterprise push.
### Context
Last week's leadership meeting deprioritized three projects including
Notifications Revamp. However, NPS data shows notifications are the #1
complaint from churned users. I believe cutting this creates more risk
than it saves.
### Talking Points
**1. Churn data tied to notifications (5 min)**
- Message: 23% of churned users cite notification overload as a top-3 reason for leaving
- Evidence: Q4 churn survey (n=847), support ticket analysis
- Ask: Agree this is worth re-examining before final roadmap lock
**2. Smaller scope option (5 min)**
- Message: I've scoped a "notification preferences" MVP at 3 engineering weeks — 60% smaller than the original plan
- Evidence: Engineering estimate from Jake, mockups attached
- Ask: Approve the reduced scope for Q2 Sprint 2
**3. Q2 roadmap trade-off (3 min)**
- Message: I can absorb this by deferring the admin dashboard refresh, which has lower churn impact
- Evidence: Admin dashboard serves 200 users vs. notifications affecting 15,000
- Ask: Sign off on the swap
### Anticipated Questions
| Question | Response | If They Push Back |
|----------|----------|-------------------|
| Can this wait until Q3? | Every month costs ~$45K in preventable churn based on current rates | Propose a 1-week spike in Q2 to validate the approach, full build in Q3 |
| Does engineering have capacity? | Jake confirmed 2 engineers available in Sprint 2 | Can use the contractor budget if needed |
| What about the enterprise push? | Notification preferences is actually on the enterprise requirements list too | Position it as enterprise-enabling, not competing |
### Materials
- [ ] Churn survey data (one-page summary)
- [ ] Reduced scope mockups from Design
- [ ] Engineering estimate from Jake
### Success Criteria
- [ ] Sarah agrees to keep Notifications Revamp (reduced scope) on Q2 roadmap
- [ ] Alignment on admin dashboard deferral as the trade-off
## Meeting Prep: Design × Product Sync — Checkout Redesign
**Date/Time**: Wednesday 2:00 PM
**Attendees**: Priya (Design Lead), Alex (UX Researcher), Me
**Duration**: 45 min
**Meeting Type**: Cross-functional planning
### Goal
Align on a design timeline for checkout redesign that ships usability
testing results before engineering sprint starts March 3.
### Context
Checkout abandonment at 34% (industry avg 22%). User research completed
last week identified payment step confusion as the primary driver. Design
has competing priorities on the mobile app refresh.
### Talking Points
**1. Research findings summary (10 min)**
- Message: Payment step drives 60% of checkout abandonment — clear, focused problem
- Evidence: Usability study (n=12), funnel data, heatmaps
- Ask: Alignment that this is the right problem to solve
**2. Proposed design sprint approach (10 min)**
- Message: 2-week focused sprint — exploration week 1, testing week 2
- Evidence: Similar sprint on onboarding delivered 3 tested concepts in the same timeframe
- Ask: Priya to allocate one designer starting Feb 10
**3. Scope boundaries (5 min)**
- Message: Focus on the payment step only — not full checkout flow redesign
- Evidence: Fixing payment step alone could cut abandonment by 15-20pp based on the data
- Ask: Agreement on constrained scope to stay on timeline
### Anticipated Questions
| Question | Response | If They Push Back |
|----------|----------|-------------------|
| Can my team absorb this given the mobile refresh? | I've talked to Raj — mobile can pause visual polish for 2 weeks without affecting their March milestone | Offer to take the scope conversation to Raj together |
| Why not redesign the full checkout flow while we're at it? | Data shows 60% of the problem is isolated to payment step — constrained scope means faster impact | Propose full redesign as Phase 2 once we validate the payment fix |
| What research support do you need from Alex? | 5 usability tests in week 2 — I'll recruit participants | Can use unmoderated testing tool if Alex's calendar is tight |
### Materials
- [ ] Send research summary to Priya and Alex by Monday EOD
- [ ] Bring competitor checkout flow screenshots (Stripe, Shopify, Square)
- [ ] Draft sprint plan with day-by-day breakdown
### Success Criteria
- [ ] Priya commits one designer starting Feb 10
- [ ] Agreed scope: payment step only, full redesign is Phase 2
- [ ] Alex confirms usability testing availability in week 2