feature-flag

Create default-OFF feature flags with guard checks and rollout plans.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill feature-flag-jnlanahan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-flag
Source: https://github.com/jnlanahan/Product-Agents-and-Skills/tree/main/skills/6-Deploy-Feature-Flag
Command: npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill feature-flag-jnlanahan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of shipping new functionality reliably by preventing accidental exposure, enabling kill-switch control, and supporting gradual rollout strategies.

Core Features & Use Cases

  • Feature-flag wiring for staged control: Gate a new UI or backend behavior behind a flag that defaults OFF and can be enabled progressively.
  • Multi-provider flag detection and extension: Detect existing feature-flag tooling (including PostHog as the preferred provider) and extend it rather than duplicating systems.
  • Rollout planning and verification: Generate a rollout plan and ensure the feature behaves correctly for both ON and OFF targets, including kill-switch validation.

Use case: You want to launch a “new dashboard v2” to a small percentage of users first, measure impact, and instantly disable it if errors spike.

Quick Start

Use the feature-flag skill to add a PostHog flag that defaults OFF, wire the server and/or client code to respect it, and save a staged rollout plan you can verify in staging.

Frequently Asked Questions about feature-flag

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

FAQPage Schema
How do I implement a staged rollout for a new feature?

A staged rollout gates a new feature behind a default-OFF flag, wiring clean guard checks in your code to enable progressive exposure while tracking user impact and maintaining kill-switch control.

Can I use PostHog for server-side feature gating and A/B testing?

Yes, PostHog is the preferred provider for server-side feature gating, allowing you to manage A/B testing and staged rollouts by extending existing flag tooling rather than duplicating systems.

What's the best way to set up a kill switch for a dark launch?

The best way to set up a kill switch for a dark launch is to implement a default-OFF feature flag, verify ON/OFF behavior thoroughly, and generate a rollout plan artifact to instantly disable the feature if errors spike.

How does feature flag tracking work for progressive delivery?

Feature flag tracking for progressive delivery works by creating a default-OFF flag, wiring clean guard checks to control exposure, and tracking user interactions to verify behavior for both ON and OFF targets.

Do I need a rollout plan artifact to manage feature flags?

Yes, generating a rollout plan artifact is required to document your staged rollout strategy, verify ON/OFF behavior, and ensure you can safely validate kill-switch control before launching to production.

Why should I gate a new UI behavior instead of shipping it directly?

You should gate a new UI behavior to prevent accidental exposure, enable instant kill-switch control if errors spike, and support gradual rollout strategies to measure impact safely before a full launch.