From experimentation-growth-engineering
Use feature flags safely: match the flag type to its purpose (release/experiment/ops/permission), give every risky change a kill switch, roll out progressively gated by a health signal, evaluate deterministically and fail-safe, and manage the flag lifecycle to prevent debt.
How this skill is triggered — by the user, by Claude, or both
Slash command
/experimentation-growth-engineering:feature-flagsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
| Type | Lifespan |
| Type | Lifespan |
|---|---|
| Release | temporary (remove after launch) |
| Experiment | until decision |
| Ops (kill switch) | long-lived |
| Permission/entitlement | permanent |
Treating all flags the same grows debt.
Kill switch for every risky change (off without a deploy). Progressive 1% -> 10% -> 100% gated by a health signal (with devops-cicd/observability-sre).
Deterministic + sticky; fail-safe defaults when the service is unreachable. Every temp flag: owner + removal date. Stale flags = combinatorial config debt + incidents.
npx claudepluginhub mcorbett51090/ravenclaude --plugin experimentation-growth-engineeringGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.