bakrsabeeh

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

Generate a full Salla-aware PRD from a brief or conversation. Platform-pillar aware, compliance-flagging, Arabic/mobile-first, with user stories, Gherkin acceptance criteria, Salla metrics, and cross-pillar dependencies.

Research a Salla competitor and produce a battlecard. Pre-seeded with Salla's competitive landscape (Zid, Shopify, Youcan, Expandcart). Slash command: /competitor-intel <name>

When the user wants to create a content strategy, build a content calendar, define content pillars, plan blog content, or organize social media content for Salla. Also use when the user mentions 'content plan', 'content strategy', 'content calendar', 'blog topics', 'social content', 'content pillars', 'editorial calendar', or 'what content should we make'. For ad creative and performance copy, see salla-performance-creative.

When the user wants to create ad creative briefs, write performance marketing copy, generate paid social copy variants, or design creative for Salla campaigns. Also use when the user mentions 'ad creative', 'performance ads', 'creative brief', 'paid social copy', 'Meta ads', 'TikTok ads', 'Snapchat ads', 'Google ads copy', 'copy variants', or 'A/B test ad copy'. For organic content strategy, see salla-content-strategy.

When the user wants to build a go-to-market strategy, enter a new market segment, plan a market expansion, or define the strategic approach for a new product line or merchant category. Also use when the user mentions 'go-to-market', 'GTM', 'GTM canvas', 'market entry', 'new segment', 'market strategy', 'market expansion', 'GCC expansion', or 'strategic plan'. For single feature launches, see salla-product-launch.

When the user wants to plan or execute a product or feature launch on Salla. Also use when the user mentions 'launch a feature', 'product launch', 'GTM for new feature', 'announce update', 'release plan', 'launch checklist', 'feature release', 'go live', or 'launch campaign'. For full go-to-market market strategy, see salla-gtm-strategy.

When the user wants to plan or execute a seasonal campaign for Salla merchants. Also use when the user mentions 'Ramadan', 'رمضان', 'Eid', 'عيد', 'White Friday', 'الجمعة البيضاء', 'National Day', 'اليوم الوطني', 'Founding Day', 'يوم التأسيس', 'seasonal campaign', 'back to school', 'summer sale', or any commerce season in the GCC. Covers pre-season planning, peak execution, and wind-down. For WhatsApp-specific messages, see salla-whatsapp-campaigns.

When the user wants to create a WhatsApp campaign, design a WhatsApp message sequence, write WhatsApp copy for merchants, or plan a WhatsApp-based funnel. Also use when the user mentions 'WhatsApp campaign', 'WA message', 'WhatsApp flow', 'WhatsApp sequence', 'WhatsApp broadcast', 'WhatsApp marketing', 'WA funnel', or 'WhatsApp onboarding'. For email sequences, see salla-merchant-onboarding.

When the user wants to set up Salla growth context, initialize the growth skills, or set up market context. Also use when the user mentions 'set up context', 'Salla context', 'merchant personas', 'GCC market', 'initialize', or wants to avoid repeating market context across growth tasks. Run this first before using any other salla-growth skill — it creates .agents/salla-growth-context.md that all other skills read automatically.

The single entry point for any Salla growth request. Use when the user has a growth task but isn't sure which specialist skill to use. Also use when the user says 'help me with growth', 'I need a campaign', 'how do I grow', 'Salla marketing', or any broad growth request. Routes to the right specialist and returns a structured Growth Brief. For complex tasks, suggests invoking the full specialist skill.

Research a Salla competitor and produce a structured battlecard. Pre-wired for the MENA e-commerce landscape: Zid, Shopify Arabia, WooCommerce, Expandcart, Rewix. Fetches website, pricing, features, reviews. Use when asked about competitors, competitive analysis, battlecards, or 'what is Zid doing?'

Capture Salla product decisions with full context, alternatives considered, rationale, and revisit conditions. Auto-links to related PRDs, OKRs, and strategy. Use when documenting a decision, recording a choice made, or asked to capture why the team decided something.

Analyze merchant and partner feedback from any source — support tickets, NPS surveys, app store reviews, Slack channels, social media. Categorize by theme, frequency, and severity. Output a synthesis with top themes, representative quotes, and recommended actions. Use when analyzing merchant pain points, partner feedback, customer complaints, or NPS data.

Generate a comprehensive launch checklist for a Salla feature. Covers release criteria, QA, Arabic/RTL review, ZATCA compliance sign-off, merchant comms, rollout strategy, rollback plan, and metrics. Use when planning a feature launch, release, or rollout for Salla merchants or partners.

Review Salla squad metrics, identify trends and anomalies, connect movements to OKRs and recent changes, and produce actionable recommendations. Pre-loaded with Salla's key metric definitions: GMV, merchant activation rate, churn, ARPM, app store revenue. Use when reviewing metrics, analyzing KPIs, or asking 'how are our numbers?'

Create or update OKRs for a Salla squad. Aligns to Salla's growth objectives: merchant GMV, activation, retention, app store revenue, partner growth. Validates quality and measures. Use when asked to write OKRs, set quarterly goals, or define key results.

Validate product ideas and opportunities for Salla with MENA market sizing (TAM/SAM/SOM), competitive landscape analysis, strategic alignment to Salla OKRs, technical feasibility, and a go/no-go recommendation. Use when evaluating new feature ideas, market expansion, or 'should we build this?'

