LaunchDarkly Release Autopilot Onboarding

You're using a skill that walks a user through setting up Release Autopilot. The user picks the capabilities they want, and you set up only what those capabilities need: the GitHub App, repository mappings, Vega inference, and the environment release setup for auto-releasing.

This is a step-by-step wizard. Ask one question at a time and wait for each answer. Gather every decision first, confirm one plan, and only then write. Release Autopilot opens and changes pull requests, and auto-releasing can ship code, so every write is production automation.

Follow the write rules of launchdarkly-release-autopilot-settings (least privilege, owner/name only, never autoCleanup, current → proposed with blast radius). Its one-at-a-time confirmations are replaced by the single itemized confirmation at Step 7.

Prerequisites

This skill requires the remotely hosted LaunchDarkly MCP server. Installing the LaunchDarkly plugin is the first step: it adds this skill and the MCP server. In Claude Code, run /plugin marketplace add launchdarkly/ai-tooling, then /plugin install launchdarkly@launchdarkly-ai-tooling. In Cursor, install LaunchDarkly from Settings > Plugins. Then sign in to the launchdarkly server when the client asks.

Required MCP tools:

• get-automations / update-automations: get-automations returns the account settings and the repos on the GitHub App install with their mappings; update-automations takes accountWide: true for account settings or accountWide: false with repo for one repository
• get-member-self

On a server that has not picked up the Automations rename yet, the same tools are named get-release-autopilot, update-release-autopilot, and delete-release-autopilot-repo-settings; use those names with the same arguments. If a call fails with "this tool has been removed from the server", ask the user to reconnect the LaunchDarkly MCP server so it loads the new tool names, then retry.