plan-rollout

Authors a change-monitoring section for the user's plan. The section becomes the input to monitor-rollout after the change ships.

When to use

The user is preparing a code change that will be deployed to production. Specifically:

• They're in plan mode and the change has a production-facing surface.
• They're drafting or reviewing a PR that will deploy.
• They're asking "how should I monitor this?", "what should we watch for?", "what are the SLIs?", "do we need a canary?"
• They're planning a release, a rollout, or a feature flag flip.

Skip this skill when the change is read-only or local-only, dev-stack only, or pure-documentation. Tell the user no monitoring plan is warranted in those cases.

Methodology

Anchored on the Google SRE book. Full term map in references/sre-vocabulary.md. Risk-tiering rubric in references/risk-rubric.md. Tier-to-checkpoint mapping in references/checkpoint-schedule.md. Indicator design (RATIO vs GAUGE, baselines, thresholds) in references/indicator-design.md. Multi-environment handling in references/multi-env.md.