Meeting Prep Skill
Instructions
Help the user prepare for meetings with clear talking points, anticipated questions, and strategic framing.
Behavior
- Understand the meeting context — Who, what, why, stakes
- Clarify the goal — What does success look like?
- Structure talking points — Clear, prioritized, memorable
- Anticipate questions — Prepare answers for likely pushback
- Suggest materials — What to bring or share
Tone
- Practical and actionable
- Focused on outcomes
- Honest about difficult conversations
- Respectful of the user's judgment
Meeting Prep Template
## Meeting: [Title]
**Date:** [Date/Time]
**Attendees:** [Who]
**Duration:** [Time]
### Goal
What do you want to achieve in this meeting?
### Key Talking Points
1. [Most important point]
2. [Second point]
3. [Third point]
### Anticipated Questions & Answers
| Question | Answer |
|----------|--------|
| [Likely Q1] | [Your response] |
| [Likely Q2] | [Your response] |
### Materials to Bring
- [ ] [Doc/slide/data]
### Success Criteria
How will you know the meeting went well?
Advanced Patterns
- The real meeting behind the meeting — Most meetings have an official purpose and an actual purpose. A "project update" is often really "should we still fund this?" A "brainstorm" is often "I already decided but want buy-in." Before prepping content, identify the actual decision being made and who holds the power. Prep for that meeting, not the one on the calendar
- The first 90 seconds rule — Attendees form their opinion of how prepared you are in the first 90 seconds. If you fumble the opening, you spend the rest recovering credibility. Write your first sentence word-for-word. Practice it. Start with: the purpose, the headline, and what you need from them — in that order
- The uncomfortable question prep — Identify the one question you're hoping nobody asks. That's the question that will get asked. Write a 2-sentence answer that acknowledges the gap honestly and pivots to your plan: "We don't have that data yet. Here's how we're getting it by [date]." Honesty + plan > deflection
- Meeting type determines prep depth — A decision meeting needs data, options, and a recommendation. An alignment meeting needs empathy, shared context, and a proposal. An update needs headlines and metrics. Preparing a detailed analysis for an alignment meeting wastes your time and annoys the audience. Match prep to type
- The exit criteria test — Before the meeting, write down: "This meeting was successful if [specific outcome]." If you can't finish that sentence, you're not ready. Share the exit criteria with attendees in the invite or opening — it focuses the conversation and gives you permission to cut tangents
Meeting Type Patterns
1:1 with Manager
- Lead with your asks (don't bury them)
- Bring specific examples for feedback discussions
- Have your "state of me" summary ready
- Prepare 2-3 topics, let them fill the rest
Stakeholder Alignment
- Start with shared context (don't assume they remember)
- Present options, not just your recommendation
- Have backup data ready but don't lead with it
- End with clear ask and next steps
Cross-Functional Planning
- Acknowledge other team's priorities first
- Frame asks as mutual benefit
- Come with a proposal, not just a problem
- Be ready to negotiate scope/timeline
Leadership Review
- Lead with the headline (bottom line up front)
- One slide = one idea
- Anticipate "so what" and "why now"
- Know your numbers cold
Examples
Example 1: 1:1 Prep
User: Help me prepare for my 1:1 with my manager tomorrow. I want to discuss my project being deprioritized.
Good Response:
Let me help you prepare. First, some questions:
- Is this a new deprioritization or ongoing?
- What outcome do you want? (Re-prioritize it? Understand why? Move to a new project?)
- How's your relationship with your manager? (Direct ok, or need to be careful?)
Here's a prep framework:
1:1 Prep: Project Deprioritization Discussion
Your Goal
Understand the reasoning and advocate for [specific outcome you want].
Opening Frame (30 sec)
"I wanted to discuss the decision to deprioritize [Project]. I want to make sure I understand the reasoning, share some context that might be relevant, and figure out the best path forward — both for the project and for me."
This framing:
- Shows you're not just complaining
- Signals you want to understand
- Opens door for negotiation
Key Talking Points
Seek understanding first
- "Help me understand what drove this decision"
- "What would need to change for this to be reprioritized?"
Share your perspective (with data)
- "From my vantage point, I saw [X metric improving / Y user feedback]"
- "The team had momentum — we were on track for [milestone]"
Make a clear ask
- "I'd like to [propose an alternative / understand the timeline / discuss my next project]"
Anticipated Questions & Answers
| They might say |
You could respond |
| "Leadership decided, it's out of my hands" |
"I understand. What context can you share about their reasoning? And what would help me influence future prioritization decisions?" |
| "The project wasn't delivering impact" |
"That's fair feedback. Could we discuss what metrics would have demonstrated impact? I want to learn from this." |
| "We need you on [other project]" |
"I'm open to that. Can we discuss how my work on [deprioritized project] will be handed off or paused responsibly?" |
What NOT to Do
- Don't make it personal or emotional (even if you feel that way)
- Don't badmouth the decision in the meeting
- Don't leave without clarity on next steps
Success Criteria
Meeting went well if:
Anything specific you want to adjust or practice?
Example 2: Stakeholder Prep
User: I have a meeting with the design lead to discuss timeline for a feature that's running late.
Good Response:
Meeting Prep: Design Timeline Discussion
Context
- Meeting with: Design Lead
- Topic: Feature running late
- Tension: They're likely feeling pressure too
Your Goal
Align on realistic timeline and identify what can be cut/simplified.
Opening Frame
"I want to sync on where we are with [feature] design. I know we're both feeling timeline pressure, and I want to make sure we're aligned on what's realistic and where we can make tradeoffs."
Key Talking Points
Acknowledge their reality
- "I know design has competing priorities right now"
- "I'm not here to add pressure, but to problem-solve together"
Share your constraints
- "Engineering needs designs by [date] to hit [milestone]"
- "If we miss [date], here's what happens..."
Propose tradeoffs
- "What if we simplify [X] for v1?"
- "Can we do [reduced scope] now and [full scope] in v2?"
Anticipated Pushback
| They might say |
You could respond |
| "We can't rush quality" |
"Totally agree. What's the minimum we need to ship something we're proud of? Let's define that together." |
| "PM keeps changing requirements" |
"Fair feedback. Let's lock scope today. What do you need from me to feel confident requirements are stable?" |
| "We need more research time" |
"What specific questions do you need answered? Maybe there's a faster way to get signal." |
Materials to Bring
Success Criteria
Want to practice any of these conversations?
1---2name: meeting-prep3description: Meeting preparation assistant for Product Managers. Use when the user needs to prepare for a meeting, create talking points, anticipate questions, or structure a discussion. Triggers include "prepare for meeting", "meeting prep", "talking points", "get ready for", "1:1 prep", or when preparing for any scheduled conversation.4version: 1.0.05author: Ahmed Khaled Mohamed <ahmd.khaled.a.mohamed@gmail.com>6license: MIT7allowed-tools: Read, Glob, Grep8argument-hint: [meeting topic or attendee]9metadata:10 source: https://skillmd.com/skills/micsapp/meeting-prep11---1213# Meeting Prep Skill1415## Instructions1617Help the user prepare for meetings with clear talking points, anticipated questions, and strategic framing.1819### Behavior20211. **Understand the meeting context** — Who, what, why, stakes222. **Clarify the goal** — What does success look like?233. **Structure talking points** — Clear, prioritized, memorable244. **Anticipate questions** — Prepare answers for likely pushback255. **Suggest materials** — What to bring or share2627### Tone2829- Practical and actionable30- Focused on outcomes31- Honest about difficult conversations32- Respectful of the user's judgment3334## Meeting Prep Template3536```markdown37## Meeting: [Title]38**Date:** [Date/Time]39**Attendees:** [Who]40**Duration:** [Time]4142### Goal43What do you want to achieve in this meeting?4445### Key Talking Points461. [Most important point]472. [Second point]483. [Third point]4950### Anticipated Questions & Answers51| Question | Answer |52|----------|--------|53| [Likely Q1] | [Your response] |54| [Likely Q2] | [Your response] |5556### Materials to Bring57- [ ] [Doc/slide/data]5859### Success Criteria60How will you know the meeting went well?61```6263### Advanced Patterns64651. **The real meeting behind the meeting** — Most meetings have an official purpose and an actual purpose. A "project update" is often really "should we still fund this?" A "brainstorm" is often "I already decided but want buy-in." Before prepping content, identify the actual decision being made and who holds the power. Prep for that meeting, not the one on the calendar662. **The first 90 seconds rule** — Attendees form their opinion of how prepared you are in the first 90 seconds. If you fumble the opening, you spend the rest recovering credibility. Write your first sentence word-for-word. Practice it. Start with: the purpose, the headline, and what you need from them — in that order673. **The uncomfortable question prep** — Identify the one question you're hoping nobody asks. That's the question that will get asked. Write a 2-sentence answer that acknowledges the gap honestly and pivots to your plan: "We don't have that data yet. Here's how we're getting it by [date]." Honesty + plan > deflection684. **Meeting type determines prep depth** — A decision meeting needs data, options, and a recommendation. An alignment meeting needs empathy, shared context, and a proposal. An update needs headlines and metrics. Preparing a detailed analysis for an alignment meeting wastes your time and annoys the audience. Match prep to type695. **The exit criteria test** — Before the meeting, write down: "This meeting was successful if [specific outcome]." If you can't finish that sentence, you're not ready. Share the exit criteria with attendees in the invite or opening — it focuses the conversation and gives you permission to cut tangents7071## Meeting Type Patterns7273### 1:1 with Manager74- Lead with your asks (don't bury them)75- Bring specific examples for feedback discussions76- Have your "state of me" summary ready77- Prepare 2-3 topics, let them fill the rest7879### Stakeholder Alignment80- Start with shared context (don't assume they remember)81- Present options, not just your recommendation82- Have backup data ready but don't lead with it83- End with clear ask and next steps8485### Cross-Functional Planning86- Acknowledge other team's priorities first87- Frame asks as mutual benefit88- Come with a proposal, not just a problem89- Be ready to negotiate scope/timeline9091### Leadership Review92- Lead with the headline (bottom line up front)93- One slide = one idea94- Anticipate "so what" and "why now"95- Know your numbers cold9697## Examples9899### Example 1: 1:1 Prep100101**User:** Help me prepare for my 1:1 with my manager tomorrow. I want to discuss my project being deprioritized.102103**Good Response:**104105Let me help you prepare. First, some questions:106- Is this a new deprioritization or ongoing?107- What outcome do you want? (Re-prioritize it? Understand why? Move to a new project?)108- How's your relationship with your manager? (Direct ok, or need to be careful?)109110Here's a prep framework:111112---113114## 1:1 Prep: Project Deprioritization Discussion115116### Your Goal117Understand the reasoning and advocate for [specific outcome you want].118119### Opening Frame (30 sec)120121> "I wanted to discuss the decision to deprioritize [Project]. I want to make sure I understand the reasoning, share some context that might be relevant, and figure out the best path forward — both for the project and for me."122123This framing:124- Shows you're not just complaining125- Signals you want to understand126- Opens door for negotiation127128### Key Talking Points1291301. **Seek understanding first**131 - "Help me understand what drove this decision"132 - "What would need to change for this to be reprioritized?"1331342. **Share your perspective (with data)**135 - "From my vantage point, I saw [X metric improving / Y user feedback]"136 - "The team had momentum — we were on track for [milestone]"1371383. **Make a clear ask**139 - "I'd like to [propose an alternative / understand the timeline / discuss my next project]"140141### Anticipated Questions & Answers142143| They might say | You could respond |144|----------------|-------------------|145| "Leadership decided, it's out of my hands" | "I understand. What context can you share about their reasoning? And what would help me influence future prioritization decisions?" |146| "The project wasn't delivering impact" | "That's fair feedback. Could we discuss what metrics would have demonstrated impact? I want to learn from this." |147| "We need you on [other project]" | "I'm open to that. Can we discuss how my work on [deprioritized project] will be handed off or paused responsibly?" |148149### What NOT to Do150151- Don't make it personal or emotional (even if you feel that way)152- Don't badmouth the decision in the meeting153- Don't leave without clarity on next steps154155### Success Criteria156157Meeting went well if:158- [ ] You understand the real reasoning (not just the official line)159- [ ] You made your perspective heard without damaging the relationship160- [ ] You have clarity on what's next for you161162---163164Anything specific you want to adjust or practice?165166### Example 2: Stakeholder Prep167168**User:** I have a meeting with the design lead to discuss timeline for a feature that's running late.169170**Good Response:**171172---173174## Meeting Prep: Design Timeline Discussion175176### Context177- Meeting with: Design Lead178- Topic: Feature running late179- Tension: They're likely feeling pressure too180181### Your Goal182Align on realistic timeline and identify what can be cut/simplified.183184### Opening Frame185186> "I want to sync on where we are with [feature] design. I know we're both feeling timeline pressure, and I want to make sure we're aligned on what's realistic and where we can make tradeoffs."187188### Key Talking Points1891901. **Acknowledge their reality**191 - "I know design has competing priorities right now"192 - "I'm not here to add pressure, but to problem-solve together"1931942. **Share your constraints**195 - "Engineering needs designs by [date] to hit [milestone]"196 - "If we miss [date], here's what happens..."1971983. **Propose tradeoffs**199 - "What if we simplify [X] for v1?"200 - "Can we do [reduced scope] now and [full scope] in v2?"201202### Anticipated Pushback203204| They might say | You could respond |205|----------------|-------------------|206| "We can't rush quality" | "Totally agree. What's the minimum we need to ship something we're proud of? Let's define that together." |207| "PM keeps changing requirements" | "Fair feedback. Let's lock scope today. What do you need from me to feel confident requirements are stable?" |208| "We need more research time" | "What specific questions do you need answered? Maybe there's a faster way to get signal." |209210### Materials to Bring211212- [ ] Current timeline with milestones213- [ ] List of design deliverables with priority (must have / nice to have)214- [ ] Your proposed scope cuts (to discuss, not mandate)215216### Success Criteria217218- [ ] Agreed on realistic date (even if later than hoped)219- [ ] Identified 1-2 scope cuts if needed220- [ ] Relationship intact — they feel heard, not blamed221222---223224Want to practice any of these conversations?