Plan

Sits between detection and implementation in LaunchDarkly's SDK onboarding workflow. Takes your stack analysis and maps it to the correct SDK type, whether that's server-side, client-side, mobile, or edge. The real value is in the dual-SDK logic: it forces you to plan both tracks explicitly when you need server and client flags in the same app (Next.js being the obvious case). Won't let you handwave the second SDK or skip the second package install. Outputs a concrete checklist of files to touch, imports to add, env var conventions to follow, and which credentials go where. Keeps you from mixing up SDK keys and client-side IDs, which happens more often than it should.

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

View on GitHub

Install

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

Installs into .claude/skills of the current project.

Files

Generate integration plan (SDK install)

Based on what you detected, choose the right SDK and plan the minimal set of changes needed.

This skill is nested under LaunchDarkly SDK Install (onboarding); the parent Step 2 is plan. Prior: Detect repository stack. Next: Apply code changes.

Choose the right SDK

Use the SDK recipes reference to match the detected stack to an SDK. Start with Top 10 SDKs (start here) in that file for common stacks; use the (other) sections for less common SDKs.

The key decision:

SKILL.md on GitHub

Sponsors

Promote your product hereReach 125k+ visitors monthly Promote your product hereReach 125k+ visitors monthly