Feature Flag Naming Convention Generator

• Encode the flag’s type so anyone can tell a short-lived release toggle from a long-lived permission flag at a glance: release = gate an in-progress feature; remove after full rollout. exp = drive an a/b test; remove when the experiment concludes. ops = toggle a system behaviour or disable a feature in an incident. perm = long-lived; gate access by plan, role, or entitlement.
• Keep keys searchable — a consistent order (type, team, feature) makes flags greppable across code and dashboards.
• Record an owner and an expiry. The key names the flag; a comment or registry should name who owns it and when it should be removed. Stale flags are the biggest source of flag debt.
• Avoid encoding the environment in the key. The same flag key should resolve differently per environment via configuration, not via separate keys.

For the full lifecycle — types, rollouts, cleanup, and safe evaluation with Optimizely Feature Experimentation — read feature flag best practices for production.