Write a Feature Flag Cleanup Plan
Added 2026-11-03
Flags are easy to add and hard to remove; define removal conditions and an owner.
My system has accumulated feature flags (list below). Write a cleanup plan: 1) classify them as fully rolled out, abandoned, or long-running experiment; 2) give each class an action and timing; 3) point out which flags need data or compatibility checks before removal; 4) give a rule to detect stale flags automatically; 5) specify what must be attached to any new flag. Do not suggest deleting them all at once.
Site original
Chinese original
How to use
功能开关的技术债，来自「上线时说要删，之后再没人提」。
Try tweaking it
- Have it restate requirements and constraints before writing code.
- Ask for the smallest change plus a rollback path, not a full-file rewrite.
What you should get
- A minimal, runnable change with copy-ready code
- Impact list: which files and call sites must follow
Common mistakes
- Asking it to touch ten files at once, then losing track of what broke what.
- Pasting only the error, with no code or version, and getting an unfixable answer.
How to check the output
- The change runs, can be rolled back, and touches nothing unrelated.
- Edge cases (empty, oversized, concurrent) are covered or explained.
Where it works
- Good for: having it restate requirements and constraints, then propose the smallest runnable change.
- Watch out: include versions and a minimal reproduction with the error, or the fix may look plausible but not fit.