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.

referencesrest-api.md

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

Release plan REST API

The user runs these commands in their own terminal with their LaunchDarkly API access token in LD_ACCESS_TOKEN, and pastes the output back. The agent shows them, filled in, and never runs them. Every endpoint is in beta, so every command sends LD-API-Version: beta. Each command prints the response body, then HTTP <status> on the last line. Replace PROJECT_KEY, PLAN_KEY, ENV_KEY, RELEASE_PLAN_KEY, and FLAG_KEY. For an instance other than https://app.launchdarkly.com, use that instance's URL.

Prefer the MCP tools. Use a command here only when the connected server has no tool for that operation: for example, flag release plans before their tools reach the account, or deleting an environment release plan without delete-environment-release-plan. Do not add -v or --trace: they print the Authorization header.

Endpoints

Flag release plans

Operation Method and path MCP tool Success
List a project's plans GET /api/v2/projects/{projectKey}/flag-release-plans?limit=50&offset=0 get-flag-release-plans 200
Get one plan GET /api/v2/projects/{projectKey}/flag-release-plans/{planKey} get-flag-release-plans with flagReleasePlanKey 200
Create a plan POST /api/v2/projects/{projectKey}/flag-release-plans create-flag-release-plan 201
Replace a plan (full update) PUT /api/v2/projects/{projectKey}/flag-release-plans/{planKey} update-flag-release-plan (changed fields only, confirm: true) 200
Delete a plan DELETE /api/v2/projects/{projectKey}/flag-release-plans/{planKey} delete-flag-release-plan (confirm: true) 204

The flag release plan tools may not be on every server yet. When one is missing, use the command below for that operation.

A project with no stored plans gets an empty list. Create a plan with "default": true to make it the project's default.

Environment release plans

Paths start with /api/v2/projects/{projectKey}/environments/{environmentKey}.

Operation Method and path MCP tool Success
List plans GET .../release-plans get-environment-release-plans 200
Get one plan GET .../release-plans/{releasePlanKey} get-environment-release-plans with releasePlanKey 200
Create a plan POST .../release-plans create-environment-release-plan 201
Replace a plan (full update) PUT .../release-plans/{releasePlanKey} update-environment-release-plan (changed fields only) 200
Delete a plan DELETE .../release-plans/{releasePlanKey} delete-environment-release-plan, where the server has it 204
Get the default GET .../default-release-plan get-environment-release-plans (default) 200, or 204 with no default
Set the default PUT .../default-release-plan with { "key": "..." } update-default-environment-release-plan with default: true 200
Clear the default DELETE .../default-release-plan update-default-environment-release-plan with default: false 204

The list returns items, totalCount, and _links, in creation order. limit is 1 to 50 (default 25). Page with offset while offset + items.length < totalCount.

Commands

List flag release plans

curl -sS -w '\nHTTP %{http_code}\n' \
  -H "Authorization: $LD_ACCESS_TOKEN" \
  -H "LD-API-Version: beta" \
  "https://app.launchdarkly.com/api/v2/projects/PROJECT_KEY/flag-release-plans?limit=50&offset=0"

Get a flag release plan

curl -sS -w '\nHTTP %{http_code}\n' \
  -H "Authorization: $LD_ACCESS_TOKEN" \
  -H "LD-API-Version: beta" \
  "https://app.launchdarkly.com/api/v2/projects/PROJECT_KEY/flag-release-plans/PLAN_KEY"

Create a flag release plan

curl -sS -w '\nHTTP %{http_code}\n' -X POST \
  -H "Authorization: $LD_ACCESS_TOKEN" \
  -H "LD-API-Version: beta" \
  -H "Content-Type: application/json" \
  "https://app.launchdarkly.com/api/v2/projects/PROJECT_KEY/flag-release-plans" \
  --data @- <<'JSON'
{
  "key": "default-release",
  "name": "Default release",
  "default": true,
  "environments": [
    { "environmentKey": "test", "environmentReleasePlanKey": "progressive", "triggerType": "flag_eval" },
    { "environmentKey": "production", "environmentReleasePlanKey": "progressive-2", "triggerType": "flag_eval" }
  ]
}
JSON

Leave out "default": true when the project already has a default.

Replace a flag release plan

Start from a fresh get. Send every field to keep, because anything left out is cleared, including default. key is not in the body; it is in the path.

curl -sS -w '\nHTTP %{http_code}\n' -X PUT \
  -H "Authorization: $LD_ACCESS_TOKEN" \
  -H "LD-API-Version: beta" \
  -H "Content-Type: application/json" \
  "https://app.launchdarkly.com/api/v2/projects/PROJECT_KEY/flag-release-plans/PLAN_KEY" \
  --data @- <<'JSON'
{
  "version": 1,
  "name": "Default release",
  "default": true,
  "executionMode": "sequential",
  "environments": [
    { "environmentKey": "test", "environmentReleasePlanKey": "progressive", "triggerType": "flag_eval" },
    { "environmentKey": "production", "environmentReleasePlanKey": "progressive-2", "triggerType": "flag_eval" }
  ]
}
JSON

Copy description, maintainer (as { "kind": "member", "memberId": ... } or { "kind": "team", "teamKey": ... }), and applicationKeys from the read when the plan has them. The read returns the maintainer with names; send only the kind and the ID or key.

Delete a flag release plan

