feature-flags

Manage feature flag rollouts with canary percentages and rollback rules.

7|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill feature-flags-camilooscargbaptista
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-flags
Source: https://github.com/camilooscargbaptista/cto-toolkit/tree/main/feature-flags
Command: npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill feature-flags-camilooscargbaptista

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides practices and implementation patterns to manage feature flags so teams can deploy changes safely with controlled rollouts, experiments, and emergency kill switches while avoiding long-lived tech debt.

Core Features & Use Cases

  • Rollout patterns: deterministic percentage canaries and staged ramps with monitoring checkpoints and rollback rules.
  • Flag types & lifecycle: guidance for release, experiment, ops, and permission flags with owner, expiry, and cleanup policies.
  • Implementation guidance: config-based and database-backed approaches, deterministic user hashing for percentage rollouts, tenant and user scoping, and automated cleanup recommendations.
  • Use case: perform a 10% canary rollout of a new billing UI, monitor error and latency metrics for 24 hours, then advance or rollback and schedule flag removal after stable production use.

Quick Start

Create a new feature flag disabled by default, enable it for internal testers, then request a 10% canary rollout and monitor metrics for 24 hours.

Frequently Asked Questions about feature-flags

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

FAQPage Schema
How do I manage feature flag rollouts for a canary deployment?

Manage feature flag rollouts using deterministic percentage hashing to enable staged canary releases, applying monitoring checkpoints and rollback rules to gradually release changes to a subset of users. You can then advance or rollback based on production metrics.

What is the best way to prevent technical debt with long-lived feature toggles?

Prevent technical debt from feature toggles by enforcing owner and expiration metadata alongside automated cleanup processes. This ensures flags are scheduled for removal after stable production use, avoiding accumulation in the codebase.

How do I configure an emergency kill switch for production software?

Configure an emergency kill switch by implementing ops flags within your feature flag lifecycle. This allows you to instantly disable a feature in production environments without deploying new code, acting as a safety mechanism for critical issues.

Can I scope feature flags to specific tenants or users for A/B testing?

Yes, you can scope feature flags to specific tenants or users for A/B testing. The Skill provides implementation guidance for tenant and user scoping, allowing targeted gating and experiments alongside percentage-based rollouts.

Does trunk-based development work with feature flag lifecycles?

Yes, feature flag lifecycles support trunk-based development workflows by allowing incomplete features to be safely merged to the main branch. Permission and release flags gate access, ensuring code remains hidden until ready for staged production rollouts.