← ClaudeAtlas

featurelisted

Feature flag design, gradual rollouts, A/B testing, kill switches. LaunchDarkly, Unleash, Flagsmith. Triggers on: /godmode:feature, "feature flag", "gradual rollout", "kill switch", "A/B test".
arbazkhan971/godmode · ★ 26 · Code & Development · score 79
Install: claude install-skill arbazkhan971/godmode
# Feature — Feature Flags & Progressive Delivery ## Activate When - User invokes `/godmode:feature` - User says "feature flag", "gradual rollout" - User says "kill switch", "A/B test" - Deploying needs safer rollout or deploy/release decoupling ## Workflow ### Step 1: Flag Strategy Assessment ```bash # Detect existing flag infrastructure grep -r "launchdarkly\|unleash\|flagsmith\|split\|statsig" \ package.json pyproject.toml 2>/dev/null # Find existing flag usage grep -rn "featureFlag\|isEnabled\|isFeatureEnabled" \ src/ --include="*.ts" --include="*.py" 2>/dev/null | wc -l # Check for stale flags (not evaluated in 30+ days) grep -rn "featureFlag\|isEnabled" src/ \ --include="*.ts" 2>/dev/null | head -20 ``` ``` FLAG STRATEGY: Current: None | Homegrown | LaunchDarkly | Unleash Flag needs: Release | Experiment | Ops | Permission Environments: Dev | Staging | Prod | Mobile IF < 5 flags: Homegrown or Flagsmith OSS IF 5-50 flags: Unleash or Flagsmith IF 50+ flags with experiments: LaunchDarkly IF strict data residency: self-hosted ``` ### Step 2: Flag Types ``` | Type | Lifecycle | Default | Duration | |------------|-------------|---------|-----------| | Release | Short-lived | OFF | < 2 weeks | | Experiment | Short-lived | CONTROL | < 4 weeks | | Ops/Kill | Permanent | ON | Forever | | Permission | Permanent | OFF | Forever | RELEASE RAMP: CREATE → INTERNAL → CANARY 1% → 5% → 25% → 50% → 100% → CLEANUP (within 2 wee