Deployment Canary

A release is not done when it is deployed — it is done when it survives contact with real traffic. This skill formalizes the canary phase between "ship" and "fully rolled out": define what healthy looks like, watch the right signals, and rollback fast when the evidence says to.

When to Use

• After deploying a new version behind a canary, percentage rollout, or feature flag
• Before promoting a release from a small traffic slice to full production
• When the release changes critical paths: auth, checkout, billing, queueing, migrations
• When a team needs explicit rollback criteria instead of "watch the dashboard and hope"

When NOT to Use