Index of every page on this site: llms.txt
All skills
launchdarkly avatar

/launchdarkly-release-plans

@f0ee110 official
Run it yourself

List, create, edit, make default, and delete LaunchDarkly release plans of both kinds: environment release plans (one environment's phases, rollout steps, and rollback metrics, with starter plans) and flag release plans (a project's environments in release order, each with its environment release plan, which Release Autopilot proposes releases from on pull requests). Also starts a flag's release from a flag release plan. Use when the user wants to see, list, build, change, or remove a release plan (such as 'show me the flag release plans' or 'what release plans does production have'), set an environment's or a project's default plan, or when another skill such as Release Autopilot onboarding needs release plans planned or created. For first-time Release Autopilot setup, use launchdarkly-release-autopilot-onboarding, which follows this skill.

Use this Skill: https://skilld.dev/gh/launchdarkly/ai-tooling/launchdarkly-release-plans

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesenvironment-release-plans.md

≈1.3k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Environment release plans: starters and custom plans

Use this from Create. A release plan is a recipe for one environment, made of phases, rollout steps, and metrics. A plan with metrics makes a release guarded, so a regression on a metric can roll it back. A plan without metrics is progressive: say so.

Before you offer a starter

Check the project with reads, not questions.

  1. Randomization unit: search-contexts with kind: "user", limit: 1 in that environment. If it finds contexts, use user. If not, call search-contexts with no kind to see which kinds the project stores. If it finds other kinds, ask header "Roll out by" with those kinds and user. If it finds none, the app has not sent contexts yet: use user, the kind every project has by default, and say so. A plan whose unit is not a context kind in the project cannot be created.
  2. Rollback metrics: a guarded plan needs the unit to be available for guarded rollouts, and no read shows that. LaunchDarkly turns this on for user by default. For any other unit, skip this check, use no metrics, and list "make <unit> available for guarded rollouts, then add rollback metrics to the plan" as a follow-up. For user, call get-metrics with metricUsedIn: "guarded_rollouts", then without it if that finds none. Keep metrics whose analysisUnits include the unit; others cannot measure the release. If any remain, ask header "Rollback metrics", multiSelect: true, with up to three of them plus "No metrics" ("Release step by step without automatic rollback").

Starter plans

Ask header "Starter plan" with options that fit the environment, marking the first "(Recommended)":

  • Production: "Progressive" ("10% → 25% → 50% of everyone, with 4-hour holds"), "Custom" ("Build the plan step by step"), and "Not now" ("Leave this environment without a release plan for now").
  • Any other environment: "Progressive" ("10% → 50% of everyone, with 4-hour holds"), "Custom", and "Not now".

If the user picked rollback metrics, add "rolls back automatically if <metric names> regress" to the descriptions. Then show the full plan and ask "Looks right" or "Adjust it", with the plan in the preview of "Looks right" (or in the question text if the question tool has no preview). For "Adjust it", change the plan as the user asks, then show the full plan again and ask "Looks right" or "Adjust it" again, with the changed plan in the question. Go on to the confirmation only after "Looks right". For "Not now", create nothing, and list "set up a release plan for <environment>" as a follow-up.

Starter Key Phases
Progressive (non-production) progressive One phase for everyone: 10% for 4h, then 50% for 4h
Progressive (production) progressive One phase for everyone: 10%, 25%, 50%, each for 4h

Every starter uses automatic advancement and cleanupBehavior: "remove_rules_and_update_default_rule", so the release finishes by serving everyone. Allocations are per 100,000 (10000 = 10%). There is no 100% step, because completing the release reaches everyone. Each 4-hour hold is durationMillis: 14400000. <unit> is the randomization unit.

The phase has only the randomization unit clause, which means everyone:

{ "attribute": "kind", "op": "in", "values": ["<unit>"], "contextKind": "<unit>" }

Rollback metrics go in progressiveRelease.metrics, keyed by metric key, each with automatic rollback:

{ "user-error-rate": { "isGroup": false, "autoRollback": true } }

A plan with metrics allows at most 50000 (50%) per step, and every starter step fits. A plan without metrics allows up to 99000 per step.

Keys

Read the environment's plans before you create one. Plan keys are unique among the project's active plans, across environments, so the same starter in two environments needs two keys. If progressive is taken, use progressive-2, then progressive-3, and so on. A taken key returns 409.

Custom plans

Ask each setting as its own question, never bundled:

  1. Randomization unit: the context kind to roll out by, such as user or account.
  2. Rollout steps: header "Rollout", with options such as "10% → 25% → 50%, 4h holds" or "10% → 50%, 24h hold". The user can type another schedule in Other.
  3. Advancement: header "Advance", options "Automatic" ("Move to the next step when the hold ends and metrics are healthy") and "Manual" ("A person moves each step").
  4. Metrics: call get-metrics. Offer up to four relevant metrics with multiSelect: true. If none fit, use launchdarkly-metric-choose to decide which metrics to add, and record each one to create before the plan. This creates the metric only: if the app does not send the event yet, list instrumenting it as a follow-up, and do not edit code or .env files.
  5. Cleanup: header "Cleanup", options "Leave rules in place" and "Remove rules and update the default rule", each with its outcome.

Every phase needs at least one clause. Follow the create-environment-release-plan tool guidance for the rest.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alert1d3 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    This skill provides a secure interface for managing LaunchDarkly release plans. It implements industry-standard safety practices, such as ensuring sensitive API tokens are never handled by the AI and requiring explicit user confirmation before any modifications are made to production settings. For advanced operations, it provides clear instructions for users to run commands locally, maintaining a secure boundary between the AI and the user's credentials.

  • Socket2d

    No alerts

  • Snyk1d

    Risk: CRITICAL · 1 issue

Signed by skilld at f0ee110. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 days ago
metadata
{
  "author": "launchdarkly",
  "version": "1.2.1"
}
Other metadata
compatibility
Uses the hosted LaunchDarkly MCP server. When the server has no tool for an operation (flag release plans before their tools reach the account, deleting an environment release plan), the user runs the REST API (beta) command that the skill shows in their own terminal.

README badge

README badge for launchdarkly/ai-tooling/launchdarkly-release-plans