skills.rest
vTRKA
vTRKACOMMUNITY
Explore all skills by this author →
GitHub

feature-flag-rollout

Designs staged feature-flag rollouts with kill-switch, percentage, cohort, or dark-launch options.

Updated Apr 27, 2026
Search Tags:#feature flags#SLI#release safety#kill-switch#staged rollout#rollback criteria#cohort targeting
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill feature-flag-rollout
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-flag-rollout
Source: https://github.com/vTRKA/supervibe/tree/main/skills/feature-flag-rollout
Command: npx skills add https://github.com/vTRKA/supervibe --skill feature-flag-rollout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feature Flag Rollout prevents risky releases from turning into production incidents by forcing a complete rollout plan (kill-switch/percentage/cohort), explicit success metrics, and testable rollback criteria before any durable work proceeds.

Core Features & Use Cases

  • Rollout shape selection: Chooses kill-switch, percentage, cohort, or dark-launch based on worst plausible outcomes and audience targeting needs.
  • Rollback contract + gates: Defines numeric SLI thresholds, a wall-clock rollback budget, and qualitative tripwires for incident-grade failures.
  • Staged execution planning: Specifies stage steps with soak times and advance gates, plus a cleanup deadline to prevent long-lived flag debt.
  • Evidence-first handoff: Blocks completion when required source evidence, owner approval, validator output, or runtime receipt is missing, returning a structured BLOCKED response.

Quick Start

Ask your AI to plan a staged rollout for a new risky behavior with a kill-switch and measurable rollback gates using feature-flag-rollout.

Frequently Asked Questions about feature-flag-rollout

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

FAQPage Schema
How do I design a safe staged rollout for a feature behind a feature flag?▼

Designing a safe staged rollout involves selecting a rollout shape like kill-switch, percentage, cohort, or dark-launch, and defining measurable rollback criteria with explicit SLI thresholds and advancement gates before deployment.

What rollback criteria should I define for a feature flag release?▼

Rollback criteria for a feature flag release should include numeric SLI thresholds, a wall-clock rollback budget, and qualitative tripwires to catch incident-grade failures during the staged advancement gates.

When do I need a kill-switch versus a cohort rollout for my release?▼

You need a kill-switch for immediate incident mitigation when worst plausible outcomes are high severity, whereas a cohort rollout targets specific audience segments when you need controlled, staged expansion of new flagged behavior.

How do I prevent feature flag debt after a staged rollout?▼

Prevent feature flag debt by specifying a cleanup deadline during rollout planning, ensuring that long-lived flagged behavior is retired after passing staged execution gates and soak times.

What happens if required evidence is missing when planning a feature flag rollout?▼

If required source evidence, owner approval, or validator output is missing during rollout planning, the process blocks completion and returns a structured BLOCKED response to enforce evidence-first handoff.

Can I use a dark-launch rollout shape for testing new behavior before a full release?▼

Yes, a dark-launch rollout shape tests new flagged behavior in production without user visibility, allowing you to validate runtime receipts and gather evidence before advancing to visible staged rollout gates.

Related Skills

Explore More Product & Management Skills→
cosmixcosmix
53

code-migration

Plan staged code migrations with rollback and feature flags.

Community
Advanced
petrkindlmannpetrkindlmann
64

performance-testing

Measure load capacity, response times, and Core Web Vitals in CI pipelines.

Community
Advanced
gaofeng21cngaofeng21cn
8

opl-connect-connector-receipt-auditor

Audit OPL Connect connector receipt candidates for evidence completeness and gap classification.

Community
Intermediate
sun2443sun2443

deploy-checklist

Generate a pre-deployment checklist with deploy, post-deploy, and rollback sections.

Community
Intermediate