feature-flag-lifecycle
Skill1 starsChanged 3 months agoMITView on GitHub
Manage feature flag add, rollout, and removal. Use when introducing flags or cleaning old flags, or Chinese "特性开关", "feature flag", "灰度", "删 flag". Prevent eternal flags.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Indium-AI-Labs/indium-agentkittheir own version, first seen Nov 1, 2026
- Ionate-Technologies/indium-agentkittheir own version, first seen Oct 20, 2026
- robisson/build-like-amazon-agent-skillstheir own version, first seen Oct 5, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- Indium-AI-Labs/indium-agentkit★ 18same name
- Ionate-Technologies/indium-agentkit★ 17same name
- robisson/build-like-amazon-agent-skills★ 16same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-diff-ship-checkSkill
- customer-bug-to-failing-testSkill
- dead-code-safe-deleteSkill
- env-drift-checkSkill
- flake-vs-bug-triageSkill
- minimal-repro-packSkill
- secret-redact-before-aiSkill
- using-ship-guard-skillsSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Cleanup ticket: remove flag + dead branches after 100% stable.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Feature Flag Lifecycle
Overview
Flags without owners become permanent debt. Plan create → rollout → cleanup.
Steps
- Create: name, default, owner, success metric, expiry target date.
- Code: single check site if possible; avoid scattered
if (flag)without abstraction. - Rollout: stages (0% → internal → % → 100%), kill switch.
- Cleanup ticket: remove flag + dead branches after 100% stable.
- Inventory: list existing flags touched by this change; any overdue expiry?
Exit criteria
- Owner + expiry
- Rollout stages
- Cleanup plan
- No new flag without default and scope
Anti-patterns
- Flag forever “just in case”
- Nested flags for one feature
Output template
## Flag plan
- Name / default / owner / expiry
- Rollout: ...
- Cleanup PR criteria: ...
- Overdue flags nearby: ...Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.