Individual skill

feature-flag-lifecycle-manager

Establishes flag naming, fallback defaults, rollout rings, cleanup telemetry, and automated dead flag retirement.

skills/architecture/feature-flag-lifecycle-manager/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 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)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Manage feature flags from creation to deprecation, establishing standardized flag taxonomy, safe fallback defaults, phased rollout rings (canary/percentage/user groups), and automated dead-code cleanup to prevent technical debt accumulation.

## When to Use

- Introducing feature flag tooling (LaunchDarkly, Unleash, PostHog, custom Redis flags).
- Codebases clogged with hundreds of ancient, permanent boolean flags.
- Releasing risky changes using percentage rollouts and progressive ring deployments.

## What to Analyze

1. **Flag Taxonomy & Lifetime**: Release Toggle (short-lived, days) vs Experiment Toggle (weeks) vs Kill Switch (permanent) vs Permission Toggle.
2. **Safe Fallback Defaults**: Guaranteed fail-safe default value if the flag service is unreachable.