plan

Generates a two-track LaunchDarkly SDK onboarding plan from the detected project stack.

25|8|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/launchdarkly/ai-tooling --skill plan-launchdarkly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/launchdarkly/ai-tooling/tree/main/skills/onboarding/sdk-install/plan
Command: npx skills add https://github.com/launchdarkly/ai-tooling --skill plan-launchdarkly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects and sequences the Steps to onboard LaunchDarkly SDKs by analyzing the repository stack, guiding users through server-side and client-side planning, and documenting required changes.

Core Features & Use Cases

  • Detect repository stack and compatibility
  • Generate a two-track integration plan (server-side and client-side) when needed
  • Specify dependencies, entrypoints, and environment conventions to apply later

Quick Start

Invoke the plan skill to generate a structured SDK onboarding plan based on the detected project stack.

Frequently Asked Questions about plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a LaunchDarkly SDK integration for my project?

Planning a LaunchDarkly SDK integration involves detecting your repository stack to generate a structured plan. This plan outlines required dependencies, entrypoints, environment variables, and specific steps for server-side and client-side tracks.

How do I know if my project stack supports LaunchDarkly SDKs?

The SDK onboarding process detects your project stack and checks compatibility automatically. It determines whether your environment supports server-side tracks, client-side tracks, or both, ensuring the generated integration plan aligns with your specific setup.

What is included in a LaunchDarkly SDK onboarding plan?

A LaunchDarkly SDK onboarding plan includes a two-track integration outline detailing required dependencies, application entrypoints, and environment variable configurations. It documents per-track implementation steps and how to verify changes against SDK recipes and project conventions.

Do I need to configure environment variables for LaunchDarkly client-side and server-side SDKs?

Yes, configuring credentials using environment variables is a required step in the SDK integration plan. The plan documents how to set up these environment variables for both server-side and client-side tracks to ensure proper authentication.

When do I need a two-track integration plan for LaunchDarkly?

A two-track integration plan is needed when your repository stack supports both server-side and client-side implementations. The planning process detects this capability and generates a combined plan with per-track steps for dependencies, entrypoints, and environment configurations.