SLO

Writes one SLO page per service in docs/sre/slo-<id>.md and links it from services/<id>.yml. The page names the events, the exact queries, the target and window, the error budget in events and in time, the burn-rate alerts, and the policy that applies when the budget runs low. The target comes from the catalogue; run the nines-per-service skill first when it is missing.

Inputs

Service (required): the catalogue id, with slo.target set.
User journey: what users do with the service, for example sign in, load the dashboard, pay.
Data: the metrics or logs system and the metric names, or the probe that measures the service.
Product owner: the person who agrees the error-budget policy with the service owner.

Steps

Set up. Copy the templates without overwriting:

mkdir -p docs/sre
rsync -a --ignore-existing "${CLAUDE_PLUGIN_ROOT}/templates/docs/sre/" docs/sre/