skills.rest
jerelvelarde
jerelvelardeCOMMUNITY
Explore all skills by this author →
GitHub

create-feature-flag-plan

Generate a feature flag lifecycle plan for progressive delivery rollouts.

6|Updated Feb 19, 2026
Search Tags:#planning#monitoring#feature-flag#kill-switch#progressive-delivery#rollout-strategy
One-click install
npx skills add https://github.com/jerelvelarde/chalk-skills --skill create-feature-flag-plan-jerelvelarde
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-feature-flag-plan
Source: https://github.com/jerelvelarde/chalk-skills/tree/main/skills/create-feature-flag-plan
Command: npx skills add https://github.com/jerelvelarde/chalk-skills --skill create-feature-flag-plan-jerelvelarde

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and executing safe, observable feature flag rollouts can be error-prone without a clear lifecycle, kill switches, and cleanup deadlines. This skill provides a structured plan template that aligns product, engineering, and operations around progressive delivery.

Core Features & Use Cases

  • Flag lifecycle blueprint: defines naming conventions, flag types, rollout stages, and ownership.
  • Deployment readiness: ensures monitoring, alerts, and rollback criteria are in place before each stage.
  • Documentation and governance: produces a repeatable plan that can be used across teams for audits and compliance.

Quick Start

Use this plan to generate a complete feature flag lifecycle document for a feature you are about to ship.

Frequently Asked Questions about create-feature-flag-plan

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

FAQPage Schema
How do I plan a safe progressive feature-flag rollout?▼

A progressive feature-flag rollout plan defines flag naming conventions, rollout stages, kill-switch behavior, monitoring requirements, and cleanup deadlines with clear ownership to manage delivery across internal, beta, and GA stages.

What should a feature flag lifecycle document include for audits and compliance?▼

A feature flag lifecycle document should include a flag definition, rollout schedule, kill-switch behavior, monitoring requirements, and a cleanup deadline with ownership to ensure deployment readiness and governance.

How do I set up a kill switch and monitoring for a new feature rollout?▼

Setting up a kill switch and monitoring for a feature rollout involves defining rollback criteria and alerting requirements before each stage to ensure deployment readiness and safe progressive delivery.

Can I use this rollout strategy plan for internal, beta, and GA releases?▼

Yes, this rollout strategy plan is designed to manage progressive delivery across internal, beta, and GA releases by specifying a complete flag lifecycle with consistent naming and deployment readiness checks.

Why do I need a cleanup deadline in my feature flag plan?▼

A cleanup deadline in a feature flag plan ensures flags are retired after a feature reaches general availability, preventing technical debt and maintaining governance across engineering teams.

What is the best way to manage feature flag ownership across teams?▼

Managing feature flag ownership across teams requires a structured lifecycle blueprint that specifies ownership, naming conventions, rollout stages, and cleanup deadlines to align product, engineering, and operations.

Related Skills

Explore More Software Engineering Skills→
GeneralJerelGeneralJerel
6

create-feature-flag-plan

Generate a feature-flag lifecycle plan covering rollout stages, monitoring, and cleanup.

Community
Advanced
dreamingechoesdreamingechoes
2

feature-flag-management

Define, manage, and retire feature flags across releases and environments.

Community
Advanced
apecloudapecloud
3

kubeblocks-observability-existing-stack

Integrate KubeBlocks metrics into an existing Prometheus/Grafana stack.

Official
Intermediate
dudedesi12dudedesi12

feature-flags

Manage feature toggles and adjust rollout percentages across environments.

Community
Intermediate