Loading...
Loading...
Found 1,142 Skills
Plans sprint by selecting items from backlog, defining objective, capacity, and execution order. Use at the beginning of a work cycle to align what will be done.
Guides pension and retirement fund work—DB vs DC structures, funding policy, liability measurement (PV of benefits, discount rates, mortality), ALM overview, plan design, public and multi-employer pensions, risk transfer (buyouts, annuities, de-risking), US regulatory overview (ERISA, PBGC, DOL, IRS qualified plans), institutional investor role, and fiduciary governance—not legal or tax advice. Use when the user mentions pension fund, retirement plan, defined benefit, defined contribution, 401(k), pension funding, PBGC, ERISA, pension liability, discount rate pension, pension buyout, de-risking pension, or ALM pension—not P&C insurance (property-casualty-insurance), actuarial modeling only (actuary), actuarial engagements (actuarial-consulting), personal IRA advice (financial-analyst), or legal interpretation (commercial-counsel).
Guides product management for human data platforms—annotation and labeling products, workforce workflows, task design, quality systems (gold sets, adjudication, inter-annotator agreement), customer ML-team project delivery, contributor experience, and privacy-safe handling of human-generated training data. Use when prioritizing roadmap for labeling/RLHF/eval data platforms, writing PRDs for annotation or QA features, defining success metrics for throughput and quality, scoping enterprise customer workflows, or balancing cost-quality-speed tradeoffs—not for hands-on model training (data-scientist), warehouse/analytics pipelines (data-warehouse-engineer), generic BRD workshops without product lens (business-analyst), AI solution architecture for copilots (applied-ai-architect-commercial-enterprise), or control implementation for audits (compliance-engineer). UX flows: product-designer. Eval harnesses: prompt-engineer-agent-prompts-evals. Pricing/packaging for platform: product-management-monetization.
Guides senior system and solution architecture—cross-service boundaries, integration patterns, non-functional requirements (scale, reliability, security, cost), ADRs, C4-style modeling, architecture review, build-vs-buy, and phased migration (strangler, dual-write). Use when designing multi-service systems, evaluating platform or vendor choices, writing or reviewing architecture decision records, defining standards and principles, or assessing technical risk across domains—not for single-service RFCs and module design (senior-software-engineer), data platform or mesh decisions (data-architect), cloud landing zone, Well-Architected, and migration architecture (cloud-architect), cloud/IaC implementation (infrastructure-engineer, cloud-engineer), internal developer platform product (platform-engineer), or program tracking (technical-program-manager). For business strategy and cases, use business-consultant; for applied AI (RAG, agents, copilots), use applied-ai-architect-commercial-enterprise.
Guides product infrastructure security—securing the runtime, data plane, and control plane that ships with the product: multi-tenant isolation, service-to-service auth, customer data boundaries, secure defaults in APIs and workers, abuse-resistant rate limits, product-scoped secrets and encryption, and security design reviews for product infra changes. Use when threat-modeling product features, designing tenant isolation, hardening service mesh or internal APIs, reviewing product IaC/modules for data leaks, defining secure baselines for microservices the product team owns, or partnering on incidents affecting customer workloads—not for corporate IdP/SIEM (information-security-engineer), CI pipeline gates only (devsecops), SOC operations (defensive-security-analyst), authorized pentest execution (offensive-security-analyst), general IDP golden paths (platform-engineer), company-wide GRC (cybersecurity), or applied AI solution architecture for LLM features (applied-ai-architect-commercial-enterprise).
Design dashboards, write analytical SQL, define KPIs, and manage stakeholder analytics requirements. Cover chart selection, data storytelling, cohort/funnel analysis, metric definitions, and BI tool patterns (Tableau, Looker, Power BI). Triggers on "build dashboard", "design dashboard", "write analytical SQL", "cohort analysis", "funnel analysis", "define KPI", "define metric", "reporting requirements", "data storytelling", "stakeholder analytics", "retention analysis", or "BI report". For business model canvas, TAM/SAM/SOM, and competitor monetization research, use business-model-researcher—not bi-analyst. For building warehouse marts, dbt models, tests, and lineage—not dashboards—use analytics-data-engineer.
Guides Site Reliability Engineering—SLI/SLO and error budgets, reliability dashboards and burn-rate alerting, production readiness reviews, capacity planning for availability, toil reduction, dependency and failure-mode analysis, release reliability (canaries, rollback criteria), and service-owner incident mitigation tied to customer impact. Use when defining or operating SLOs, measuring error budget burn, improving service reliability, running PRRs before launch, planning scalable resilient capacity, or leading technical mitigation during outages—not for CI/CD pipeline implementation (devops), incident program and paging policy design (incident-management-engineer), cloud access and patch tickets (cloud-system-administrator), load-test profiling (performance-engineer), rollout cutover strategy (deployment-strategist), or greenfield cloud build-out (cloud-engineer).
Extracts exact, behaviour-first specifications from an existing codebase. Defines domain concepts, use cases, and business rules with precision — zero implementation details. Use when reverse-engineering a legacy project into precise specs or preparing an AI-friendly spec set for a rewrite.
Create alerts, notifications, and automated actions on Fabric data and events via Fabric REST API and `az rest` CLI. Use when the user wants to: (1) create, update, or delete an alert or notification flow, (2) send a Teams message, send an email, or run a Fabric item when something happens, (3) connect alert logic to Eventhouse, Eventstream, Real-time Hub, or Digital Twin Builder / Ontology data, (4) adjust thresholds, filters, event triggers, or actions, (5) troubleshoot or change an existing Activator/Reflex definition. Triggers: "create an alert", "notify me when", "let me know when", "take action when", "send me an email when", "send a teams message when", "run a pipeline when", "update an alert", "delete an alert", "activator rule"
Design and implement collaborative data schemas using the Jazz framework. Use this skill when building or working with Jazz apps to define data structures using CoValues. This skill focuses exclusively on schema definition and data modeling logic.
Use when defining dynamic content rules, tokens, and conditional offers inside nurture programs.
Use hexagonal architecture for external systems; define ports (interfaces) and per-provider adapters; select adapter at composition edge