Skip to content
Log in

Feature Flag Plan

Plans a flag with a removal date, because flags are permanent by default and a codebase of them is unmaintainable.

0

Share this prompt

Free — no card needed

Create a free account

to open Feature Flag Plan — and the other 364 prompts across 21 categories.

We store your email address to send these. We never sell it or pass it to advertisers. Withdraw at any time. Privacy Policy.

Already have an account?

CategoryCodingForDevelopers, OperatorsTested onClaudeChatGPT

Running it, start to finish

  1. Classify the flag and set its removal date in the ticket.
  2. Check it in one place as high up as you can.
  3. Write the removal plan before you write the feature.

What you get back

The output this produces, every time.

  • Classifies the flag by lifespan, since release, experiment and operational flags have different rules.
  • Sets the removal date at creation, without which the flag is permanent.
  • Writes the removal plan up front, turning a later archaeology exercise into a small task.

Getting better results

Where this usually goes wrong, and how to avoid it.

  • Check as high up as possible. One branch at a boundary is removable. Twelve scattered conditionals are twelve chances to leave one behind.
  • Fail towards the old behaviour. When the flag service is unreachable, the safe default is what was working yesterday.
  • Remove an old flag while you are in there. Section 8 costs almost nothing when you are already in that code and is never scheduled on its own.

More Coding prompts

All Coding →

Written for The AI University. Every prompt in this library is original work — authored, tested and revised here, not collected from elsewhere. 365 of them, free with an account.