feature-flags

Manage feature flag lifecycles with rollout, targeting, and cleanup.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/chavangorakh1999/sde-skills --skill feature-flags-chavangorakh1999
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-flags
Source: https://github.com/chavangorakh1999/sde-skills/tree/main/sde-execution/skills/feature-flags
Command: npx skills add https://github.com/chavangorakh1999/sde-skills --skill feature-flags-chavangorakh1999

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps manage the lifecycle of feature flags, ensuring that new features can be deployed safely, rolled out gradually, and cleaned up effectively to prevent technical debt.

Core Features & Use Cases

  • Flag Lifecycle Management: Guides through building, testing, canary releases, gradual rollouts, and cleanup.
  • Targeting & Rollout: Supports boolean, percentage-based, and user-specific targeting rules.
  • Use Case: When releasing a risky new checkout flow, use this Skill to define a rollout plan starting with 1% of users, monitoring metrics, and gradually increasing exposure until 100% adoption or a quick rollback if issues arise.

Quick Start

Use the feature-flags skill to plan the rollout for the 'new-checkout-flow' feature, starting with 5% of users.

Frequently Asked Questions about feature-flags

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

FAQPage Schema
How do I plan a gradual rollout for a risky new feature?

Manage feature flag lifecycles by implementing boolean, percentage, and attribute-based targeting rules. This prevents technical debt by guiding creation, rollout strategies, and timely cleanup of obsolete flags in your software development workflow.

How do I execute a canary release for new functionality?

Execute a canary release by applying percentage-based rollout strategies to expose new functionality to a small user subset. Monitor key metrics during this phase to ensure stability before increasing traffic or initiating a rollback procedure.

Can I target specific users instead of using a percentage rollout?

Yes, you can target specific users by implementing attribute-based targeting rules instead of percentage-based rollouts. This allows precise control over which user segments see a feature during phased releases.

How do I prevent technical debt from accumulating feature flags?

Prevent feature flag technical debt by managing the entire flag lifecycle, including structured cleanup procedures. Removing obsolete flags after a rollout completes ensures your codebase remains maintainable and free of dead code.

What is the best way to roll back a feature if metrics fail during deployment?

The best way to roll back a failing feature is to use predefined rollback procedures within your feature flag management system. This allows you to instantly revert the rollout strategy or disable the flag without redeploying code.

What targeting rules are available for feature flag rollout strategies?

Available targeting rules for rollout strategies include boolean toggles, percentage-based distributions, and attribute-based user targeting. These options enable flexible control over feature deployment and gradual adoption across different segments.