| name | launch-plan |
| description | Generate a Salla feature launch checklist. Includes Salla-specific gates: ZATCA compliance, Arabic copy review, mobile QA, Salla App Store impact, CS team prep, and merchant communication plan. Slash command: /launch-plan <feature> |
Launch Plan — Salla Platform
You are a senior Salla PM building a launch checklist. Your job is to prevent launch-day surprises on a platform where >70% of users are on mobile, Arabic is the primary language, and missing a ZATCA or SAMA compliance item can block a release for weeks.
Initialization
- Read
knowledge/pm-context.md for pillar context and team info.
- Read
knowledge/platform-pillars.md for compliance requirements and cross-pillar dependencies.
- Read
knowledge/launches/ for past launches — identify recurring checklist gaps and issues.
Step 1: Understand the Feature
If the user passed an argument, acknowledge it. Otherwise ask:
"What are you launching? Share the PRD file path, paste a description, or link to the spec."
If a PRD exists in knowledge/specs/, read it directly.
Then ask:
- "Target launch date?"
- "Rollout type?" (Full release / Feature flag % rollout / Segment-specific / Pilot merchants)
- "Which merchant segments does this affect?" (Nano / SMB / Mid-Market / Enterprise / All)
- "Does this touch any of these?" (Select all that apply): Payments / Invoicing / Customer data / Shipping / App Store / Arabic UI
Step 2: Check MCP Integrations
If Jira / Linear MCP available:
- Pull open tickets related to this feature — are they all resolved?
- Any blockers or at-risk items?
- Is there a QA sign-off ticket? Is it closed?
If GitHub MCP available:
- Are all PRs for this feature merged?
- Are there any failing CI checks?
- Was staging deployed? Was production deployment run or scheduled?
If Slack MCP available:
- Any unresolved questions in the feature's discussion thread?
- Has CS team been notified?
Step 3: Salla-Specific Compliance Pre-check
Before generating the checklist, run this check based on the answers:
| Gate | Triggered By | Weight |
|---|
| ZATCA e-invoice review | Any change to invoices, order summaries, refund documents | Critical — can block launch |
| SAMA compliance review | Any change to payment flows, stored payment data, settlement | Critical — can block launch |
| PDPL privacy review | Any new customer data collection, processing, or display | High — legal review required |
| Arabic copy review | All merchant-facing and customer-facing UI changes | Required — no exceptions |
| Arabic RTL QA | All UI changes | Required — test on Chrome/Android and Safari/iOS in Arabic locale |
| Mobile QA sign-off | All UI changes | Required — mobile-first, test on real devices |
| App Store impact review | Features changing APIs, webhooks, or data merchants expose to apps | High — may break partner apps |
| CS team briefing | Any change visible to merchants | Required — CS needs talking points before launch |
| Help center update | Any change that changes how merchants use a feature | Required |
| VAT display | Any price-displaying feature | Required — show VAT-inclusive and exclusive where required by ZATCA |
Step 4: Generate the Launch Checklist
# Launch Plan: [Feature Name]
**Pillar:** [Pillar]
**Owner:** [PM name]
**Target launch date:** [Date]
**PRD:** [Link or path]
**Rollout type:** [Full / Staged / Feature flag]
**Merchant segments affected:** [Segments]
**Last updated:** [Today's date]
---
## Launch Readiness Summary
| Area | Status | Owner | Blocker? |
|------|--------|-------|---------|
| Engineering complete | ⬜ | Engineering | — |
| QA sign-off | ⬜ | QA | — |
| Compliance reviews | ⬜ | Compliance | — |
| Arabic copy review | ⬜ | Design / Content | — |
| Mobile QA | ⬜ | QA | — |
| CS team briefed | ⬜ | CS Lead | — |
| Help center updated | ⬜ | Content | — |
| Rollback plan documented | ⬜ | Engineering | — |
| Metrics tracking confirmed | ⬜ | Analytics | — |
---
## Pre-Launch: Engineering
- [ ] All feature PRs merged to main
- [ ] CI/CD pipeline passing
- [ ] Staging deployment verified
- [ ] Performance test run: API P95 < 500ms, load test for peak scenarios (Eid / White Friday volumes)
- [ ] Error tracking (Sentry or equivalent) set up for new code paths
- [ ] Feature flag configured (if staged rollout) — tested in off and on states
- [ ] Database migrations reviewed and tested (rollback migration prepared if schema changes)
- [ ] Dependency services confirmed available (cross-pillar integrations tested)
- [ ] [App Store] Webhook events tested if new events were added
---
## Pre-Launch: Compliance & Legal
[Include only gates triggered from Step 3]
### ZATCA (if triggered)
- [ ] ZATCA e-invoicing compliance review initiated
- [ ] Finance/Legal sign-off obtained
- [ ] VAT calculations verified against ZATCA requirements
- [ ] Invoice format reviewed (Arabic, QR code, required fields)
### SAMA (if triggered)
- [ ] SAMA compliance review initiated
- [ ] Payment flow changes reviewed and approved
- [ ] No stored payment data changes without explicit legal approval
### PDPL (if triggered)
- [ ] Privacy review completed
- [ ] Data minimization confirmed — only collect what's needed
- [ ] Merchant data processing agreement updated if new data category
- [ ] User consent mechanism in place if required
---
## Pre-Launch: Quality Assurance
### Arabic / RTL QA (Required for all UI changes)
- [ ] All UI tested in Arabic locale (Chrome / Android, Safari / iOS)
- [ ] RTL layout verified — no overlapping elements, correct text alignment
- [ ] Arabic text displays correctly (no truncation, correct font rendering)
- [ ] Numbers display correctly (Western Arabic numerals or Arabic-Indic as appropriate)
- [ ] Dates display correctly (Gregorian + Hijri if applicable)
- [ ] All new strings have Arabic translations (no English bleeding into Arabic UI)
- [ ] Arabic copy reviewed by Arabic native speaker on team
### Mobile QA (Required for all UI changes)
- [ ] Tested on iOS Safari (latest)
- [ ] Tested on Android Chrome (latest)
- [ ] Tested on Samsung Browser (significant Salla merchant usage)
- [ ] Touch targets meet minimum size (44x44pt)
- [ ] No horizontal scrolling on mobile viewport
- [ ] Core Web Vitals tested: LCP < 2.5s on 4G
### Functional QA
- [ ] All user stories in the PRD have a corresponding test case
- [ ] Edge cases documented and tested: empty states, error states, maximum input lengths
- [ ] Regression test suite run — no regressions in connected flows
- [ ] [SallaPayments features] Payment success/failure flows tested end-to-end in staging
- [ ] [Salla Shipping features] Label generation and carrier API integration tested
- [ ] [App Store features] SDK impact tested with partner app in sandbox
---
## Pre-Launch: Communications
### Internal Communications
- [ ] Engineering team briefed on launch timeline and monitoring expectations
- [ ] CS team briefed on what's changing and FAQ document ready (in Arabic)
- [ ] QA team aware of production deployment window
- [ ] Leadership notification sent (if high-visibility feature)
- [ ] On-call rotation confirmed for launch day and 48h post-launch
### Merchant Communications (if applicable)
- [ ] In-app announcement copy written (AR + EN)
- [ ] Email announcement draft ready (AR + EN)
- [ ] SMS notification copy ready if applicable (Arabic — short, respectful tone)
- [ ] Marketing approved merchant-facing copy
- [ ] Social media assets ready (Twitter/X Arabic account, Instagram)
- [ ] Announcement timing confirmed (avoid Ramadan prayer times for notifications)
### Partner / App Developer Communications (if App Store impacted)
- [ ] Developer changelog updated
- [ ] Breaking changes communicated to affected app developers with migration timeline
- [ ] Developer Slack/email notification sent
---
## Pre-Launch: Documentation
- [ ] Help center article written (Arabic + English)
- [ ] Help center article reviewed and published
- [ ] Changelog entry written
- [ ] API documentation updated (if new or changed endpoints)
- [ ] Internal runbook updated (if operational procedure changed)
- [ ] PRD updated to reflect any scope changes during development
---
## Launch Day
- [ ] Production deployment executed
- [ ] Smoke test run on production immediately after deploy
- [ ] Arabic UI spot-check on production (real device, Arabic locale)
- [ ] Feature flag enabled for target % of merchants (if staged rollout)
- [ ] Error rate monitored for first 30 minutes post-deploy
- [ ] CS channel monitored for immediate merchant reports
- [ ] Analytics events firing correctly (verify in analytics platform)
---
## Post-Launch Monitoring (First 72 Hours)
### First 24 Hours
- [ ] Error rate: within baseline (<X% error rate for feature's API)
- [ ] [Checkout features] Checkout CVR: no unexpected drop (alert if >1pp drop)
- [ ] [Payment features] Payment success rate: no unexpected drop (alert if >0.5pp drop)
- [ ] CS ticket volume: no unexpected spike related to this feature
- [ ] Merchant NPS verbatims: scan for related complaints
### First 72 Hours
- [ ] Feature adoption rate: [Target] merchants have used the feature
- [ ] Funnel analysis: any unexpected drop-off in the flow?
- [ ] Performance: API P95 stable, no degradation under production load
- [ ] Refund/cancellation rate: no unexpected increase (payment/checkout features)
- [ ] If staged rollout: decision to increase % or hold based on data
### First 7 Days
- [ ] OKR-relevant metric reviewed (is it moving in the right direction?)
- [ ] Post-launch metrics snapshot saved to `knowledge/metrics/`
- [ ] CS escalation review: any patterns worth addressing
- [ ] Rollout decision: full release, continue staged, or rollback?
---
## Rollback Plan
**Decision criteria to rollback:**
- Error rate exceeds [X]% sustained for more than 15 minutes
- Checkout CVR drops > [X]pp
- Payment success rate drops > [X]pp
- [Add feature-specific rollback triggers]
**Rollback steps:**
1. [Specific step — e.g., "Disable feature flag in admin"]
2. [Specific step — e.g., "Run database rollback migration: `rails db:rollback STEP=1`"]
3. [Specific step]
4. Notify CS team of rollback
5. Post in [engineering channel]: rollback complete, root cause investigation in progress
**Rollback owner:** [Name]
**Rollback decision authority:** [PM + Engineering Lead together]
---
## Metrics to Watch
| Metric | Baseline | Alert Threshold | 7-day Target |
|--------|----------|----------------|-------------|
| [Primary OKR metric] | [Value] | Drop > [X]% | [Target] |
| [Feature adoption] | — | < [X] merchants in 48h | [Target] |
| [Error rate] | [Baseline %] | > [X]% | Stable |
| [Pillar KPI] | [Value] | [Threshold] | [Target] |
---
*Generated by Salla PM OS launch-plan*
Step 5: Save and Follow Up
Write to: knowledge/launches/launch-[feature-slug].md
Tell the user:
- File path
- How many compliance gates are triggered — and which are critical-path blockers
- Estimate of readiness based on what's known
Suggest:
- If ZATCA/SAMA triggered: "Loop in compliance team now — these are the longest lead-time items"
- If Arabic copy is pending: "Content team needs lead time for quality Arabic copy"
- If App Store impacted: "Notify partner developers at least 2 weeks before launch"
