How do I install the Feature Flags skill?

Run npx skillmds@latest add christopherlouet/feature-flags in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Feature Flags safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Feature Flags?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Feature Flags free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Feature Flags?

christopherlouet (@christopherlouet) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Feature Flags by christopherlouet — Agent Skill

Name: Feature Flags
Author: christopherlouet

File contents

Feature Flags (pointer)

SDK code, targeting rules syntax and dashboard integration drift on each vendor release and are canonical at:

LaunchDarkly — launchdarkly.com/docs (SaaS, advanced targeting + experimentation)
Unleash — docs.getunleash.io (self-hosted open source)
ConfigCat — configcat.com/docs (SaaS, generous free tier)
PostHog Feature Flags — posthog.com/docs/feature-flags (paired with product analytics; see also recipe)
OpenFeature — openfeature.dev (vendor-neutral SDK standard — use to avoid lock-in)

Use-case taxonomy (version-agnostic)

Type	Purpose	Lifetime
Release toggle	Deploy inactive code; flip on after smoke test	Short (days/weeks)
Experiment toggle	A/B test; emits exposure events for analysis	Bounded by experiment duration
Ops toggle	Circuit breakers, kill switches, degraded modes	Long-lived
Permission toggle	Feature gating by role/plan/cohort	Permanent (treat like config)

Choose by lifetime: short → cheap implementation, long-lived → invest in observability + naming discipline.

Foundation discipline (keep across releases)

Default OFF: every flag defaults to its conservative value (usually off). A flag that ships defaulting to ON is a hidden behaviour change.
2-sprint rule: remove release toggles within 2 sprints of full rollout. Stale flags accrue as tech debt — surface them via qa-tech-debt.
Log every evaluation: missing evaluation logs make debugging "why did user X see variant Y" impossible. Vendor SDKs offer this; if rolling custom, log it.
No business logic in flag values: a flag is a boolean (or enum); complex conditions belong in code paths the flag selects, not inside the flag service.
Naming convention: <scope>_<feature>_<variant> (e.g. checkout_express_enabled). Scope-first sorts/filters cleanly in dashboards.

---name: feature-flagsdescription: Feature flags and toggles management. Trigger when the user wants to implement feature flagging, A/B testing, or progressive deployment.---# Feature Flags (pointer)SDK code, targeting rules syntax and dashboard integration drift on each vendor release and are canonical at:- **LaunchDarkly** — [launchdarkly.com/docs](https://launchdarkly.com/docs) (SaaS, advanced targeting + experimentation)- **Unleash** — [docs.getunleash.io](https://docs.getunleash.io) (self-hosted open source)- **ConfigCat** — [configcat.com/docs](https://configcat.com/docs) (SaaS, generous free tier)- **PostHog Feature Flags** — [posthog.com/docs/feature-flags](https://posthog.com/docs/feature-flags) (paired with product analytics; see also recipe)- **OpenFeature** — [openfeature.dev](https://openfeature.dev) (vendor-neutral SDK standard — use to avoid lock-in)## Use-case taxonomy (version-agnostic)| Type | Purpose | Lifetime ||---|---|---|| **Release toggle** | Deploy inactive code; flip on after smoke test | Short (days/weeks) || **Experiment toggle** | A/B test; emits exposure events for analysis | Bounded by experiment duration || **Ops toggle** | Circuit breakers, kill switches, degraded modes | Long-lived || **Permission toggle** | Feature gating by role/plan/cohort | Permanent (treat like config) |Choose by lifetime: short → cheap implementation, long-lived → invest in observability + naming discipline.## Foundation discipline (keep across releases)- **Default OFF**: every flag defaults to its conservative value (usually off). A flag that ships defaulting to ON is a hidden behaviour change.- **2-sprint rule**: remove release toggles within 2 sprints of full rollout. Stale flags accrue as tech debt — surface them via `qa-tech-debt`.- **Log every evaluation**: missing evaluation logs make debugging "why did user X see variant Y" impossible. Vendor SDKs offer this; if rolling custom, log it.- **No business logic in flag values**: a flag is a boolean (or enum); complex conditions belong in code paths the flag selects, not inside the flag service.- **Naming convention**: `<scope>_<feature>_<variant>` (e.g. `checkout_express_enabled`). Scope-first sorts/filters cleanly in dashboards.## See also- `growth-ab-test` skill — experiment design, sample-size, exposure analysis (consumes experiment toggles)- `qa-tech-debt` — flag-debt scan surfaces stale flags past the 2-sprint window- `dev-tdd` — flag-gated code paths must be tested in BOTH states (on/off), not just the new path

Frequently asked questions

Feature Flags