salla-pm-dashboard

name	salla-pm-dashboard
description	Salla PM Dashboard: produces a single-page product status overview by reading all knowledge files. Shows OKR progress, sprint status, recent decisions, blockers, upcoming launches, and key metrics. Use when asked for a status overview, dashboard, or 'what's going on with my product'.

Salla PM Dashboard

You produce a single-page status dashboard by reading everything in the knowledge/ directory and pulling live data from any available MCP integrations.

Before Running

1. Check that knowledge/ exists. If not: "لم أجد قاعدة معرفة. شغّل /salla-pm-setup أولاً."
2. Read knowledge/pm-context.md for squad and product context.

Data Collection

Read all available knowledge files. Note what exists and what is missing.

Files to Read (skip any that don't exist)

• knowledge/pm-context.md — Squad/product context
• knowledge/okrs.md — OKR definitions and progress
• knowledge/team.md — Team info and capacity
• knowledge/roadmap/*.md — Roadmap items (most recent)
• knowledge/sprints/*.md — Sprint scoping (most recent)
• knowledge/decisions/*.md — Recent decisions (last 5)
• knowledge/launches/*.md — Upcoming or recent launches
• knowledge/metrics/*.md — Latest metrics snapshots
• knowledge/feedback/synthesis-*.md — Latest feedback synthesis
• knowledge/priorities/*.md — Current prioritization
• knowledge/opportunities/*.md — Recent opportunity assessments

MCP Integrations (use if available, skip gracefully if not)

• Linear / Jira: Current sprint tickets, status, blockers, velocity
• GitHub: Open PRs, recent deployments, failing CI checks
• Slack: Recent product-related threads, unresolved questions

For each unavailable integration, add a note in the dashboard: (Live data unavailable — connect {tool} MCP for real-time updates)

Dashboard Output

Present in this format:

# Salla PM Dashboard — {squad_name}
*Generated: {today's date and time}*

---

## OKR Progress

| Objective | Key Result | Progress | Status |
|-----------|-----------|----------|--------|
| {obj} | {kr} | {X%} | {On track / At risk / Not tracked} |

---

## Sprint Status
{Current sprint name/number}

| Status | Count |
|--------|-------|
| To Do | {N} |
| In Progress | {N} |
| Done | {N} |

**Blocked items:**
- {item}: {blocker details}

{If no sprint data: "لا توجد بيانات سبرينت. شغّل /salla-sprint-scope لتخطيط السبرينت القادم."}

---

## Recent Decisions (آخر القرارات)
{Last 3-5 decisions with date, title, and outcome}
{If none: "لم يتم توثيق أي قرارات. استخدم /salla-decision-record بعد قرارك القادم."}

---

## Open Blockers (العوائق المفتوحة)
{Blocked items from sprint, launches, or decisions}
{If none: "✓ لا توجد عوائق محددة."}

---

## Upcoming Launches (الإطلاقات القادمة)
{Next 2-3 launches with target date and readiness status}
{If none: "لا توجد إطلاقات مخططة. استخدم /salla-launch-plan عندما تكون مستعداً."}

---

## Metrics Snapshot (لمحة المؤشرات)
{Latest values for key metrics from pm-context.md}
{Trends if multiple snapshots exist}

| Metric | Current | Target | Trend |
|--------|---------|--------|-------|
| {metric} | {value} | {target} | {↑ / ↓ / →} |

{If no data: "لا توجد مؤشرات مسجلة. استخدم /salla-metrics-check لبدء التتبع."}

---

## Merchant/Partner Feedback Themes (آراء التجار)
{Top 3 themes from latest feedback synthesis}
{If none: "لا توجد تحليلات آراء. استخدم /salla-feedback-synthesis لتحليل آراء التجار."}

---

## What Needs Attention (ما يستحق الانتباه)
{Synthesize: what looks off, what's overdue, what's at risk}
{Specific recommendations with skill commands}

Behavior Notes

• Be honest about gaps. If data is missing, say so and point to the skill that fills the gap.
• Highlight risks. If an OKR has no progress updates and the quarter is half over, flag it. If a launch is approaching with no plan, flag it.
• Salla-specific awareness. Flag compliance-related items (ZATCA, VAT) as high priority automatically. Flag anything affecting Arabic/RTL UX or local payment methods.
• Keep it scannable. Use tables, bullets, short phrases. This is a dashboard, not a narrative.
• Bilingual. Use Arabic for section headers; English for technical terms where natural.
• Suggest actions. End each empty section with the specific command the user can run to fill it.