Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From experimentation-growth-engineering
Set up feature flags typed by purpose with kill switches, progressive rollout, and a lifecycle policy.
How this command is triggered — by the user, by Claude, or both
Slash command
/experimentation-growth-engineering:setup-feature-flags [rollout / flag situation]The summary Claude sees in its command listing — used to decide when to auto-load this command
You are running `/experimentation-growth-engineering:setup-feature-flags`. Use `feature-flag-engineer` + the `feature-flags` skill. ## Steps 1. Type each flag (release/experiment/ops/permission); add kill switches. 2. Design progressive rollout gated by a health signal (with devops-cicd). 3. Set fail-safe defaults; assign owner + removal date per temp flag. 4. Emit (from `templates/flag-spec.md`) + Structured Output block.
You are running /experimentation-growth-engineering:setup-feature-flags. Use feature-flag-engineer + the feature-flags skill.
templates/flag-spec.md) + Structured Output block.npx claudepluginhub mcorbett51090/ravenclaude --plugin experimentation-growth-engineering