Use feature flags safely: match the flag type to its purpose (release/experiment/ops/permission), give every risky change a kill switch, roll out progressively gated by a health signal, evaluate deterministically and fail-safe, and manage the flag lifecycle to prevent debt.
Scanned 9/23/2026
Skills Directorynpx -y skills add mcorbett51090/RavenClaude --skill feature-flags --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Feature Flags?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mcorbett51090-feature-flags)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: feature-flags
description: "Use feature flags safely: match the flag type to its purpose (release/experiment/ops/permission), give every risky change a kill switch, roll out progressively gated by a health signal, evaluate deterministically and fail-safe, and manage the flag lifecycle to prevent debt."
---
# Feature Flags
## Type by purpose
| Type | Lifespan |
|---|---|
| Release | temporary (remove after launch) |
| Experiment | until decision |
| Ops (kill switch) | long-lived |
| Permission/entitlement | permanent |
Treating all flags the same grows debt.
## Safe rollout
Kill switch for every risky change (off without a deploy). Progressive 1% -> 10% -> 100% gated by a **health signal** (with devops-cicd/observability-sre).
## Evaluate + lifecycle
Deterministic + sticky; **fail-safe defaults** when the service is unreachable. Every temp flag: **owner + removal date**. Stale flags = combinatorial config debt + incidents.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
