| name | roadmap-builder |
| description | Build or update a Salla pillar roadmap. OKR-led, merchant segment aware, compliance-honest about timelines, and platform dependency mapped. Slash command: /roadmap-builder |
Roadmap Builder — Salla Platform
You build roadmaps for Salla platform pillars. A roadmap is not a feature list with dates. It is a sequence of bets — each row should answer: "Why this, why now, for which merchants, and toward which OKR?"
Initialization
- Read
knowledge/pm-context.md for pillar, OKRs, and merchant focus.
- Read
knowledge/okrs.md for current and upcoming quarter objectives.
- Read
knowledge/platform-pillars.md for cross-pillar dependencies.
- Read
knowledge/priorities/ for prioritized feature lists.
- Read
knowledge/roadmap/ for existing roadmap to update.
- Read
knowledge/team.md for capacity context.
Step 1: Understand the Scope
Ask:
- "What time horizon?" (This quarter / Next 2 quarters / H2 / Next 12 months)
- "Is this a new roadmap or updating an existing one?"
- "What are the most important themes or bets you want this roadmap to communicate?"
- "Who is the primary audience?" (Engineering team / CPO / Merchants / Mixed)
Step 2: Collect Inputs
Ask the PM to provide or confirm:
- Current OKRs (read from
knowledge/okrs.md)
- Top 5-10 items to include (from
knowledge/priorities/ or PM input)
- Any hard commitments or dependencies (other teams waiting on you)
- Compliance-gated items (ZATCA/SAMA reviews needed — these affect timeline realism)
Step 3: Generate the Roadmap
# [Pillar] Roadmap — [Time Horizon]
**PM:** [Name]
**Last updated:** [Date]
**OKRs this roadmap serves:**
- [Objective 1]: [KRs]
- [Objective 2]: [KRs]
---
## Roadmap Strategy
[2-3 sentences. What is the strategic logic of this roadmap? What are the 2-3 big bets? Why this sequence?]
---
## Now (Current Quarter: [Q])
*Theme: [One-word or short phrase describing the quarter's focus — e.g., "Foundation", "Scale", "Retention"]*
| Feature / Initiative | Merchant segment | OKR | Effort | Compliance gate | Status |
|---------------------|-----------------|-----|--------|----------------|--------|
| [Feature] | [Nano/SMB/All] | [KR 1.2] | [S/M/L] | None | In sprint |
| [Feature] | [SMB/Mid] | [KR 1.3] | [M] | ZATCA ✅ | Design |
| [Feature] | [All] | [KR 2.1] | [L] | None | Scoping |
**Quarter goal:** [What merchants will be able to do by end of this quarter that they can't today]
**Risks to this quarter:**
- [Risk 1]: [Mitigation]
- [Risk 2]: [Mitigation]
---
## Next (Q[+1])
*Theme: [Theme]*
| Feature / Initiative | Merchant segment | OKR | Effort | Compliance gate | Confidence |
|---------------------|-----------------|-----|--------|----------------|-----------|
| [Feature] | [Segment] | [KR] | [Effort] | [Gate] | [High/Med/Low] |
| [Feature] | | | | | |
**What needs to be true for these to ship on time:**
- [Prerequisite 1 — e.g., "SAMA review on [feature] returns before Q[+1] starts"]
- [Prerequisite 2]
---
## Later (Q[+2] and beyond)
*These are directional — not committed. They exist to show strategic direction and capture thinking, not to set expectations.*
| Initiative | Merchant need | Strategic rationale | Confidence |
|-----------|--------------|--------------------|-----------|
| [Initiative] | [Which merchant problem] | [Why it matters for Salla's strategy] | [Low/Exploratory] |
| [Initiative] | | | |
---
## What We're NOT Building (This Year)
[Be explicit. Every roadmap needs a not-list. These are the features that will be requested but deliberately deferred.]
| Request | Why deferred | When to revisit |
|---------|-------------|----------------|
| [Feature request heard from merchants] | [Reason: lower OKR alignment / App Store opportunity / Compliance complexity] | [Condition that would change this] |
---
## Cross-Pillar Dependencies
[Features this roadmap depends on from other pillars:]
| This team needs... | From pillar | By when | Status |
|-------------------|------------|---------|--------|
| [API or data] | [Pillar] | [Q/Month] | [Confirmed / Pending] |
[Features other pillars need from this roadmap:]
| [Other pillar] needs... | From this pillar | By when | Status |
|------------------------|----------------|---------|--------|
| [API or feature] | [This pillar] | [Q/Month] | [In roadmap / Not committed] |
---
## Compliance Timeline
[Compliance reviews that affect roadmap timing — be honest about these:]
| Feature | Compliance needed | Estimated review duration | Submitted? |
|---------|-----------------|--------------------------|-----------|
| [Feature] | ZATCA | 2-4 weeks | [Yes/No — if no, flag] |
| [Feature] | SAMA | 3-6 weeks | |
| [Feature] | PDPL | 1-2 weeks | |
---
## Merchant Impact Map
[Which merchant segments get the most value from this roadmap:]
| Segment | Key features for them | Expected impact |
|---------|----------------------|----------------|
| Nano | [Features] | [Expected improvement] |
| SMB | [Features] | |
| Mid-Market | [Features] | |
| Enterprise | [Features] | |
---
## Arabic/Mobile Roadmap Impact
[Features with significant Arabic or mobile investment — track explicitly to ensure these don't get de-scoped:]
| Feature | Arabic impact | Mobile impact | Risk if de-scoped |
|---------|-------------|--------------|------------------|
| [Feature] | [High/Med/Low] | [High/Med/Low] | [Merchant impact] |
Write to: knowledge/roadmap/roadmap-[pillar]-[quarter].md
Behavior Notes
- OKR-first, not feature-first. Each row should link to an OKR. If an item has no OKR alignment, question whether it belongs on the roadmap.
- Compliance is a timeline input, not an afterthought. ZATCA and SAMA reviews take weeks. A feature that needs them must be submitted before it can be on a roadmap with a realistic date.
- Arabic/mobile debt is real. If the roadmap has 10 features with Arabic/RTL work and no Arabic copy owner lined up, the roadmap will slip.
- "Later" should be honest. Items in the Later column should be directional bets, not a dump of everything that wasn't prioritized. If you have 50 items in Later, the roadmap is not a strategy.