curl -sS -w '\nHTTP %{http_code}\n' -X DELETE \
  -H "Authorization: $LD_ACCESS_TOKEN" \
  -H "LD-API-Version: beta" \
  "https://app.launchdarkly.com/api/v2/projects/PROJECT_KEY/flag-release-plans/PLAN_KEY"

List an environment's release plans

curl -sS -w '\nHTTP %{http_code}\n' \
  -H "Authorization: $LD_ACCESS_TOKEN" \
  -H "LD-API-Version: beta" \
  "https://app.launchdarkly.com/api/v2/projects/PROJECT_KEY/environments/ENV_KEY/release-plans"

Each item has key, name, version, progressiveRelease, and default (true for the environment's default plan). The list leaves out incomplete plans.

Replace an environment release plan

A full replace: the phases, steps, clauses, and metrics become exactly what you send. Start from a fresh get, and send version from it. The key and environment cannot change.

curl -sS -w '\nHTTP %{http_code}\n' -X PUT \
  -H "Authorization: $LD_ACCESS_TOKEN" \
  -H "LD-API-Version: beta" \
  -H "Content-Type: application/json" \
  "https://app.launchdarkly.com/api/v2/projects/PROJECT_KEY/environments/ENV_KEY/release-plans/RELEASE_PLAN_KEY" \
  --data @- <<'JSON'
{
  "version": 2,
  "name": "Progressive",
  "progressiveRelease": {
    "randomizationUnit": "user",
    "advancementMode": "automatic",
    "cleanupBehavior": "remove_rules_and_update_default_rule",
    "phases": [
      {
        "clauses": [{ "attribute": "kind", "op": "in", "values": ["user"], "contextKind": "user" }],
        "steps": [{ "allocation": 10000, "durationMillis": 14400000 }, { "allocation": 50000, "durationMillis": 14400000 }]
      }
    ],
    "metrics": {}
  }
}
JSON

A version mismatch returns 409 and changes nothing.

Delete an environment release plan

curl -sS -w '\nHTTP %{http_code}\n' -X DELETE \
  -H "Authorization: $LD_ACCESS_TOKEN" \
  -H "LD-API-Version: beta" \
  "https://app.launchdarkly.com/api/v2/projects/PROJECT_KEY/environments/ENV_KEY/release-plans/RELEASE_PLAN_KEY"

It returns 409 while a flag release plan still names the plan. Remove it from those flag release plans first. Its key can be used again after the delete.

Set or clear an environment's default

curl -sS -w '\nHTTP %{http_code}\n' -X PUT \
  -H "Authorization: $LD_ACCESS_TOKEN" \
  -H "LD-API-Version: beta" \
  -H "Content-Type: application/json" \
  "https://app.launchdarkly.com/api/v2/projects/PROJECT_KEY/environments/ENV_KEY/default-release-plan" \
  --data '{ "key": "RELEASE_PLAN_KEY" }'

Setting the default replaces the current one. The plan must be active in the environment and have a randomization unit. To clear the default, send -X DELETE to the same path with no body (204 whether or not there was one). GET on the path returns the default, or 204 when there is none.

Flag release plan fields

Create takes these fields. Replace takes the same fields without key, plus version.

Field Required Rules
key Create only 1 to 256 characters, ^[a-zA-Z0-9][._\-a-zA-Z0-9]*$. Unique among the project's active plans. Cannot change
name Yes At most 256 characters
description No At most 1024 characters
environments Yes 1 to 50 entries, in release order, each environment once
environments[].environmentKey Yes An environment in the project
environments[].triggerType Yes flag_eval, webhook, manual, or promotion. The first environment cannot use promotion
environments[].environmentReleasePlanKey Unless immediate A complete environment release plan in that environment, with exactly one phase
environments[].isImmediate No true releases at once with no release plan. Do not send a release plan key with it
executionMode No sequential, the only value LaunchDarkly accepts and the default
applicationKeys No At most 25 keys. Auto-releasing uses them to choose a plan for an application
default No Create: only when the project has no stored default. Replace: true demotes the current default; left out clears it. (update-flag-release-plan keeps the current value when it is left out)
maintainer No { "kind": "member", "memberId": "..." } or { "kind": "team", "teamKey": "..." }
version Replace only, optional The version from the last read. A mismatch returns 409 and changes nothing

A project has at most 100 active plans.

Flag release plan response

Create, get, and replace return the plan. Its version starts at 1 and goes up by 1 on each update.

{
  "key": "default-release",
  "_id": "0b6c3a43-5d0e-4f43-9a8e-2f6f1d7c9e10",
  "version": 1,
  "name": "Default release",
  "default": true,
  "executionMode": "sequential",
  "applicationKeys": [],
  "environments": [
    { "environmentKey": "test", "environmentReleasePlanKey": "progressive", "isImmediate": false, "triggerType": "flag_eval" },
    { "environmentKey": "production", "environmentReleasePlanKey": "progressive-2", "isImmediate": false, "triggerType": "flag_eval" }
  ]
}

Errors

Errors return { "code": "...", "message": "..." }. Read message for the reason.

Status When
400 A field breaks a rule above; an environment is not in the project; a release plan is unknown, incomplete, or in another environment; default on create while the project has a default; the project already has 100 plans; an unknown plan key when starting a release
401 No token, or the token is not valid
403 Plan does not allow this operation: the account does not have flag release plans. Any other message: the token's role lacks the action
404 The project, flag, or plan does not exist
409 Create: another active plan has the key. Replace: version does not match the plan's current version. Deleting an environment release plan: a flag release plan still names it

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