Feature Flag Lifecycle Policy

Control flag sprawl and risk.

Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Write a feature flag lifecycle policy. Flag system in use: [FLAG_SYSTEM]. Number of current flags and how old they are: [FLAG_INVENTORY]. Services and teams involved: [TEAMS].

Define flag types (release, experiment, ops, permission) with a different expiry for each, naming rules, required metadata (owner, created, expected removal date, linked ticket), default values and fail-safe behaviour if the flag service is down, rollout steps with percentages, and removal procedure including code clean-up. Provide a table of types with their rules and a sample flag record. Add an audit query concept to find flags past expiry and a monthly clean-up ritual. Include testing guidance for combinations and a note on flags that guard security-sensitive changes.

Add a sample monthly clean-up report as a table, with flag name, owner, age, last evaluated, and recommended action, filled with four invented rows. Describe how to test with the flag on and off in CI, how to avoid long-lived flags becoming permanent configuration, and a rule that a flag in front of a database migration needs a removal date agreed before the migration ships.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

• CD