capability-manage-flags

Manages feature flag lifecycle including creation, activation, deactivation, and cleanup across codebases.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/learnn-com/engineering-kb --skill capability-manage-flags-learnn-com
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: capability-manage-flags
Source: https://github.com/learnn-com/engineering-kb/tree/main/.skills/capability-manage-flags
Command: npx skills add https://github.com/learnn-com/engineering-kb --skill capability-manage-flags-learnn-com

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature flags accumulate as technical debt when teams create them but never track, deactivate, or remove them. This Skill provides a structured, idempotent workflow to manage the full feature flag lifecycle so stale flags get detected and cleaned up instead of lingering in the codebase. ## Core Features & Use Cases - Flag Inventory & Status: Scans the codebase for flag configuration files, SDK usage, and flag service integrations to build a complete inventory with type, status, references, and age. - Lifecycle Actions: Supports create, activate, deactivate, cleanup, and status actions, with idempotent behavior that shows current state instead of duplicating existing flags. - Stale Flag Detection & Cleanup: Flags inactive for more than 30 days are marked stale, and cleanup removes flag conditionals while keeping the winning code path after explicit confirmation. - Use Case: A team finishing a gradual rollout invokes the status action, finds three stale experiment flags, and uses the cleanup action to remove the flag checks from 12 files while keeping the flag-on behavior. ## Quick Start Ask the AI to scan the repository for all feature flags and show their current status, or to create a new release flag named according to project conventions.

Frequently Asked Questions about capability-manage-flags

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clean up stale feature flags in my codebase?▼

Run the cleanup action on a flag to get a removal plan showing affected files, then confirm to strip flag conditionals while keeping the winning code path. Flags inactive for more than 30 days are automatically flagged as stale cleanup candidates.

How to create a feature flag following project conventions?▼

Use the create action, which prompts for flag name, type (Release, Experiment, Ops, Permission), default value, and scope. It adds the flag to configuration, generates a wrapper utility, and inserts a cleanup reminder comment with an expected removal date.

Does this work with LaunchDarkly, Unleash, or Split?▼

Yes, the detection step scans for flag service configurations including LaunchDarkly, Unleash, and Split, as well as custom SDK usage like isEnabled() calls. If no flag service is configured, it falls back to code-level flags using constants or config files.

What happens if I try to create a flag that already exists?▼

The Skill is idempotent: invoking create on an existing flag shows its current state and offers lifecycle actions instead of re-creating it. Similarly, activating an already-active flag simply confirms the current state.

Can feature flag cleanup break active code paths?▼

Cleanup always requires explicit developer confirmation before modifying files. If removal would break active code paths, the Skill warns and refuses to proceed without confirmation, and it preserves the winning flag-on or flag-off behavior.