Skip to content

proflead/codex-skills-library / skills/reliability/reliability-slo-sla

reliability-slo-sla

Verified

Define or review SLOs and SLAs for a service. Use when a senior developer needs reliability targets.

Reliability SLO/SLA

Purpose

Define or review SLOs and SLAs for a service.

Inputs to request

  • User-facing indicators and expectations.
  • Historical reliability data.
  • Business impact thresholds.

Workflow

  1. Define user-visible indicators and error budget metrics.
  2. Set measurable SLO targets and alert thresholds.
  3. Align SLAs with business impact and support.

Output

  • SLO/SLA proposal with metrics.

Quality bar

  • Ensure metrics are observable and stable.
  • Document consequences of budget burn.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 321kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 321kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 321kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 321kUpdated Claude CodeCodexVerifiedInstall