Audit Flags

Identify stale feature flags and provide actionable cleanup recommendations.

Prerequisites

Omen CLI must be installed and available in PATH.

Workflow

Step 1: Detect All Flags

Run the flags analysis:

omen -f json flags

Returns all feature flag references with staleness information, grouped by provider.

Step 2: Identify Ownership

Run the ownership analysis:

omen -f json ownership

Determine who owns the code containing flags - they should own cleanup.

Step 3: Check Coupling

Run the temporal coupling analysis:

omen -f json temporal

Find files that change together with flag-containing files.

Flag Lifecycle Reference

Flag Type	Expected Lifespan	Action if Stale
Release	7-14 days	Remove after 100% rollout
Experiment	30-90 days	Remove after analysis complete
Ops/Kill Switch	Permanent	Document, don't remove
Permission	Permanent	Document, audit access

Priority Matrix

Priority	Criteria	Action
CRITICAL	>90 days stale, high file spread	Immediate removal
HIGH	>60 days stale or in hotspot files	This sprint
MEDIUM	>30 days stale	Next sprint
LOW	Recently added or low file spread	Monitor

Output Format

Generate a flag audit report:

# Feature Flag Audit Report

## Summary

| Metric | Count |
|--------|-------|
| Total flags | 23 |
| Stale (>30 days) | 8 |
| Critical priority | 2 |
| High priority | 3 |

## Stale Flags (Action Required)

### `enable_new_checkout` (CRITICAL)
- **Provider**: LaunchDarkly
- **Age**: 95 days
- **References**: 12 across 5 files
- **Owner**: alice (payment team)
- **Action**: Remove - likely at 100%

### `experiment_pricing_v2` (HIGH)
- **Provider**: Split
- **Age**: 67 days
- **References**: 4 across 2 files
- **Owner**: bob (growth team)
- **Action**: Check experiment results, then remove

## Cleanup Roadmap

### This Sprint
1. Remove `enable_new_checkout` - 2 hours
2. Investigate `experiment_pricing_v2` - 1 hour

### Next Sprint
1. Clean up remaining HIGH priority flags

## Permanent Flags (Document)

| Flag | Type | Purpose |
|------|------|---------|
| `kill_switch_payments` | Ops | Emergency disable |
| `beta_access` | Permission | Feature gating |

Cleanup Steps

For each stale flag:

1. Verify flag state in provider dashboard
2. If serving 100%: Remove flag checks, keep enabled code path
3. If serving 0%: Remove flag checks AND disabled code path
4. Remove flag from provider dashboard
5. Update tests that reference this flag