Post-Change Monitor Planner
Goal
Define the smallest useful monitoring set after a change.
This skill does not build monitoring systems. It decides what should be watched, what thresholds matter, and when to escalate.
When To Use
- before rollout
- after a risky change is approved
- when rollback or mitigation depends on early detection
Scope Boundaries
In scope:
- define what to monitor
- define threshold logic
- define escalation timing
Out of scope by default:
- full observability implementation
- long-term analytics strategy
Workflow
- State the change going live.
- Identify likely regression surfaces.
- Choose a small monitor set.
- Define thresholds and observation window.
- Define escalation owner or next action.
Output Contract
change_under_watchmonitor_setthresholdsobservation_windowescalation_rulerecommended_followupnext_step
Guardrails
- Do not monitor everything.
- Prefer early indicators tied to the main risk.
- Keep thresholds explicit enough to act on.