slo-reliability-architect

What problem does it solve?

This Skill helps define reliability targets that reflect how users actually experience a product, replacing noisy infrastructure-first alerting with business-relevant SLOs, SLIs, and error budgets.

Core Features & Use Cases

• Journey-Based SLO Design: Inventories critical user journeys such as login, checkout, exports, and APIs, then assigns symptom-based SLIs at the edge where users feel failures.
• Error Budgets and Paging Policy: Translates reliability targets into user-meaningful error budgets and burn-rate alerting so pages fire on budget threats while cause metrics go to tickets.
• Failure and Tenant Analysis: Evaluates dependency chains, shared failure modes, noisy-neighbor effects, and per-tenant or tiered reliability views so aggregate metrics do not hide real customer pain.
• Use Case: A team with a 99.95% aggregate uptime but unhappy enterprise tenants can use this Skill to create per-tenant SLOs, demote CPU alerts, and define when release velocity must slow down.

Quick Start

Ask for reliability design for your product by listing the journeys that matter, the current alert noise, and any tenant or SLA constraints.