Skip to main content
configure-feature-flags Feature flags with OpenFeature and providers (GOFF, flagd, LaunchDarkly). Use when setting up the SDK, configuring a relay proxy, or adding flag test helpers.
Jump to install Skills Marketplace Discover and explore AI skills built by the community.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Show prompt details A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/laurigates/claude-plugins --skill configure-feature-flagsThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Download Zip Downloading... Related occupations SOC
Based on SOC occupation classification
More from this repository Install, configure and troubleshoot MCP servers. Use when adding/enabling servers, editing .mcp.json, fixing OAuth, or when a server runs stale code after an upstream fix.
FinOps snapshot — org billing, workflow stats, cache usage. Use when you want a high-level view of CI spending or workflow health before diving deeper.
GitHub Actions billing, workflow efficiency, and waste analysis at org or repo level. Use when investigating CI/CD costs, wasted runs, or optimizing triggers.
created "2025-12-16T00:00:00.000Z" modified "2026-05-09T00:00:00.000Z" reviewed "2025-12-16T00:00:00.000Z" description Feature flags with OpenFeature and providers (GOFF, flagd, LaunchDarkly). Use when setting up the SDK, configuring a relay proxy, or adding flag test helpers. allowed-tools Glob, Grep, Read, Write, Edit, Bash, AskUserQuestion, TodoWrite, WebSearch, WebFetch args [--check-only] [--fix] [--provider <goff|flagd|launchdarkly|split>] argument-hint [--check-only] [--fix] [--provider <goff|flagd|launchdarkly|split>] name configure-feature-flags
/configure:feature-flags
Check and configure feature flag infrastructure using the OpenFeature standard with pluggable providers.
When to Use This Skill
Use this skill when... Use another approach when... Adding feature flag infrastructure to a new project Creating or editing individual flag definitions in YAML Setting up OpenFeature SDK with a provider (GOFF, flagd, LaunchDarkly) Debugging why a specific flag evaluation returns unexpected values Auditing existing feature flag configuration for completeness Writing application logic that consumes feature flags Configuring relay proxy infrastructure (Docker, Kubernetes) Managing LaunchDarkly or Split dashboard settings Adding feature flag test helpers and in-memory providers Configuring error tracking (/configure:sentry instead)
Context
Package JSON: !find . -maxdepth 1 -name \'package.json\'
Python project: !find . -maxdepth 1 -name \'pyproject.toml\'
Go project: !find . -maxdepth 1 -name \'go.mod\'
Cargo project: !find . -maxdepth 1 -name \'Cargo.toml\'
OpenFeature SDK: !find . -maxdepth 1 \( -name package.json -o -name pyproject.toml -o -name Cargo.toml -o -name go.mod \) -exec grep -l 'openfeature' {} +
GOFF config: !find . -maxdepth 2 -name 'flags.goff.yaml' -o -name 'flags.goff.yml'
Docker compose: !find . -maxdepth 1 -name 'docker-compose*.yml' -o -name 'docker-compose*.yaml'
Project standards: !find . -maxdepth 1 -name \'.project-standards.yaml\'
Parameters
Parse from $ARGUMENTS:
--check-only: Report compliance status without modifications--fix: Apply all fixes automatically without prompting--provider <provider>: Override provider detection (goff, flagd, launchdarkly, split)
Version Checking
CRITICAL : Before configuring feature flags, verify latest SDK and provider versions using WebSearch or WebFetch:
OpenFeature JS SDK : Check
OpenFeature Python SDK : Check PyPI
Execution Execute this feature flag configuration workflow:
Step 1: Detect project language and existing setup Check for existing feature flag infrastructure:
Indicator Language Detected Provider @openfeature/server-sdk in package.jsonNode.js OpenFeature (check for provider) @openfeature/web-sdk in package.jsonBrowser JS OpenFeature Web @openfeature/react-sdk in package.jsonReact OpenFeature React openfeature-sdk in pyproject.tomlPython OpenFeature Python @openfeature/go-feature-flag-providerNode.js GO Feature Flag go-feature-flag-relay-proxy in docker-composeAny GO Feature Flag Relay flagd in docker-compose/k8sAny flagd provider
Step 2: Analyze current state Check for complete feature flag setup:
Verify OpenFeature SDK installed for project language
Check provider package installed
Verify provider initialized in application startup
Check evaluation context configuration
Check hooks configured (logging, telemetry)
For GOFF: verify flag configuration file exists, relay proxy configured
For flagd: verify container/service configured, gRPC/HTTP endpoints
Step 3: Generate compliance report Print a formatted compliance report:
Feature Flag Compliance Report
==============================
Project: [name]
Language: [detected]
Provider: [detected or None]
OpenFeature SDK: [status per check]
Provider Config: [status per check]
Infrastructure: [status per check]
Overall: [X issues found]
Recommendations: [list specific fixes]
If --check-only, stop here.
Step 4: Install SDK and configure provider (if --fix or user confirms) Based on detected language, install and configure the OpenFeature SDK with the selected provider. Use code templates from REFERENCE.md .
Install OpenFeature SDK and provider packages
Create feature flag client wrapper module
Create evaluation context helper
Create middleware for HTTP frameworks (Express, FastAPI, etc.)
Step 5: Create flag configuration Create flags.goff.yaml with example flags covering common patterns:
Simple boolean flag
Percentage rollout
Multi-variant flag (A/B test)
Environment-specific flag
User-specific override
Scheduled rollout
Step 6: Configure infrastructure
Create docker-compose entry for relay proxy (local development)
Optionally create Kubernetes manifests for production
Step 7: Create test configuration Create test file using in-memory provider for feature flag unit tests.
Step 8: Update standards tracking Update .project-standards.yaml:
components:
feature_flags: "2025.1"
feature_flags_sdk: "openfeature"
feature_flags_provider: "[goff|flagd|launchdarkly]"
Step 9: Print completion report Print a summary of all changes made including SDK installed, provider configured, flag file created, and next steps (start relay, initialize in app, use flags in code).
For detailed code templates, flag configuration patterns, and infrastructure manifests, see REFERENCE.md .
Agentic Optimizations Context Command Quick compliance check /configure:feature-flags --check-onlyAuto-fix with GOFF provider /configure:feature-flags --fix --provider goffValidate flag config goff lint --file flags.goff.yamlCheck relay proxy health `curl -s http://localhost:1031/health List configured flags `curl -s http://localhost:1031/v1/feature/flags Check SDK installed (JS) `jq -r '.dependencies
Flags Flag Description --check-onlyReport status without offering fixes --fixApply all fixes automatically without prompting --provider <provider>Override provider detection (goff, flagd, launchdarkly, split)
Examples
/configure:feature-flags
/configure:feature-flags --check-only
/configure:feature-flags --fix --provider goff
/configure:feature-flags --fix --provider launchdarkly
Error Handling
No package manager found : Cannot install SDK, provide manual stepsProvider not supported : List supported providers, suggest alternativesRelay proxy unreachable : Check Docker/K8s configurationInvalid flag syntax : Validate with goff lint before deployment
See Also 