Interactive wizard to design an SLO with SLI, target, error budget, and burn-rate alerts
Step through SLO design using the slo-architect skill. Produces an SLO definition, computes error budget + multi-window burn-rate alerts, and runs the reviewer to catch common bugs.
/slo-design
/slo-design --service checkout-svc --sli-type request-success-rate --target 99.9SKILL=engineering/slo-architect/skills/slo-architect
# Step 1: gather inputs (service, sli-type, target, window, owner)
# Step 2: render SLO definition
python "$SKILL/scripts/slo_designer.py" \
--service "$SERVICE" \
--sli-type "$SLI_TYPE" \
--target "$TARGET" \
--window-days "$WINDOW_DAYS" \
--owner "$OWNER" \
--policy-doc "$POLICY_DOC" \
--format json > .slo.json
# Step 3: compute error budget + burn-rate alerts
python "$SKILL/scripts/error_budget_calculator.py" \
--target "$TARGET" \
--window-days "$WINDOW_DAYS"
# Step 4: render the markdown SLO for peer review
python "$SKILL/scripts/slo_designer.py" \
--service "$SERVICE" \
--sli-type "$SLI_TYPE" \
--target "$TARGET" \
--window-days "$WINDOW_DAYS" \
--owner "$OWNER" \
--policy-doc "$POLICY_DOC"
# Step 5: validate against the reviewer
echo "=== After saving the SLO, run slo_review.py against the doc ==="A markdown SLO definition with:
slo-architect skill installed.slo.json written for use with downstream tools (chaos-engineering blast radius, etc.)slo_review.py checks19392f7
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.