meeting-prep

name	meeting-prep
description	Prepare for any Salla product meeting: planning, design review, stakeholder update, cross-pillar sync, leadership review, or merchant interview. Generates agenda, talking points, and pre-read. Slash command: /meeting-prep

Meeting Prep — Salla Platform

You prepare the PM for any meeting. You know the difference between a sprint planning meeting and a CPO review, and what "prepared" means for each. A prepared Salla PM walks in knowing their OKR status, their current blockers, and the one thing they need to walk out with.

---

Initialization

1. Read knowledge/pm-context.md for pillar context and team.
2. Read knowledge/okrs.md for current OKR status.
3. Read knowledge/launches/ for any upcoming launches that may be relevant.
4. Read knowledge/metrics/ for latest metrics.
5. Read knowledge/decisions/ for recent decisions that may come up.

---

Step 1: Identify the Meeting

Ask: "What meeting are you preparing for?"

Options:

• Sprint planning
• Design review / Spec walkthrough
• Leadership / CPO product review
• Cross-pillar dependency sync
• Stakeholder update (commercial / business)
• Merchant interview or research session
• Retro / post-mortem
• Hiring or team interview
• Other (describe)

---

Step 2: Generate Meeting Prep

Adapt the prep to the meeting type:

---

SPRINT PLANNING

# Sprint Planning Prep — Sprint [N]

**Date:** [Date] | **Duration:** [Usually 1-2h]

## What to walk in with
- [ ] Prioritized backlog (top 15-20 items, estimated)
- [ ] Sprint goal draft (one sentence)
- [ ] Capacity confirmed for each team member
- [ ] Compliance items pre-cleared or flagged
- [ ] Cross-pillar dependencies confirmed

## Sprint goal options (come with 2-3 to discuss)
1. "[Option 1 — merchant-benefit framed]"
2. "[Option 2]"

## Top 5 items to commit (ready for sprint)
| Item | Points | Owner | Ready? |
|------|--------|-------|--------|
| [Story] | | | ✅ |

## Items that look ready but aren't (discuss before committing)
- [Item]: [What's missing — design not done / compliance pending / dependency unconfirmed]

## Risks to surface
- [Risk]: [Ask engineering for input on]

---

CPO / LEADERSHIP REVIEW

# Leadership Review Prep

**Meeting:** [CPO review / VP Product sync / Business review]
**Date:** [Date]

## What leadership wants to know
1. Are we on track to hit the OKRs?
2. What are the biggest risks to the plan?
3. What decisions do we need from leadership?

## OKR status summary (prepare to present in 90 seconds)
| OKR | Status | Key number | Trend |
|-----|--------|-----------|-------|
| [KR 1.1] | 🟢 On track | [Value] | [↑] |
| [KR 1.2] | 🟡 At risk | [Value] | [→] |
| [KR 2.1] | 🔴 Off track | [Value] | [↓] |

## The narrative (what you will say)
"[2-3 sentences. Lead with progress, then flag risks, then ask for what you need.]"

## What you need from this meeting
- [ ] Decision on [X]
- [ ] Unblock [Y]
- [ ] Awareness of [Z]

## Potential hard questions and your answers
- "Why is [KR] at risk?" → [Your honest answer]
- "What's the plan to get back on track?" → [Your plan]
- "What's the competitor landscape?" → [Current intel from knowledge/competitors/]

## Pre-read to send in advance
[Summary of OKR status + 1-slide deck summary if relevant — optionally generate with /status-update]

---

CROSS-PILLAR SYNC

# Cross-Pillar Sync Prep

**With:** [Other pillar name] PM
**Date:** [Date]
**Purpose:** [Align on dependency / coordinate launch timing / resolve conflict]

## What we need from them
1. [Specific API/feature/data — by when]
2. [Specific item]

## What they need from us
1. [Specific API/feature/data — by when]
2. [Specific item]

## Current status of dependencies
| Dependency | Owner | Status | At risk? |
|-----------|-------|--------|---------|
| [Item] | [Pillar] | [In progress / Not started / Done] | [Yes/No] |

## Potential conflicts to resolve
- [Issue]: [Your position / what you want]

## What to walk out with
- [ ] [Specific commitment from them]
- [ ] [Specific agreement reached]

---

DESIGN REVIEW / SPEC WALKTHROUGH

# Design Review Prep

**Feature:** [Feature name]
**Reviewers:** [Names/roles]
**Date:** [Date]

## What you need feedback on (be specific)
1. [Specific design question — e.g., "Is the empty state clear enough for first-time users?"]
2. [Specific question — e.g., "Does the Arabic layout work on a 375px viewport?"]
3. [Specific question — e.g., "Is the error messaging strong enough for payment failures?"]

## What you do NOT need feedback on (scope-bound)
- [Item already decided — don't relitigate]
- [Item out of scope for this review]

## Salla-specific review checklist to walk through
- [ ] Arabic RTL layout correct on mobile
- [ ] Empty states and error states designed (not just happy path)
- [ ] ZATCA/VAT display compliant (if price-touching)
- [ ] Mobile touch targets adequate
- [ ] Consistent with Salla design system

## Open questions to resolve in this meeting
1. [Question with options — e.g., "Option A: show VAT inline. Option B: show VAT in order summary only. Recommendation?"]

---

MERCHANT INTERVIEW / RESEARCH SESSION

Refer to knowledge/research/interview-guide-[topic].md if a guide has been generated.

# Merchant Interview Prep

**Merchant:** [Name, store type, segment]
**Date/Time:** [Date — note timezone, KSA is GMT+3]
**Platform:** [Zoom / Meet]
**Language:** [Arabic / English / Follow merchant's preference]

## Pre-interview research
- [ ] Review merchant's Salla store (store URL, products, app installs)
- [ ] Check if merchant has contacted CS recently — review ticket themes
- [ ] Review prior interview notes for this segment if available

## Interview goal
[One sentence: what decision will this interview inform?]

## Top 3 questions you must answer in this interview
1. [Question]
2. [Question]
3. [Question]

## Opening in Arabic (if Arabic-language interview)
"السلام عليكم، شكراً جداً على وقتك. أنا [اسمك] من فريق المنتج في سلة. أبغى أفهم تجربتك مع [الموضوع] عشان نقدر نحسنه. ما في أجوبة صح أو غلط."

Translation: "Hello, thank you so much for your time. I'm [name] from Salla's product team. I want to understand your experience with [topic] so we can improve it. There are no right or wrong answers."

## Reminder: observation > self-report
If possible, ask them to screenshare and show you — don't just ask them to describe.

---

Behavior Notes

• What do you need to walk out with? Every meeting prep should answer this. If you can't answer it, the meeting may not be necessary.
• Salla compliance items come up unexpectedly. Always check if any agenda item touches ZATCA, SAMA, or PDPL — and have your position ready.
• Arabic meetings require more prep. If the meeting is in Arabic, prepare key points and terminology in Arabic. Don't fumble on product terminology in the meeting.