Skip to content
Skills Library
DevOps & cloud · Planning

ship-progressively

/ship-progressively

Use when rolling out any risky change to many users/hosts — stage it (canary → progressive → full) behind health gates and flags so a bad change is caught at 1% and auto-aborted, not at 100%.

Repository
truecast ↗
Licence
MIT
Last repository change
17.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 17.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when rolling out any risky change to many users/hosts — stage it (canary → progressive → full) behind health gates and flags so a bad change is caught at 1% and auto-aborted, not at 100%.

Original author description

Use when rolling out any risky change to many users/hosts — stage it (canary → progressive → full) behind health gates and flags so a bad change is caught at 1% and auto-aborted, not at 100%.

How it works

  1. The method
  2. Choosing the strategy
  3. The discipline
Original SKILL.md headings · 33 lines, 377 words
SKILL.md preview
---
name: ship-progressively
description: Use when rolling out any risky change to many users/hosts — stage it (canary → progressive → full) behind health gates and flags so a bad change is caught at 1% and auto-aborted, not at 100%.
---
# Ship progressively — expose the bug to 1%, not to everyone

The single biggest avoidable outage class is the **instant global rollout of a bad change.** CrowdStrike's July
2024 update crashed ~8.5M machines worldwide because a faulty content file shipped to everyone at once with no
staged rollout and no per-customer ability to delay — a ~$5B+ lesson in why you never fan a change out globally
in one step. Progressive delivery is how you make a bad change a small incident instead of a catastrophe.

## The method
1. **Canary first.** Route a small slice (1 host / 1% of traffic / internal users) to the new version. Watch
   its golden signals against the baseline for a real bake time — long enough for the failure to show.
2. **Gate each stage on health.** Promote 1% → 5% → 25% → 100% only while the canary's SLIs hold. **Automate
   the abort**: if the canary regresses (error rate, latency, crashes), halt and roll back without a human in
   the loop. Humans are too slow and too optimistic mid-rollout.
3. **Decouple deploy from release with feature flags.** Ship the code dark, then turn the behavior on for a
   cohort via a flag. Now "rollback" is a flag flip (instant, no redeploy), and you can ramp independently of
   the deploy.
4. **Stage by blast radius, not just by percentage** — region by region, tenant tier by tier, low-risk cohort
   first. Never make the first cohort your highest-value customer.

## Choosing the strategy
- **Canary / progressive traffic shift** — services behind a load balancer or mesh.
- **Blue-green** — two full environments, flip the router; instant rollback, double the cost during cutover.
- **Feature flag / dark launch** — application behavior; decouples release from deploy, enables per-cohort ramp
  and kill-switch.
- **Rolling update** — replace instances batch by batch; cheap, but ensure surge/health-check config so a bad
  image doesn't replace all healthy ones.

## The discipline
- A change that goes to 100% in one step had better be trivial and instantly reversible — otherwise it's a bet,
  not a deploy.
- The canary only protects you if you're *watching the right signal* (`observability-that-pages-on-symptoms`)
  and the abort is *automatic*. A canary nobody watches is just a slower outage.

Versions

The database has no other skills named ship-progressively.

Database snapshot: 13.11.2026 · package version 1ca374e2f8e7 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90safe-deployment
    Discipline for shipping changes reversibly, decouple deploy (code reaches production) from release (users see it) with feature flags, roll out progressively, and define the automated rollback trigger before shipping, not during the incident. Use when the user asks how to deploy…
  • 90deployment-strategies
    Gets a change into production safely — blue-green, canary, rolling, feature flags, and the rollback that makes each of them safe. Use this whenever the user is planning a release, asks how to deploy without downtime, mentions canary or blue-green, is adding a feature flag, or is…
  • 90canary-analysis
    Judge a canary release against a concurrent baseline using pre-set metric gates, automatic rollback, and statistically honest windows. Use when a deploy is rolling out to a slice of production traffic and you must decide pass, hold, or revert.
  • 90feature-flags
    Use when adding, rolling out, or cleaning up feature flags — gating a change, doing a progressive/canary release, building a kill switch, or removing a stale flag. Covers flag types, safe rollout, and the discipline that keeps flags from becoming permanent tech debt.
  • 100canary-release
    Ship a change as an Argo Rollouts canary in this team's cluster at the hackathon, check it, then promote or abort it through Radar. Use when asked for a canary, progressive delivery, a safe or gradual release, to promote or abort a rollout, or to switch the app from a Deployment to a Rollout.
  • 100flyio-deploy-integration
    Plan a Fly.io rolling, canary, or blue-green release with health, capacity, storage, and rollback constraints. Use when a release needs progressive exposure. Trigger with: "canary deploy on Fly", "use Fly blue-green", "design Fly rollout".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.