Feature Flags Architect
Use when adding, retiring, or auditing feature flags.
Before & after
Same prompt, same agent — the only difference is the skill.
Reviewing your feature flags for technical debt is a good practice. Over time, you can accumulate flags that are no longer needed—they might be old experiments, beta features that went fully live, or toggles that never got cleaned up. This can add unnecessary complexity and make your codebase harder to maintain. You'd want to audit which flags are actually being used, which ones are stale or always-on, and plan how to remove them. You might also want to think about your flag naming conventions, how you organize them, and whether you're following best practices for flag lifecycle management. If you can give me access to your flags or share a list, I can help identify which ones to clean up.
FEATURE FLAG AUDIT REPORT STALE FLAG SCANNER RESULTS Stale flags (always-ON for 60+ days): • flag_v2_dashboard: Deployed June 15, 100% rollout since June 20, no kill-switch used -> Action: Remove from code, clean database record -> Estimate: 10 minutes (grep + git) • flag_experiment_pricing: A/B test ended May 30, still in codebase serving control -> Action: Clean up experiment wrapper, merge winner branch -> Estimate: 20 minutes (code refactor) Stale flags (always-OFF for 90+ days): • flag_legacy_auth: Disabled March 1, deprecated OAuth flow -> Action: Delete outright (never ships) -> Estimate: 5 minutes STALE FLAG CLEANUP PRIORITY 1. HIGH: Always-on flags (safe to remove, no user impact) 2. MEDIUM: Always-off + new code independent (can remove safely) 3. LOW: Kill-switch flags (keep; provide safety net) FLAG DEBT CLEANUP PLAN Week 1: Remove 3 always-on, 2 always-off flags Checklist: Code review, test on staging, confirm flag config deleted Week 2: Audit flag naming (standardize prefix, remove suffixes) Week 3: Document flag lifecycle policy (max 6 months, auto-archive) CLEANUP BEFORE/AFTER Before: 24 flags in codebase (12 stale, 8 active, 4 kill-switches) After: 14 flags (0 stale, 8 active, 6 kill-switches) -> Reduced flag count by 40%, improved maintainability PREVENTION □ Add flag retirement date at creation (auto-reminder at 180 days) □ Monthly audit job (list stale flags in Slack #dev-operations) □ Kill-switch flags only: Opt-in; all feature flags default to review for removal
About this skill
name: feature-flags-architect description: Use when Use when adding, retiring, or auditing feature flags.
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.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the feature-flags-architect skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Feature Flags Architect; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: feature-flags-architect
description: Use when adding, retiring, or auditing feature flags.
version: 1.0.0
category: Development / Engineering
author: AgentVolt
license: proprietary
tags:
- development
- engineering
---
# Feature Flags Architect
Plans and audits feature flag usage — rollout strategy, kill-switch design, and flag debt cleanup — so flags stay a delivery tool instead of permanent branching logic.
## When to use
… (sign up to view the full skill)Featured in
More development skills
View all Development skills →Generate
Scaffold code, tests, and boilerplate from a short spec.
Performance Profiler
Systematic performance profiling for Node.js, Python, and Go applications.
Threat Detection
Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.
Agent Harness
Turns a domain folder of skills into a bounded agentic loop: compile a goal into a task plan, execute with the domain's tools, verify every task, retry within a budget.