メニュー
Feature flags with OpenFeature and providers (GOFF, flagd, LaunchDarkly). Use when setting up the SDK, configuring a relay proxy, or adding flag test helpers.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/laurigates/claude-plugins --skill configure-feature-flagsコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
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.
SKILL.md を表示中
SOC 職業分類に基づく
| 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 |
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)