flag-ramp

Create and manage multi-step ramp schedules for a GrowthBook feature flag rule. A ramp schedule progressively increases (or decreases) a rule's traffic coverage over time, with defined hold intervals between steps. Steps can be manual (operator advances them) or time-gated (auto-advance after an interval).

All API calls go through the bundled helper: ${CLAUDE_PLUGIN_ROOT}/scripts/gb-call. It needs GB_API_KEY set in env or written to ~/.config/growthbook/.env by /growthbook:gb-setup.

How ramp schedules work

A ramp schedule is attached to a specific rule on a feature flag. When published, the ramp begins running immediately — there is no automatic delay unless you explicitly set a startDate (uncommon; most teams prefer to trigger the ramp manually after publish via the GrowthBook UI).

At each step, the schedule applies actions — patches to the rule, typically changing coverage. After a step:

• If the step has an interval (seconds), it auto-advances after that duration.
• If interval is null, it holds until a team member manually advances it in the UI.

When all steps complete, endActions are applied (typically setting coverage to 1.0). If the ramp is rolled back at any point, startActions are applied (restoring the pre-ramp state).

Ramp schedules are staged on a draft revision as rampActions and executed atomically at publish time.

Workflow