Daily morning briefing for Salla PMs. Reads all knowledge files, pulls from MCP integrations, and produces a prioritized 'what matters today' summary. Salla-specific: flags ZATCA deadlines, Saudi calendar events, merchant metric alerts. Use at the start of the day or when asked 'what should I focus on today?'

A comprehensive collection of Agent Skills for software engineering excellence. Use when designing systems, reviewing code, debugging failures, designing APIs, building test strategies, optimizing performance, hardening security, or responding to incidents. Activate for any senior engineering task.

Use when the user asks to "design an API", "review an API", "choose between REST and GraphQL", "version an API", "design a webhook", or discusses API contracts, backwards compatibility, or client-server interfaces. Provides senior engineering guidance for API design decisions.

Use when the user asks to "review this code", "give me feedback on a PR", "what should I look for in code review", "how do I review a pull request", or wants to improve their code review process. Provides a structured, senior-engineer-level code review framework.

Use when the user says "I have a bug", "this isn't working", "help me debug", "I can't reproduce this", "this works locally but not in production", or needs to trace a failure to its root cause. Provides systematic debugging methodology for software engineers.

Use when the user says "we have an incident", "production is down", "users are reporting errors", "our error rate spiked", "help me write a postmortem", or needs to structure an on-call response. Provides a systematic incident response framework for software engineers and on-call engineers.

Use when the user says "this is too slow", "how do I optimize this", "help me profile this", "our p99 is too high", "we're hitting database limits", or discusses latency, throughput, memory usage, or CPU profiling. Provides systematic performance engineering methodology.

Use when the user asks "is this secure", "how do I prevent SQL injection", "how should I store passwords", "do a threat model", "review this for security issues", "how do I handle authentication", or discusses OWASP, encryption, secrets management, or authorization. Provides security engineering guidance for software engineers.

Use when the user asks to "design a system", "evaluate architecture", "scale a service", "choose between databases", "design for high availability", "review a system design", or discusses distributed systems, microservices, data modeling, or architectural trade-offs. Provides senior engineering guidance for system architecture decisions.

Professional-grade skill for translating product intent, PRDs, roadmap items, and product discussions into explicit implementation-ready capability plans. Exposes constraints, invariants, interfaces, architectural decisions, and unresolved questions before multi-service work starts. Use when you need a durable, reusable capability contract that survives across harnesses, sessions, and teams.

Professional-grade article writing for blogs, guides, tutorials, newsletters, and long-form content. Enhanced with audience targeting, SEO optimization, distribution strategy, quality metrics, voice profiling, content frameworks, research methodology, and comprehensive quality assurance. Write distinctive, credible content that converts readers into users, customers, or advocates.

Operate long-lived agent workloads with observability, security boundaries, and lifecycle management. Specialized for GCC tech companies (Saudi Arabia, UAE, Kuwait, Qatar, Bahrain, Oman) building production AI systems with enterprise requirements, compliance needs, and reliability standards.

Think before you build. Validate the "why," run product diagnostics, and pressure-test product direction for GCC tech companies. Specialized for Saudi Arabia, UAE, Kuwait, Qatar, Bahrain, and Oman. For product teams, leaders, and founders who want to validate before engineering starts.

Evidence-first current-state research workflow specialized for PMs, founders, and entrepreneurs conducting market research, competitive analysis, and due diligence in GCC markets. Use when the user wants fresh facts, market comparisons, competitive enrichment, investor/partner/market intelligence, or recommendations built from current public evidence and supplied local context.

Offers product managers and teams an informed choice about response depth and token consumption before answering. Specialized for PM workflows: roadmaps, PRDs, market analysis, feature specs, team coordination. Use when the user explicitly wants to control response length, depth, or token budget for PM tasks. TRIGGER when: "token budget", "response length", "short version", "brief", "detailed", "exhaustive", "quick answer", "full analysis", "executive summary vs deep dive", "I need a 5-minute read", "give me the full thing", or clear variants where user is controlling answer size/depth for PM decisions. DO NOT TRIGGER when: user already specified depth level this session (maintain it), or request is a simple fact lookup.

Activate a 23-agent autonomous AI marketing team for Salla app developers on apps.salla.sa. Use when a developer wants to grow their app — increase installs, improve merchant activation, recover failed invoices, reduce churn, boost reviews, rank higher in the marketplace, or run any growth operation automatically. Triggers the full agentic workforce or individual agent tiers based on the growth goal. Say 'grow my app', 'increase installs', 'recover failed payments', 'reduce churn', 'get more reviews', 'rank higher', 'run a campaign', or 'activate the growth team'. For generic SaaS churn only: see churn-prevention. For generic email sequences: see email-sequence. For generic SEO: see ai-seo.

Conduct market research, competitive analysis, investor due diligence, and industry intelligence for the Gulf Cooperation Council (GCC) market with source attribution and decision-oriented summaries. Specifically designed for tech products, SaaS, platforms, and digital services targeting GCC markets (Saudi Arabia, UAE, Kuwait, Qatar, Bahrain, Oman). Use when researching market sizing, competitor comparisons, fund research, technology trends, or research informing GCC-specific business decisions.