feature-flags-architect
Use when adding, retiring, or auditing feature flags. Triggers on "add a flag", "ship behind a flag", "rollout plan", "kill switch", "stale flags", "flag debt", "LaunchDarkly", "GrowthBook", "Statsig", "Unleash", "Flipt", or any progressive-delivery question. Ships flag debt scanner, rollout planner, and kill-switch auditor (all stdlib Python), 4 references on flag taxonomy + provider trade-offs + rollout strategies + lifecycle, plus a /flag-cleanup slash command.
Profile →npx skills add alirezarezvani/claude-skills --skill feature-flags-architect --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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` ``` request → design → ship → ramp → cleanup → archive ``` 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 ```bash # 1. Audit the repo for flag debt python scripts/flag_debt_scanner.py --repo . --max-age-days 90 # 2. Plan a progressive rollout for a new flag python scripts/rollout_planner.py --population 100000 --target-percent 100 --duration-days 14 --strategy ring # 3. Verify every flag
- 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
- killswitchaudit.py
- Provider chooser (5 + DIY)
- Workflows
- Workflow 1: Ship a new feature behind a flag
- Workflow 2: Quarterly flag cleanup
- Workflow 3: Choose a provider
- Workflow 4: Design a kill switch
python scripts/flag_debt_scanner.py --repo . --max-age-days 90 python scripts/rollout_planner.py --population 100000 --target-percent 100 --duration-days 14 --strategy ring python scripts/kill_switch_audit.py --repo . --flag-doc docs/feature-flags.md python scripts/flag_debt_scanner.py --repo . --max-age-days 90 --format text python scripts/flag_debt_scanner.py --repo . --max-age-days 60 --format json > debt.json python scripts/rollout_planner.py --population 50000 --target-percent 25 --duration-days 7 --strategy linear python scripts/rollout_planner.py --population 1000000 --target-percent 100 --duration-days 30 --strategy log python scripts/kill_switch_audit.py --repo . --flag-doc runbooks/flags.md --format json
What does the feature-flags-architect skill do?
Use when adding, retiring, or auditing feature flags. Triggers on "add a flag", "ship behind a flag", "rollout plan", "kill switch", "stale flags", "flag debt", "LaunchDarkly", "GrowthBook", "Statsig", "Unleash", "Flipt", or any progressive-delivery question. Ships flag debt scanner, rollout planner, and kill-switch auditor (all stdlib Python), 4 references on flag taxonomy + provider trade-offs + rollout strategies + lifecycle, plus a /flag-cleanup slash command.
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill feature-flags-architect --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.