feature-flags

Implements feature flag lifecycle with OpenFeature SDK setup, progressive rollout, and CI expiry checks.

Updated May 21, 2026
One-click install
npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill feature-flags-cagesthrottleus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-flags
Source: https://github.com/CagesThrottleUs/private-ai-harness/tree/main/skills/feature-flags
Command: npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill feature-flags-cagesthrottleus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying new features directly to all users couples deployment with release, making risky launches, A/B tests, and instant rollbacks difficult. This Skill decouples deployment from release by setting up a complete feature flag system with naming conventions, rollout stages, and enforced cleanup. ## Core Features & Use Cases - Flag Registry and Naming Convention: Produces a registry at wiki/guides/feature-flag-registry.md with typed prefixes (release-, exp-, ops-, permission-), owners, and expiry dates. - OpenFeature SDK Setup: Generates vendor-neutral flag evaluation code for TypeScript/Node.js, Python, and Go that works with LaunchDarkly, GrowthBook, or environment variable backends. - Progressive Rollout Pattern: Implements consistent-hash percentage rollouts (1% → 5% → 25% → 50% → 100%) plus a CI hygiene check that blocks merges when flags expire. - Use Case: When shipping a new checkout flow, use this Skill to wrap it in a release-checkout-v2 flag, roll it out to 1% of users, monitor error rates at each stage, and enforce code cleanup within two sprints of reaching 100%. ## Quick Start Ask the AI to set up a feature flag with gradual rollout for the new feature you are about to deploy.

Frequently Asked Questions about feature-flags

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

FAQPage Schema
How do I set up feature flags for gradual rollout?

Register the flag with a typed prefix like release-, add OpenFeature SDK evaluation code with a fallback default, then increase the rollout percentage in stages from 1% to 100% while monitoring error rates and SLOs at each step.

What naming convention should feature flags use?

Use the pattern {type}-{feature}-{context} with lowercase and hyphens, such as release-checkout-v2 or ops-payment-stripe. Prefixes are release, exp, ops, and permission, and names should avoid version numbers.

Does OpenFeature work with LaunchDarkly and GrowthBook?

Yes, OpenFeature is a vendor-neutral CNCF standard whose SDK accepts providers for LaunchDarkly, GrowthBook, DevCycle, or plain environment variables. The same evaluation code works regardless of the backend.

How do I prevent stale feature flags from accumulating?

Assign every non-permanent flag an owner and expiry date in the registry, then run the CI hygiene check that parses the registry and fails the build when any flag is past its expiry. Remove flag code within two sprints of reaching 100% rollout.

When should I not use a feature flag?

Skip flags for bug fixes going to all users immediately, infrastructure changes, and docs-only changes. Flags add technical debt, so they are only justified for risky releases, experiments, kill switches, or permission gates.