Feature Flagging Strategy

Develop a feature flagging strategy for {{product_or_team}}.

Current maturity: {{maturity}}
Team size: {{team_size}}
Release frequency: {{frequency}}

**Feature Flag Categories:**

**1. Release Flags**
- Purpose: Ship code, deploy separately
- Lifecycle: Short (days to weeks)
- Removal priority: High

**2. Experiment Flags**
- Purpose: A/B testing
- Lifecycle: Duration of test
- Data requirements: Clear

**3. Operational Flags**
- Purpose: Circuit breakers, kill switches
- Lifecycle: Permanent
- Criticality: High

**4. Permission Flags**
- Purpose: Entitlements, tier access
- Lifecycle: Permanent
- Relationship to billing

**Governance Framework:**

**Naming Conventions**
- Pattern: [type]_[feature]_[date]
- Documentation requirements

**Lifecycle Management**
- Creation approval
- Review cadence
- Removal triggers
- Tech debt tracking

**Targeting Rules**
- User-based targeting
- Percentage rollouts
- Environment controls
- Segment targeting

**Monitoring**
- Flag usage tracking
- Stale flag identification
- Impact measurement

**Best Practices:**
- Default states
- Fallback behaviors
- Testing requirements
- Documentation standards