From configure-plugin
Checks and configures OpenFeature feature flag infrastructure with providers (GOFF, flagd, LaunchDarkly, Split) in JavaScript, Python, Go, Rust projects. Audits setup, adds SDKs, relay proxies for Docker/Kubernetes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/configure-plugin:configure-feature-flagsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Check and configure feature flag infrastructure using the OpenFeature standard with pluggable providers.
Check and configure feature flag infrastructure using the OpenFeature standard with pluggable providers.
| 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) |
find . -maxdepth 1 -name \'package.json\'find . -maxdepth 1 -name \'pyproject.toml\'find . -maxdepth 1 -name \'go.mod\'find . -maxdepth 1 -name \'Cargo.toml\'find . -maxdepth 1 \( -name package.json -o -name pyproject.toml -o -name Cargo.toml -o -name go.mod \) -exec grep -l 'openfeature' {} +find . -maxdepth 2 -name 'flags.goff.yaml' -o -name 'flags.goff.yml'find . -maxdepth 1 -name 'docker-compose*.yml' -o -name 'docker-compose*.yaml'find . -maxdepth 1 -name \'.project-standards.yaml\'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)CRITICAL: Before configuring feature flags, verify latest SDK and provider versions using WebSearch or WebFetch:
Execute this feature flag configuration workflow:
Check for existing feature flag infrastructure:
| Indicator | Language | Detected Provider |
|---|---|---|
@openfeature/server-sdk in package.json | Node.js | OpenFeature (check for provider) |
@openfeature/web-sdk in package.json | Browser JS | OpenFeature Web |
@openfeature/react-sdk in package.json | React | OpenFeature React |
openfeature-sdk in pyproject.toml | Python | OpenFeature Python |
@openfeature/go-feature-flag-provider | Node.js | GO Feature Flag |
go-feature-flag-relay-proxy in docker-compose | Any | GO Feature Flag Relay |
flagd in docker-compose/k8s | Any | flagd provider |
Check for complete feature flag setup:
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.
Based on detected language, install and configure the OpenFeature SDK with the selected provider. Use code templates from REFERENCE.md.
Create flags.goff.yaml with example flags covering common patterns:
Use flag templates from REFERENCE.md.
Create test file using in-memory provider for feature flag unit tests.
Update .project-standards.yaml:
components:
feature_flags: "2025.1"
feature_flags_sdk: "openfeature"
feature_flags_provider: "[goff|flagd|launchdarkly]"
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.
| Context | Command |
|---|---|
| Quick compliance check | /configure:feature-flags --check-only |
| Auto-fix with GOFF provider | /configure:feature-flags --fix --provider goff |
| Validate flag config | goff lint --file flags.goff.yaml |
| Check 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 |
| Flag | Description |
|---|---|
--check-only | Report status without offering fixes |
--fix | Apply all fixes automatically without prompting |
--provider <provider> | Override provider detection (goff, flagd, launchdarkly, split) |
# Check compliance and offer fixes
/configure:feature-flags
# Check only, no modifications
/configure:feature-flags --check-only
# Auto-fix with GO Feature Flag provider
/configure:feature-flags --fix --provider goff
# Configure for LaunchDarkly
/configure:feature-flags --fix --provider launchdarkly
goff lint before deployment/configure:all - Run all compliance checks/configure:sentry - Error tracking (often used with feature flags for rollback)npx claudepluginhub laurigates/claude-plugins --plugin configure-pluginIntegrates OpenFeature SDK for vendor-agnostic feature flags with standardized API, covering Node.js installation, evaluation, providers, and hooks for A/B testing and canary releases.
Manages feature flag lifecycle: detect flags in codebases, classify categories, and design rollout strategies with naming conventions. For auditing stale flags or planning new flag architecture.
Creates and configures LaunchDarkly feature flags that match existing codebase patterns. Guides exploration of SDK usage, naming conventions, and flag types before creation.