definir-slo

Cria/Atualiza:

• .planning/slos/<slo_name>.md — definição canônica do SLO
• supabase/migrations/<timestamp>_create_sli_<slo_name>.sql — view materializada SLI

Após: SLO está em draft status. Próximo passo: /burn-rate-status <slo_name> para validar baseline; após 1+ semana, promover de draft → test_channel → primary.

Flags:

• --target <percent> — target % do SLO (default: agent sugere baseado em criticality, sempre ≤ 99.95%)
• --owner <email> — owner do SLO (default: AskUserQuestion)
• --window <duration> — sliding window (default: 30d)

Pré-requisito (Full mode): projeto Supabase configurado, schema observability com tabela de events (Phase 31 supabase-architect projeta isso).

1. Parsear argumentos

FEATURE=$(echo "$ARGUMENTS" | awk '{print $1}')
TARGET=$(echo "$ARGUMENTS" | grep -oE -- '--target [0-9.]+' | awk '{print $2}')
OWNER=$(echo "$ARGUMENTS" | grep -oE -- '--owner [^ ]+' | awk '{print $2}')
WINDOW=$(echo "$ARGUMENTS" | grep -oE -- '--window [^ ]+' | awk '{print $2}')

[ -z "$FEATURE" ] && {
  echo "Uso: /definir-slo <feature> [--target N] [--owner email]"
  exit 1
}

[ -z "$WINDOW" ] && WINDOW="30d"

2. Detectar supabase/config.toml

PROJECT_ID=""
if [ -f supabase/config.toml ]; then
  PROJECT_ID=$(grep -E '^project_id\s*=' supabase/config.toml | sed 's/.*= *"\(.*\)".*/\1/' | head -1)
fi

3. Dispatch para slo-engineer

Task(
  subagent_type="slo-engineer",
  prompt="
feature: ${FEATURE}
${TARGET:+target: ${TARGET}}
${OWNER:+owner: ${OWNER}}
window: ${WINDOW}
${PROJECT_ID:+project_id: ${PROJECT_ID}}

Aplicar skill event-based-slos. Gerar:
1. .planning/slos/<slo_name>.md (SLO definition canônico)
2. supabase/migrations/<timestamp>_create_sli_<slo_name>.sql (materialized view + pg_cron refresh)

Se target > 99.95%, recusar e explicar — métrica informativa, não SLO.
Se Full mode (mcp__supabase disponível), apply_migration; senão, output text.
"
)