operating-production-services

SLOs (Service Level Objectives) define reliability targets; error budgets quantify how much failure you can tolerate within a period. This Skill provides templates and patterns to establish the SLO/SLI/SLA hierarchy, calculate error budgets from your reliability target, and align incident response to budget consumption so you maintain stability thresholds.

Burn-rate alerts detect when your service consumes error budget too quickly, triggering intervention before reliability targets breach. This Skill includes Prometheus-based burn-rate rules and SLO alerting patterns in references that automate threshold detection and alert routing for incident response.

Postmortems document what happened, why, and what to prevent recurrence. This Skill provides postmortem templates and enforces 5 Whys analysis methodology so your team extracts actionable insights from incidents and closes the feedback loop on reliability improvements.

SLO alerting links alerts directly to user-facing reliability targets rather than infrastructure metrics, reducing noise and focusing on outcomes. Use this approach for mature services where you've defined explicit reliability expectations; it's not intended for initial service development or undefined reliability needs.

On-call practices establish who responds, when, and how during incidents. This Skill provides incident-response patterns and postmortem-driven feedback loops that integrate SLO alerting with team escalation and retrospective analysis to sustain reliable service operation.