feature-flag-manager

Define feature flags with rollout strategies and cleanup plans.

28|3|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/girijashankarj/cursor-handbook --skill feature-flag-manager-girijashankarj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-flag-manager
Source: https://github.com/girijashankarj/cursor-handbook/tree/main/.cursor/skills/backend/feature-flag-manager
Command: npx skills add https://github.com/girijashankarj/cursor-handbook --skill feature-flag-manager-girijashankarj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gate and manage features with flags to control rollout velocity, perform safe deployments, and clean up obsolete configurations without code changes.

Core Features & Use Cases

  • Gate features behind flags across environments (dev, staging, prod)
  • Support rollout strategies (boolean on/off, percentage, user segment) and canaries
  • Provide a cleanup workflow with documentation, tests, and maintenance guidance

Quick Start

Configure a new flag named FEATURE_EXAMPLE and enable it in staging to validate the rollout.

Frequently Asked Questions about feature-flag-manager

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

FAQPage Schema
How do I gate a feature behind a flag for a controlled rollout?

To gate a feature, identify the target code path, define a flag name, assign an owner, and apply gating logic. You then plan rollout stages across dev, staging, canary, and production with monitoring.

What rollout strategies can I use for feature flags?

Supported feature flag rollout strategies include boolean on/off toggles, percentage-based rollouts, and user segment targeting. These approaches enable safe deployments and canary releases without requiring code changes.

How do I manage feature flag cleanup after a rollout completes?

Feature flag cleanup requires maintaining a target removal date, testing both enabled and disabled code paths, and executing removal steps when rollout completes to eliminate obsolete configurations.

Do I need to test both enabled and disabled feature flag paths?

Yes, you must test both enabled and disabled feature flag paths. Maintaining tests for both states ensures gating logic functions correctly and prevents failures during rollout or final cleanup.

Can I use feature flags for canary deployments across staging and production?

Yes, feature flags support canary deployments. The workflow plans rollout stages from dev and staging to canary and production, enabling controlled deployment velocity and monitoring at each step.