Feature Flags Architect — Development

Feature Flags Architect provides end-to-end discipline for feature flags: classify them, ship them, ramp them, and retire them. It ships three stdlib Python tools (flag debt scanner, rollout planner, kill-switch auditor), four reference docs, and a /flag-cleanup slash command to enforce a controlled lifecycle and reduce flag debt.

engineering claude-code

📂 View skill on GitHub ↗ 🚀 How to use

✨ What it does

Classifies flags into 4 types (Release, Experiment, Operational, Permission) with lifespans and cleanup triggers
Scans code for flag references and flags debt based on age and usage
Generates phased rollout schedules with strategies (ring, linear, log, cohort)
Audits that every flag has a documented kill switch with owner, type, and monitoring
Provides provider comparison and decision rules
Includes a /flag-cleanup slash command for full cleanup workflow

🎯 When to use it

Adding a new feature flag and need a rollout plan
Auditing a codebase for stale or orphaned flags
Choosing a feature flag provider (LaunchDarkly, GrowthBook, Statsig, Unleash, Flipt, or DIY)
Designing a kill-switch path for a risky launch
Cleaning up flag debt before a release freeze

🚀 How to use

Trigger: /flag-cleanup

Trigger by asking to add a flag, ship behind a flag, plan a rollout, audit stale flags, or use the /flag-cleanup slash command. Provide your repository path, flag documentation file, and parameters like population size, target percent, duration, and strategy. Example prompts:

Add a new release flag for the checkout redesign and plan a ring rollout to 100% over 14 days for 100k users.
Audit this repo for flag debt older than 90 days.
Run /flag-cleanup

📄 Output: Produces a flag debt report, a rollout plan markdown table, a kill-switch audit report, and a cleanup plan.

📦 Add this skill to Claude Code

# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills

# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/engineering/skills/feature-flags-architect .claude/skills/feature-flags-architect

Skill source: engineering/skills/feature-flags-architect/SKILL.md

⚠️ Good to know

The scripts rely on common flag-call patterns and may miss custom flag implementations; requires git history for age detection and a flag documentation file for kill-switch audit.

❓ FAQ

What are the four flag types and which should be on a debt-scanner watchlist?

The four types are Release, Experiment, Operational, and Permission. Only Release and Experiment flags should be on a debt-scanner watchlist; Operational and Permission flags are long-lived by design.

How does the kill_switch_audit.py work?

It cross-references code-discovered flags against a documentation file (--flag-doc) to verify each flag has an entry declaring owner, type, kill-switch trigger, and monitoring dashboard, reporting missing docs as FAIL and missing fields as WARN.

What rollout strategies are available in rollout_planner.py?

The strategies are ring (1%→5%→25%→50%→100%), linear (constant rate), log (rapid early, slow tail), and cohort (by named cohort).

🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.