feature-flags

Manage feature flags and controlled rollouts for ASP.NET Core services.

4|1|Updated Mar 15, 2026

Search Tags:#configuration #dotnet #aspnetcore #rollout #feature-flags #feature-management #azure-app-configuration

Ready to run

npx skills add https://github.com/FaysilAlshareef/dotnet-ai-kit --skill feature-flags-faysilalshareef

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-flags
Source: https://github.com/FaysilAlshareef/dotnet-ai-kit/tree/main/skills/infra/feature-flags
Command: npx skills add https://github.com/FaysilAlshareef/dotnet-ai-kit --skill feature-flags-faysilalshareef

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feature flags and controlled rollouts are hard to coordinate across services and environments, leading to risky releases and feature debt.

Core Features & Use Cases

Centralized feature flag definitions and removal targets across ASP.NET Core services
Support for TimeWindow, Targeting, and Percentage rollout filters
Azure App Configuration integration and appsettings-based configuration
Audit and governance features to track flag lifecycles and kill switches
Easy instrumentation with FeatureManagement and custom filters

Quick Start

Install and configure Microsoft.FeatureManagement in your ASP.NET Core project, register the required filters, and define your feature flags with removal targets to enable safe, gradual releases.

Frequently Asked Questions about feature-flags

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

FAQPage Schema

How do I configure feature flags for gradual rollouts in ASP.NET Core?▼

Feature flags in ASP.NET Core use Microsoft.FeatureManagement to apply runtime toggles and gradual deployments. You register filters like TimeWindow or Percentage and define toggles in appsettings to enable safe, controlled releases across services.

What is a feature flag removal target and when do I need one?▼

A feature flag removal target is an auditing mechanism that tracks a toggle's lifecycle to enforce cleanup. You need removal targets to prevent feature debt and manage emergency kill switches effectively across your .NET applications.

Can I use Azure App Configuration to manage feature management across multiple services?▼

Yes, Azure App Configuration integration is supported for centralized feature management. It allows you to coordinate feature flags and controlled rollouts across multiple ASP.NET Core services and environments from a single source.

Does this feature management setup support custom targeting filters?▼

Yes, the feature management setup supports custom feature filters and targeting policies. You can instrument custom filters alongside built-in TimeWindow, Targeting, and Percentage rollout filters for precise control over your .NET application releases.

What's the best way to implement an emergency kill switch for a deployed ASP.NET Core API?▼

The best way to implement an emergency kill switch is by configuring a feature flag with a targeting policy or custom filter. This enables immediate runtime toggling of API functionality without redeploying your ASP.NET Core service.

Why use time window filters for feature rollouts instead of manual deployments?▼

Time window filters automate scheduled feature activations within your rollout strategy, reducing human error. They allow you to enable or disable toggles at predetermined times without requiring manual code deployments or configuration updates.