What problem does it solve? Teams lack a structured way to define service level objectives, track error budgets, and set burn-rate alerting thresholds across Trigent products, making reliability posture hard to measure and enforce. ## Core Features & Use Cases - SLO Definition: Generate SLI definitions with New Relic NRQL and Azure Monitor queries, SLO targets, and error budgets per service for products like Emergency Management, Training, Visitor Management, and SmartPass. - Error Budget & Burn-Rate Alerts: Calculate remaining error budget in minutes per month and produce 3-tier multi-window burn-rate alert thresholds with an error budget release policy. - Compliance Review: Audit current SLO compliance against live Azure Service Bus DLQ metrics and optionally document results as a Confluence page. - Use Case: Run the define mode for the Emergency Management product to get 99.9% availability targets for the emergency-management-api, NRQL alert queries, and a Confluence SLO page. ## Quick Start Ask the assistant to define SLOs for the Emergency Management product using the sre-slo skill.