메뉴
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
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Log a Salla product decision with context, options considered, rationale, and revisit conditions. Builds institutional memory so 'why did we do X?' is always answerable. Slash command: /decision-record
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
Facilitate a Salla sprint retrospective or post-mortem. Structured format with specific Salla considerations: compliance slippage, Arabic QA issues, cross-pillar dependency failures, and merchant impact. Slash command: /retro-facilitator
Generate Salla stakeholder updates in three versions: engineering (technical detail), leadership (business impact), and merchant-facing (what's new). Slash command: /status-update
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>
Review and sharpen a Salla PRD or spec. Checks for missing edge cases, weak acceptance criteria, Arabic/mobile gaps, compliance blind spots, and unclear merchant value. Returns a marked-up version with specific improvements. Slash command: /refine-spec
| 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 |
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.
Scan all knowledge files systematically. If a file or directory doesn't exist, skip silently.
knowledge/pm-context.md — pillar context, OKRs, team infoknowledge/okrs.md — OKRs and progressknowledge/platform-pillars.md — platform context and metrics definitionsknowledge/launches/ — upcoming and recent launchesknowledge/decisions/ — pending or recently made decisionsknowledge/retros/ — open action items from retrospectivesknowledge/updates/ — most recent stakeholder updateknowledge/metrics/ — latest KPI reviewsknowledge/experiments/ — running experiments and pending resultsknowledge/meetings/ — today's meetings and outstanding action itemsknowledge/briefs/ — most recent brief (to track what's changed since then)knowledge/feedback/ — most recent merchant feedback synthesisknowledge/sprints/ — current sprint plan and blockersUse these if available, skip gracefully if not:
If no MCP tools available, note which data is missing and show the briefing with what's available.
Run this analysis before writing 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]
After writing the file, present a verbal summary to the PM. Lead with:
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?
When relevant, note:
Flag if today is within 2 weeks of any of these events and the briefing should be adjusted accordingly.