feature-flag-staged-cutover

Name: feature-flag-staged-cutover
Availability: InStock
Author: elchananteitzwork-a11y

Enforces recorded flag, rollback, and validation evidence before milestone cutover.

Updated Jun 11, 2026

Search Tags:#feature flag #rollback plan #release discipline #milestone validation #staged cutover #activation criteria

Ready to run

npx skills add https://github.com/elchananteitzwork-a11y/supplement-intelligence --skill feature-flag-staged-cutover-elchananteitzwork-a11y

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-flag-staged-cutover
Source: https://github.com/elchananteitzwork-a11y/supplement-intelligence/tree/main/.claude/skills/feature-flag-staged-cutover
Command: npx skills add https://github.com/elchananteitzwork-a11y/supplement-intelligence --skill feature-flag-staged-cutover-elchananteitzwork-a11y

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Milestones often get marked "live" without any record of how to turn them off, what justified activation, or who approved the change, making regressions hard to reverse. This Skill formalizes the cutover discipline so no feature flag flips without documented evidence. ## Core Features & Use Cases - Five-Point Cutover Checklist: Requires a recorded flag name, activation criteria, rollback plan, validation evidence, and explicit owner approval before any milestone moves from validated to live. - Scope Guardrails: Distinguishes Planner-owned cutover decisions from implementing Agents that only record toggle mechanics, and excludes routine bug fixes, test-only changes, and build-only scoped work. - Use Case: A Planner is about to mark milestone M2.14 complete after validation. The Skill requires the master plan to record the exact flag identifier, the validation report link, the rollback steps, and the project owner's sign-off before the status changes. ## Quick Start Ask the assistant to apply the feature flag staged cutover checklist before marking the current milestone live, recording the flag name, rollback plan, and validation evidence.

Frequently Asked Questions about feature-flag-staged-cutover

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

FAQPage Schema

How do I safely cut over a feature flag to production?▼

Record five items before flipping the flag: the exact flag identifier, activation criteria based on validation results, a rollback plan with named executors, a link to validation evidence, and explicit project owner approval. Only then mark the milestone live.

What should a feature flag rollback plan include?▼

A rollback plan should state the exact steps to revert the flag if the cutover causes a regression and identify who is authorized to execute those steps. It must be recorded before activation, not improvised after an incident.

When should I not use a staged cutover checklist?▼

Skip it for routine bug fixes with no flag, work explicitly scoped as build-only with no cutover in its R&D document, and test-only changes. The discipline applies only when a milestone moves from validated to live.

Can an implementing agent decide a milestone is ready for cutover?▼

No. An implementing Agent only records the mechanics of the toggle it is wiring, such as the flag name and rollback path. The readiness decision is Planner-owned and requires the project owner's explicit recorded approval.

Why is marking a milestone complete without a rollback record risky?▼

Without a recorded flag name and rollback path, a post-cutover regression has no defined revert procedure, turning a reversible change into an uncontrolled incident. The checklist exists to prevent exactly this gap.