skills.rest
GeneralJerel
GeneralJerelCOMMUNITY
Explore all skills by this author →
GitHub

create-feature-flag-plan

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans for feature-flag lifecycles enable progressive delivery with clear rollout criteria, kill-switch strategies, and predictable cleanup.

Core Features & Use Cases

  • Flag naming, type definitions, and default behavior aligned with engineering docs
  • Multi-stage rollout (Internal, Beta, GA) with success criteria and rollback rules
  • Monitoring requirements, thresholds, and cleanup ownership to prevent flag debt

Quick Start

Provide the feature name to generate a complete feature-flag plan and save it to .chalk/docs/engineering/<n>feature_flag_plan<feature-slug>.md.

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 progressive delivery rollout for a new feature?▼

To plan progressive delivery, generate a feature-flag lifecycle plan covering rollout stages, success criteria, and rollback rules. This defines the flag behavior for internal testing, beta users, and general availability.

What is feature flag debt and how do I prevent it during a rollout?▼

Feature flag debt occurs when flags remain in code past their useful life. Prevent it by defining strict cleanup deadlines, assigning clear ownership, and setting monitoring thresholds within your feature-flag lifecycle plan.

How do I define kill switch behavior for a staged feature flag?▼

Define kill switch behavior by establishing default flag states and rollback rules within your feature-flag plan. This ensures immediate deactivation if monitoring thresholds are breached during the beta or GA rollout stages.

Can I generate a feature flag plan for a multi-stage beta rollout?▼

Yes, you can generate a plan for multi-stage beta rollouts. The plan covers internal testing, beta user expansion, and general availability, complete with success criteria and monitoring requirements for each stage.

What's the best way to document feature flag naming and type definitions?▼

Document feature flag naming and type definitions by generating a dedicated feature-flag plan. This aligns default behavior and flag types with engineering docs, saving the output to a structured markdown file for team reference.

Related Skills

Explore More Product & Management Skills→
vibbsvibbs
6

feature-flags

Design feature flag strategies with naming conventions, lifecycles, and progressive discovery patterns.

Community
Advanced
jerelvelardejerelvelarde
6

create-feature-flag-plan

Generate a feature flag lifecycle plan for progressive delivery rollouts.

Community
Advanced
joshua3403joshua3403

phase-9-deployment

Automate production deployments with builds, configurations, and rollback plans.

Community
Advanced
SylphxAISylphxAI
4

deployments

Manages deployments with safe rollbacks and feature flags in production.

Official
Advanced