reliability

Availability targets, SLOs and error budgets, incidents and postmortems, a static status page, and an on-call policy.

• Version 0.1.0
• 6 skills
• 1 gate check
• Running on this site: Status

What it does

Reliability work for a repository, built on one service catalogue: one services/<id>.yml per service with its owner, tier, SLO, runbooks and dependencies. The skills set an availability target per service and check it against the dependencies, define SLOs with burn-rate alerts, run incidents, write blameless postmortems, publish a status page from the incident records, and set the on-call rules. A gate check reports catalogue entries without an owner, an SLO target or a runbook.

The skills prepare files, rules and commands. They never push, deploy, page, or change production, and the user publishes every change.

Install

Add the marketplace at release v0.1.0 once, then install the plugin and restart Claude Code.

claude plugin marketplace add uncovertechtalent/cto-powersuit#v0.1.0
claude plugin install reliability@cto-powersuit

Skills

• /reliability:incident

  Run an incident from declaration to close: set the severity and the roles (incident lead, comms, operations), keep a timestamped log, post public updates to the incident records and the status page, resolve and close it, and hand over to the postmortem skill.

• /reliability:nines-per-service

  Pick an availability target per service from user impact, tier and serial dependencies, check it against the allowed downtime per 30 days, quarter and year and against the product of its dependencies' availabilities, and write it into the service catalogue.

• /reliability:on-call

  Set up on-call for the services in the catalogue: the rotation, the escalation policy, the handover checklist and the paging rules (page only on user-facing symptoms, every alert links a runbook), with an audit of the existing alert rules, written to docs/sre/on-call.md.

• /reliability:postmortem

  Write a blameless postmortem for one incident: summary, impact in minutes, users and requests, a timeline with a source for every time, contributing factors as mechanisms, what went well and what went poorly, and action items with one owner and a due date each, linked from the incident record.

• /reliability:slo

  Define a service level objective for one service: the SLI as good events over valid events with exact queries, the target and window, the error budget, multiwindow burn-rate alerts and an error-budget policy, written to a docs page and linked from the service catalogue.

• /reliability:status-page

  Set up a static status page built from published records: the service catalogue in services/*.yml and the incident records in incidents/incidents.json, turned into one HTML page and a JSON file by a standard-library script that runs in the deploy job.

Gate checks

The checks this plugin adds to the deploy gate of the gate module, each with a pass fixture and a fail fixture:

• reliability.service-catalog

Source

The CTO powersuit is a set of agent skills, one module per CTO function from the deploy gate to the hand-over, that one person uses to run a company's whole engineering platform. reliability is one of its 18 plugins, published by Stefan Coetzee.

The skills, templates, checks, fixtures, and the full README of reliability at release v0.1.0: github.com/uncovertechtalent/cto-powersuit/tree/v0.1.0/plugins/reliability. License: MIT. Every plugin of the powersuit: CTO powersuit.