---
name: quarterly-plan
description: "Build a Salla pillar quarterly plan from OKRs, roadmap, team capacity, and compliance calendar. Produces an execution plan with milestones, risks, and a readiness checklist. Slash command: /quarterly-plan"
---

# Quarterly Plan — Salla Platform

You build the execution plan for a Salla PM's quarter. This is the document that sits between the roadmap and the sprint — the "here's how we're actually going to hit the OKRs" plan.

---

## Initialization

1. Read `knowledge/pm-context.md` for pillar context and team info.
2. Read `knowledge/okrs.md` for the current quarter's OKRs.
3. Read `knowledge/roadmap/` for the roadmap to execute against.
4. Read `knowledge/team.md` for capacity and working agreements.
5. Read `knowledge/platform-pillars.md` for compliance calendar context.

---

## Step 1: Gather Quarter Context

Ask:
1. "Which quarter are we planning?" (Q1/Q2/Q3/Q4 + year)
2. "Are the OKRs finalized, or still being refined?"
3. "Are there any fixed events this quarter?" (Major launches, compliance deadlines, company all-hands, peak seasons)
4. "Any team changes this quarter?" (New hires, departures, sabbaticals)

---

## Salla Quarterly Calendar Awareness

Before planning, note which Salla events fall in this quarter:

| Event | Typical Quarter | PM Impact |
|-------|---------------|----------|
| White Friday | Q4 (Nov) | Feature freeze 2 weeks before. Only P0 fixes. |
| Eid Al-Fitr | Q1 or Q2 (varies by Hijri year) | High merchant demand. Avoid major launches. |
| Eid Al-Adha | Q2 or Q3 (varies) | Same as Eid Al-Fitr. |
| Saudi National Day | Q3 (Sep 23) | Marketing season. Merchant promotions heavy. |
| Ramadan | Q1 or Q2 (varies) | Avoid non-essential launches. CS volume spikes. |
| Salla Annual Planning | Q4 | OKR-setting for next year. Roadmap presentations. |
| 11.11 | Q4 (Nov 11) | Growing event. High checkout load. |

---

## Step 2: Generate the Quarterly Plan

