manage-feature-flags

Manage feature flag lifecycle with reactive stores and declarative gating elements.

4|1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/lushly-dev/afd --skill manage-feature-flags
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-feature-flags
Source: https://github.com/lushly-dev/afd/tree/main/.claude/skills/manage-feature-flags
Command: npx skills add https://github.com/lushly-dev/afd --skill manage-feature-flags

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive framework for defining, implementing, and managing feature flags, ensuring controlled rollouts and clean codebases.

Core Features & Use Cases

  • Flag Definition: Define flags with schemas for type, expiry, and dependencies.
  • Gating: Implement declarative gates for frontend UI and handler delegation for backend logic.
  • Lifecycle Management: Streamline the process of adding, validating, expiring, and cleaning up flags.
  • Use Case: Introduce a new UI component by defining a release flag, gating the component with a flag-gate element, and ensuring it's removed after a successful rollout.

Quick Start

Use the manage-feature-flags skill to add a new release flag named 'new-dashboard-layout' with an expiry date of next month.

Frequently Asked Questions about manage-feature-flags

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

FAQPage Schema
How do I implement feature flags for controlled UI rollouts?

Feature flags enable controlled rollouts by defining release flags with expiry schemas and gating UI components declaratively using custom elements. This ensures new layouts are safely introduced and easily toggled without redeploying code.

What is the best way to manage feature flag lifecycle and prevent stale flags?

Managing the feature flag lifecycle requires defining schemas with expiry dates and conducting hygiene compliance checks. This process streamlines adding, validating, and cleaning up stale flags to maintain a clean codebase.

How does backend handler delegation work for feature flag gating?

Backend handler delegation for feature flag gating swaps server-side logic implementations based on flag state. It uses a flag store singleton to route execution to different handlers, allowing safe backend logic swaps.

Can I define dependencies and expiry dates for feature flags?

Yes, feature flag definitions support schemas for type, expiry, and dependencies. This allows you to set automatic expiration dates and establish prerequisite relationships between flags for robust release management.

When do I need a kill switch for feature management?

A kill switch is needed in feature management to instantly disable a problematic release. By defining a flag and gating the component, you can deactivate the feature reactively through the flag store without code changes.

Does this feature flag framework require external dependencies?

No, this feature flag framework operates without external dependencies. It uses internal reactive stores, declarative gating elements, and handler delegation patterns to manage release gating and lifecycle independently.