Agent skill · software engineering · alirezarezvani
feature-flags-architect
Use before adding, rolling out or retiring a feature flag or kill switch, or when flag debt piles up. Plans the rollout with rollout_planner.py, finds stale flags with flag_debt_scanner.py and audits kill switches with kill_switch_audit.py.
Why this skill is useful
Adds 3 executable Python scripts for auditing flag debt, planning rollouts, and verifying kill switches that enhance feature flag management capabilities.
What it needs
Requires python installed locally. About 6k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.
What this skill does
Feature Flags Architect End-to-end discipline for feature flags: classify them, ship them, ramp them, and retire them. Most teams treat flags as throwaway if-statements; this skill treats them as a controlled lifecycle with measurable debt. When to use Adding a new flag and need a rollout plan Auditing a codebase for stale or orphaned flags Choosing a flag provider (LaunchDarkly vs GrowthBook vs Statsig vs Unleash vs Flipt vs build-your-own) Designing a kill-switch path for a risky launch Cleaning up flag debt before a release freeze Reviewing whether a feature should ship behind a flag at all Core principle: flags are a lifecycle, not an if Flags that skip cleanup become debt: dead branches, stale defaults, untested code paths, unbounded blast radius. The three scripts in this skill enforce the lifecycle. Quick start The 4 flag types (taxonomy) Different flag types have different lifespans and ownership. Misclassifying creates debt. Type Purpose Typical lifespan Owner Cleanup trigger --- --- --- --- --- Release Hide unfinished features in production days–weeks Eng 100% rollout reached Experiment A/B test variants weeks Product/Marketing Test concluded; winner picked Operational Circuit breakers, perf toggles, kill switches months–years Eng/SRE Replaced by autoscaling/feature retirement Permission Entitlements per user/account/plan years (permanent) Product Plan/role removed Only Release and Experiment flags should be on a debt-scanner watchlist. Operational and Permission flags are by design long-lived. See references/flagtaxonomy.md for decision tree. The 3 Python tools All three are stdlib-only. Run with --help. flagdebtscanner.py Finds flags older than --max-age-days with low usage, suggesting candidates for cleanup. Detection heuristic: 1. Walk --repo for code references matching common flag-call patterns: flag("..."), isFlagEnabled("..."), featureFlag("..."), getFlag("...") client.variation("...", ...), unleash.isEnabled("..."), growthbook.feature("...") 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/feature-flags-architect--b067dd