feature-flags

Implement dynamic feature flags with Redis-managed configuration for Express and FastAPI.

783|62|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/dadbodgeoff/drift --skill feature-flags-dadbodgeoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-flags
Source: https://github.com/dadbodgeoff/drift/tree/main/drift%20v1%20depreciated/skills/feature-flags
Command: npx skills add https://github.com/dadbodgeoff/drift --skill feature-flags-dadbodgeoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ioredis, redis, express, fastapi, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows you to manage the release of new features without requiring code deployments, enabling gradual rollouts, A/B testing, and immediate feature disabling.

Core Features & Use Cases

  • Gradual Rollouts: Release features to a small percentage of users first, then incrementally increase exposure.
  • A/B Testing: Test different versions of a feature with distinct user segments.
  • Kill Switches: Quickly disable problematic features in production to mitigate issues.
  • Targeted Releases: Enable features for specific users or groups (e.g., beta testers, premium users).

Quick Start

Use the feature-flags skill to check if the 'new_dashboard' feature is enabled for the current user.

Frequently Asked Questions about feature-flags

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

FAQPage Schema
How do I implement feature flags for gradual rollouts without redeploying code?

Feature flags enable dynamic feature availability without code deployments by managing configuration via Redis. This approach supports gradual rollouts by exposing features to a small percentage of users first, then incrementally increasing exposure.

Can I use dynamic configuration to set up A/B testing and kill switches in Express and FastAPI?

Yes, dynamic configuration supports A/B testing and kill switches through provided middleware for both Express and FastAPI. This allows you to test feature versions with distinct segments and quickly disable problematic features in production.

What is the best way to manage targeted feature releases for specific user segments?

Targeted releases are managed by enabling features for specific users or groups, such as beta testers or premium users. This dynamic configuration is handled through Redis, allowing immediate feature toggling without application restarts.

Do I need Redis to run feature flags for TypeScript and Python backends?

Yes, Redis is required as the dependency for managing the dynamic feature flag configuration. The system integrates with TypeScript/JavaScript and Python backends to control feature availability across your application stack.

How do kill switches work when disabling problematic features in production?

Kill switches provide immediate feature disabling to mitigate production issues. By toggling the configuration in Redis, you can instantly turn off problematic features across connected Express and FastAPI services without waiting for a new deployment.