feature-flags-architect

Topics in the source

• Feature Flags Architect
• When to use
• Core principle: flags are a lifecycle, not an if
• Quick start
• The 4 flag types (taxonomy)
• The 3 Python tools
• flagdebtscanner.py
• rolloutplanner.py

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. 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 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. 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

This is an excerpt. Refer to the complete source and its current requirements.