create-feature-flag-plan
Create Feature Flag Plan
Overview
Generate a feature flag lifecycle plan for progressive delivery. Covers flag naming, rollout stages from internal to beta to GA, kill switch behavior, monitoring requirements at each stage, and a cleanup plan with a deadline and owner for flag removal. Prevents flag debt and ensures safe, observable rollouts.
Workflow
-
Read engineering context -- Scan
.chalk/docs/engineering/for existing feature flag conventions, architecture docs, and monitoring infrastructure. Check.chalk/docs/product/for the PRD or pitch that describes the feature being flagged. -
Parse the feature -- Extract from
$ARGUMENTSthe feature to create a flag plan for. If unspecified, ask the user to name the feature. -
Determine the next file number -- Read filenames in
.chalk/docs/engineering/to find the highest numbered file. The next number ishighest + 1. -
Define the flag -- Name the flag following conventions found in engineering docs, or default to
enable_<feature_slug>. Specify the flag type (boolean, percentage, user-segment) and default value (always off). -
Plan rollout stages:
- Internal (team only): Who tests, what to validate, success criteria to advance
- Beta (selected users/accounts): Selection criteria, opt-in mechanism, feedback channel, success criteria to advance
More from generaljerel/chalk-skills
python-clean-architecture
Clean architecture patterns for Python services — service layer, repository pattern, domain models, dependency injection, error hierarchy, and testing strategy
24create-handoff
Generate a handoff document after implementation work is complete — summarizes changes, risks, and review focus areas for the review pipeline. Use when done coding and ready to hand off for review.
16create-review
Bootstrap a local AI review pipeline and generate a paste-ready review prompt for any reviewer agent. Use after creating a handoff or when ready to get an AI code review.
15fix-findings
Fix findings from the active review session — reads reviewer findings files, applies fixes by priority, and updates the resolution log. Use after pasting reviewer output into findings files.
15fix-review
When the user asks to fix, address, or work on PR review comments — fetch review comments from a GitHub pull request and apply fixes to the local codebase. Requires gh CLI.
15review-changes
End-to-end review pipeline — creates a handoff, generates a review (self-review or paste-ready for another provider), then offers to fix findings. Use when you want to review your changes before pushing.
13