Individual skill
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.
engineering/skills/feature-flags-architect/SKILL.md
Source commit 8f082544116fc0d014188e521ca40304cdfc86b0
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 29,593
- Repository last updated
- Nov 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agentic-ai Repository topic
- anthropic-claude Repository topic
- claude-ai Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- claude-code-skills Repository topic
- ai-coding-agent Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- openai-codex Repository topic
- feature-flags Declared skill tag
- progressive-delivery Declared skill tag
- rollout Declared skill tag
- kill-switch Declared skill tag
- launchdarkly Declared skill tag
- growthbook Declared skill tag
- statsig Declared skill tag
- unleash Declared skill tag
- flipt Declared skill tag
- release-engineering Declared skill tag
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 9,587 bytesSKILL.mdcore · 9,587 bytesSKILL.mdcore · 9,587 bytesSKILL.mdcore · 9,587 bytesSKILL.mdcore · 9,587 bytesassets/flag_request_template.mddoc · 1,770 bytesreferences/flag_lifecycle.mddoc · 5,869 bytesreferences/flag_taxonomy.mddoc · 4,511 bytesreferences/provider_comparison.mddoc · 5,148 bytesreferences/rollout_strategies.mddoc · 5,024 bytesscripts/flag_debt_scanner.pyruns · 4,827 bytesscripts/kill_switch_audit.pyruns · 5,000 bytesscripts/rollout_planner.pyruns · 4,573 bytes
Read excerpt
# 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`