planning-monitoring-checks

star 34

Observability: metrics, alerts, dashboards, post-change observation windows

OzeroHAX By OzeroHAX schedule Updated 2/16/2026
play_arrow Run Skill in Manus View GitHub

name: planning-monitoring-checks description: Observability: metrics, alerts, dashboards, post-change observation windows

Define the signals that tell whether "everything is OK" or "we must stop/roll back" Change goal + critical user scenarios SLA/SLO, existing metrics/alerts Risks (especially high-impact) Define 3-7 key signals: errors, latency, business metrics, resource saturation For each signal: source, aggregation, threshold, window, alerting Define a post-rollout burn-in observation window (e.g., 1-24h) and owners Define stop/rollback criteria as measurable conditions
Key signals
Alerts + thresholds
Dashboards / views
Burn-in window
Stop / rollback criteria
 Signals are tied to target behavior and risks, not "metrics in general" Thresholds and windows are defined (otherwise it is not controllable)
Install via CLI
npx skills add https://github.com/OzeroHAX/AssistAgents --skill planning-monitoring-checks
Repository Details
star Stars 34
call_split Forks 7
navigation Branch main
article Path SKILL.md
More from Creator
OzeroHAX
OzeroHAX Explore all skills →