salla-briefing

name	salla-briefing
description	Daily PM briefing for Salla Platform PMs. Reads all knowledge files, checks sprint status, flags OKR risks, surfaces merchant feedback signals, and tells you exactly where to focus. Slash command: /salla-briefing

Salla Daily PM Briefing

You are generating the Salla PM's daily briefing. Scan everything, surface what matters today, and give a precise "start here" directive. Think like a senior Salla PM who has read every document and just needs to tell their junior what to focus on.

---

Step 1: Read Everything

Scan all knowledge files systematically. If a file or directory doesn't exist, skip silently.

1. knowledge/pm-context.md — pillar context, OKRs, team info
2. knowledge/okrs.md — OKRs and progress
3. knowledge/platform-pillars.md — platform context and metrics definitions
4. knowledge/launches/ — upcoming and recent launches
5. knowledge/decisions/ — pending or recently made decisions
6. knowledge/retros/ — open action items from retrospectives
7. knowledge/updates/ — most recent stakeholder update
8. knowledge/metrics/ — latest KPI reviews
9. knowledge/experiments/ — running experiments and pending results
10. knowledge/meetings/ — today's meetings and outstanding action items
11. knowledge/briefs/ — most recent brief (to track what's changed since then)
12. knowledge/feedback/ — most recent merchant feedback synthesis
13. knowledge/sprints/ — current sprint plan and blockers

---

Step 2: Check for MCP Integrations

Use these if available, skip gracefully if not:

Sprint & Backlog (Jira / Linear MCP)

• Current sprint: % complete, stories remaining, days left
• Blockers and at-risk tickets
• New tickets added since sprint start (scope creep check)
• Any tickets blocking other teams

Code Activity (GitHub MCP)

• PRs merged since last briefing (especially to production)
• PRs awaiting review that are blocking sprint delivery
• CI/CD failures or failed deployments
• Critical bug reports (P0/P1 issues opened)

Communication (Slack MCP)

• Merchant escalations or complaints in #cs-escalations or equivalent
• Key product channel discussions since yesterday
• Mentions or DMs needing response
• Any compliance/legal flags raised

If no MCP tools available, note which data is missing and show the briefing with what's available.

---

Step 3: Salla-Specific Analysis

Run this analysis before writing the briefing:

3a. OKR Trajectory

• For each active OKR, assess current trajectory based on available metric data
• Flag any KR that is at-risk or off-track
• Ask: "At the current rate, will we hit this KR by end of quarter?"
• Salla-specific note: OKRs touching GMV should be tracked against weekly GMV data if available

3b. Launch Readiness

• Any Salla features launching in the next 7 days?
• Check launch checklist for: ZATCA compliance sign-off, Arabic copy review, mobile QA, CS team briefed
• Any launch in the last 7 days with post-launch metrics to review?

3c. Merchant Signal Check

• Any spikes in CS tickets related to your pillar?
• Merchant NPS movement since last review?
• Any merchant escalations in the queue?
• Any feedback synthesis flagging a new theme?

3d. Compliance & Regulatory Flags

• Any pending ZATCA, SAMA, or PDPL items that need PM sign-off?
• Any regulatory deadlines approaching?

3e. Action Item Sweep

• Collect all open action items across meetings, retros, post-mortems
• Flag overdue items or items with no owner

3f. Experiment Status

• Any experiments with results ready for a decision?
• Any experiments running longer than their scheduled end date?

3g. Decision Queue

• Any decisions with revisit dates past due?
• Any pending decisions blocking work?

3h. Calendar Context

• Meetings today — what prep is needed?
• Any important internal deadlines today (planning, reviews, sign-offs)?
• Any Salla platform-wide events (all-hands, OKR review, planning cycle start)?

---

Step 4: Write the Briefing

Write to knowledge/briefs/brief-YYYY-MM-DD.md using today's date.

# Salla PM Briefing: [Date] | [Pillar Name]

## Start Here
[One sentence: the single most important thing to focus on today. Be specific — not "check metrics" but "Checkout CVR dropped 1.2pp last week and the root cause is still unknown — that's today's #1 job."]

---

## Priority Actions

### Must Do Today
1. **[Action]** — [Why it's urgent, what happens if not done, who else is waiting]
2. **[Action]** — [Why it's urgent]

### Should Do Today
1. **[Action]** — [Context]
2. **[Action]** — [Context]

### This Week
1. **[Action]** — [Deadline or event driving it]
2. **[Action]** — [Deadline or event driving it]

---

## OKR Status

| OKR | Progress | Trajectory | Flag |
|-----|----------|------------|------|
| [KR text] | [X%] | [On track / At risk / Off track] | [Note] |

## Sprint Status
- **Progress:** [X/Y stories, Z% complete]
- **Days remaining:** [N]
- **Blockers:** [Specific items]
- **At risk:** [Stories or items at risk of not completing]

## Merchant Signals
- **CS tickets (pillar):** [Volume trend, top complaint theme]
- **NPS:** [Latest score, trend direction]
- **Escalations:** [Any active, assigned owner]
- **Feedback themes:** [From latest feedback synthesis]

## Platform Activity
- **Shipped since last brief:** [Features, fixes, or deploys]
- **PRs needing review:** [Blocking or time-sensitive]
- **Experiment results ready:** [Headline result, recommendation pending]

## Launches
- **Upcoming (next 7 days):** [Feature name, date, readiness %]
- **Recent:** [Feature name, launch date, post-launch status]

## Metrics Snapshot

| Metric | Value | vs Last Period | Status |
|--------|-------|---------------|--------|
| GMV (pillar-relevant) | — | — | — |
| Active Merchants | — | — | — |
| [Pillar KPI 1] | — | — | — |
| [Pillar KPI 2] | — | — | — |

## Open Action Items

| Item | Source | Owner | Due | Status |
|------|--------|-------|-----|--------|
| [Item] | [Meeting/retro/etc.] | [Name] | [Date] | [Overdue / Due soon / On track] |

## Compliance & Regulatory
- [Any pending ZATCA, SAMA, or PDPL items needing PM input]
- [Upcoming regulatory deadlines]

## Decisions Needing Attention
- [Decision]: revisit date [date], context: [why it needs re-evaluation]

## Missing Context
[Data sources unavailable, knowledge gaps, items that need investigation]

---

Step 5: Present the Briefing

After writing the file, present a verbal summary to the PM. Lead with:

1. "Start here" — the single most important thing
2. "Must do today" — 2-3 time-sensitive actions with brief context
3. Flags — anything red (off-track OKRs, merchant escalations, compliance items, overdue actions)

Keep the verbal summary to 5-7 bullet points. Point to the full file for details.

End with:

Full briefing at knowledge/briefs/brief-[date].md. What do you want to dig into?

---

Salla Seasonal Context

When relevant, note:

• Ramadan: Merchant order volumes spike 2-4x. Shipping delays are common. CS tickets spike. Avoid major feature launches during Ramadan unless prepared.
• Eid periods: 3-5 days of very high volume, then sudden drop. Checkout stability is critical.
• White Friday (Black Friday): Largest GMV day of the year. Feature freeze 2 weeks before. Only P0 fixes shipped.
• Saudi National Day (Sep 23): Marketing campaign season. Many merchants run promotions — discount codes and checkout load are tested hard.
• 11.11: Growing in Saudi Arabia. Second-largest sales day after White Friday.

Flag if today is within 2 weeks of any of these events and the briefing should be adjusted accordingly.