Use rollout-plan

Plan the progressive release of a code change behind a feature flag or canary

Plan the progressive release of a code change behind a feature flag or canary — the exposure ladder (internal, beta cohort, 1%, 5%, 25%, 50%, 100%, or what the traffic supports), and for each step who is exposed, decision and guardrail metrics with a baseline and a threshold against a control cohort, the minimum traffic and time before the numbers mean anything, a promote / hold / roll back rule set in advance, who watches and what aborts automatically; then what turning the flag off does not undo, and who removes the flag by when.

Reach for it when the user asks for a rollout plan, canary plan, ramp schedule, progressive delivery or percentage rollout, "how long should the canary run", "when do we go from 5% to 25%", or how to turn on a flagged feature safely.

Install it

npx skilldrop-cli install rollout-plan                 # Claude Code, your user folder
npx skilldrop-cli install rollout-plan --project       # Claude Code, this repo
npx skilldrop-cli install rollout-plan --ide cursor    # or kiro, codex, antigravity, copilot

It is part of the Dev team pack: --pack dev-team installs it with its neighbours.

It ships scripts, so it needs Python 3 (standard library only, nothing to install). What they may touch is declared in its manifest.

Ask for it

Say it the way you would to a colleague. Requests like these route to it:

• "Plan a canary rollout for the new pricing engine — it's behind a feature flag"
• "What percentages should we ramp the checkout_v2 flag through, and when do we promote each step?"
• "How long does our 1% canary need to run before the error numbers mean anything?"
• "Write a progressive delivery plan with rollback criteria for the new recommendations widget"
• "We're turning on the new login flow for users next week — how do we do it gradually and safely?"

Requests like these belong to a different skill, so it shouldn't answer them:

• "Plan the backfill and expand-contract migration for splitting the users table"
• "Are we ready to launch the new checkout on Monday? Give me a go/no-go"
• "Write the release notes for version 4.2"

If another skill answers instead, ask for this one by name: "use rollout-plan".

Check what you get

A good result:

• The first two lines answer the user's question in plain words, with the input fact that settles it.
• The binding constraint is named and the ladder visibly follows it (cap, cycle, deadline, segment, shadow, volume).
• Every threshold is testable: metric, baseline, limit against the flag-off control; counts where volumes are small.
• Every number traces to the input, to arithmetic on it, or to a one-line [assumption].
• A deadline in the input gets a dated ladder that shows whether it is met.
• Promote, hold, roll back and abort are written before the step, with a watcher, a sign-off where one is needed, and an override role.
• The not-undone list covers what this change sends, writes or charges, with handling for each.
• The flag has an owner and a removal date.
• The reply is shorter than the plan it replaces would be at full length; "To confirm" is never longer than the ladder.

See a worked example

• sync engine workspaces

Use something else when

• Schema changes, backfills, datastore or provider swaps, dual-writes: migration-plan
• "Are we ready to launch?" go/no-go: launch-readiness
• SLOs, alerts and dashboards for the service: observability-plan
• Defining what success means for the feature: success-metrics
• The on-call procedure for the service as a whole: runbook-generator
• A change with no flag, canary or staged deploy: there is nothing to ramp; plan the gate first

Where a loop runs it

• Stage plan of the release loop

Next

• SKILL.md, the instructions the agent reads
• Its page on the site
• Related: migration-plan, launch-readiness, observability-plan, success-metrics, runbook-generator

Edit this page on GitHub · View source