```markdown
# Quarterly Plan: [Pillar] — Q[X] [Year]

**PM:** [Name]
**Quarter:** [Dates: Month D → Month D, Year]
**Status:** Planning / Active / Complete

---

## Quarter Goal

> [One sentence. What does success look like at the end of this quarter? Frame it in merchant terms.]

---

## OKRs This Quarter

| Objective | Key Result | Baseline | Target | Owner |
|-----------|-----------|---------|--------|-------|
| [Objective 1] | [KR 1.1] | [Value] | [Target] | [Name] |
| | [KR 1.2] | | | |
| [Objective 2] | [KR 2.1] | | | |

---

## Quarterly Calendar

[Map key milestones and events across the quarter]

```
Month 1                    Month 2                    Month 3
────────────────────────────────────────────────────────────────
Sprint 1    Sprint 2    Sprint 3    Sprint 4    Sprint 5    Sprint 6
│           │           │           │           │           │
├── [Feature A launch]
│           ├── [ZATCA review for Feature B — submit]
│           │           ├── [Feature B launch]
│           │           │           ├── [Eid / seasonal event — freeze]
│           │           │           │           ├── [OKR mid-quarter review]
│           │           │           │           │           ├── [Q-end metrics review]
```

---

## Sprint-by-Sprint Plan

### Sprint 1 ([Date range])
**Goal:** [What ships or gets done]
**Key items:**
- [Item] — [Owner] — [OKR alignment]
- [Item]
**Compliance items to initiate:**
- [ZATCA/SAMA submission for [feature] — must submit this sprint for [target launch sprint]]

### Sprint 2 ([Date range])
**Goal:** [What ships or gets done]
**Key items:**
- [Item]
**Compliance sign-offs expected:**
- [Compliance review return expected for [feature]]

[Continue for all sprints]

---

## Milestone Tracker

| Milestone | Target date | Owner | Dependencies | Status |
|-----------|------------|-------|-------------|--------|
| [Feature A to staging] | [Date] | [Name] | [Dependency] | ⬜ |
| [ZATCA sign-off for Feature B] | [Date] | Compliance | Submit by [date] | ⬜ |
| [Feature B launch] | [Date] | [Name] | ZATCA ✅ | ⬜ |
| [OKR mid-quarter review] | [Date] | PM | Metrics data | ⬜ |
| [Arabic copy reviewed for Feature C] | [Date] | Content | Design finalized | ⬜ |

---

## Capacity Summary

| Sprint | Available pts | Committed pts | Buffer |
|--------|--------------|--------------|--------|
| Sprint 1 | [X] | [Y] | [X-Y pts] |
| Sprint 2 | [X] | [Y] | |
| Sprint 3 | [X] | [Y] | |
| Sprint 4 | [X] | [Y] | |
| Sprint 5 | [X] | [Y] | |
| Sprint 6 | [X] | [Y] | |
| **Quarter total** | [X] | [Y] | |

**Team notes:**
- [Any OOO or reduced capacity periods]
- [New team member ramping — reduced velocity expected in Sprints 1-2]

---

## Compliance Calendar

[Compliance items must be tracked proactively — these are the most common reason Salla timelines slip]

| Feature | Compliance needed | Submit by | Expected return | Launch target |
|---------|-----------------|----------|----------------|--------------|
| [Feature] | ZATCA | [Date] | [Date] | [Date] |
| [Feature] | SAMA | [Date] | [Date] | [Date] |

**Action:** PM must initiate all compliance submissions in Sprint 1. Don't wait.

---

## Cross-Pillar Dependencies

| We need from... | What | By when | Status |
|----------------|------|---------|--------|
| [Pillar] | [Specific API/data/feature] | [Sprint/Date] | [Confirmed / Pending confirmation] |

| [Pillar] needs from us | What | By when | Status |
|------------------------|------|---------|--------|
| [Feature/API] | [Description] | [Sprint/Date] | [In plan / Not committed] |

**Action:** Confirm all cross-pillar dependencies in Sprint 1 planning.

---

## Quarter Risks

| Risk | Likelihood | Impact | Mitigation | Owner |
|------|-----------|--------|-----------|-------|
| [Seasonal event delays key launch] | [High if [event] falls in Q] | High | [Launch before or after event] | PM |
| [Compliance review takes longer than expected] | Medium | High | [Submit early, have backup plan] | PM + Compliance |
| [Engineering capacity reduced by unplanned work] | Medium | Medium | [Protect 20% buffer capacity] | Engineering Lead |
| [Cross-pillar dependency slips] | Low | High | [Weekly sync with [pillar] PM] | PM |

---

## Arabic/Mobile Commitment

[Explicit tracking of Arabic and mobile work — these should not be cut when sprints get tight]

| Feature | Arabic copy needed | Mobile QA scope | Risk if cut |
|---------|------------------|----------------|------------|
| [Feature] | [Yes/No] | [Light/Heavy] | [Merchant impact] |

**Arabic copy lead time:** Allow at least [X days] for content team to produce quality Arabic copy.

---

## What Success Looks Like

At the end of Q[X], we will know this quarter was successful if:

1. ✅ [KR 1.1 target hit]
2. ✅ [KR 1.2 target hit]
3. ✅ [KR 2.1 target hit]
4. ✅ [Feature A launched and adopted by [N] merchants]
5. ✅ [No critical merchant issues caused by our launches]

---

## Quarter Readiness Checklist

- [ ] OKRs finalized and approved by CPO
- [ ] Roadmap confirmed with engineering team
- [ ] Compliance submissions scheduled in Sprint 1
- [ ] Cross-pillar dependencies confirmed with peer PMs
- [ ] Team capacity confirmed (OOO, new hires, known events)
- [ ] Seasonal events noted — launch windows planned around them
- [ ] Arabic copy owner confirmed for all UI features
- [ ] Mobile QA plan confirmed
```

Write to: `knowledge/roadmap/quarterly-plan-[pillar]-Q[X]-[year].md`