reliability-observability-gate

What problem does it solve?

Reliability and observability gates prevent production changes from shipping without measurable SLI/SLO impact, bounded failure modes, evidence-backed incident readiness, and testable recovery plans.

Core Features & Use Cases

• SLI/SLO impact and error-budget discipline: Ensures every user-facing path has an SLI and that error budgets are defined and respected before release.
• Performance, capacity, and cost guardrails: Verifies latency budgets, concurrency limits, saturation signals, and cost/capacity exposure are explicitly captured.
• Telemetry and alerting correctness: Requires structured logs with trace context propagation, bounded metric label cardinality, and multi-window multi-burn-rate alerting.
• Resilience controls validation: Checks circuit breakers, rate limits, timeouts, retries, fallbacks, DLQ/depth monitoring, and tested recovery/rollback criteria.
• Use Case: Before deploying a new feature that changes a critical API endpoint and adds async background processing, define SLI/SLO targets, resilience controls, and evidence-based recovery steps to reduce incident risk.

Quick Start

Use this skill to review a proposed production change and produce a complete reliability-and-observability plan that includes SLI/SLO assessment, telemetry requirements, alerting design, capacity/cost guardrails, and tested recovery and rollback criteria.