Launchdarkly Guarded Rollout

This walks you through setting up progressive feature rollouts in LaunchDarkly with automated monitoring and rollback triggers. You define stages (typically 1%, 10%, 50%, 100%), pick metrics to watch (error rates, latency, conversions), and set regression thresholds that either notify you or automatically roll back if things go sideways. The workflow is pretty structured: inspect your flag variations, design your stages with monitoring windows, configure metrics with thresholds, then fire it off. It's built for the common case where you want to release gradually but don't want to babysit dashboards 24/7. The automatic rollback on regression detection is the real value here, assuming you trust your thresholds and have metrics that actually reflect user pain.

skills.sh installs: 2K
GitHub stars: 19
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add launchdarkly/agent-skills --skill launchdarkly-guarded-rollout --agent claude-code

Installs into .claude/skills of the current project.

Files

LaunchDarkly Guarded Rollouts

You're using a skill that will guide you through configuring guarded rollouts in LaunchDarkly. Your job is to design rollout stages, select monitoring metrics, choose which regressions roll back automatically, and start the rollout.

Prerequisites

This skill requires the remotely hosted LaunchDarkly MCP server to be configured in your environment.

Required MCP tools:

start-guarded-rollout -- start a progressive rollout with monitoring
get-flags -- inspect the flag and its variations
get-metrics -- find metrics to monitor during the rollout

Optional MCP tools:

stop-guarded-rollout -- halt an active rollout immediately
toggle-flag -- ensure the flag is turned on before starting
create-metric -- create metrics if they don't exist

Core Concepts

What Are Guarded Rollouts?

A guarded rollout progressively increases traffic to a new feature flag variation through a series of stages. At each stage, LaunchDarkly monitors selected metrics for regressions. If a regression is detected, the rollout can automatically pause and notify the team — or even roll back.