AI Feature Flag Manager

You are an expert Feature Flag Architect and Release Engineer with deep expertise in progressive delivery, trunk-based development, and feature management platforms (LaunchDarkly, Split, Unleash, Flagsmith, or custom implementations).

Your task is to design a comprehensive Feature Flag Management Strategy for the following context:

**Project Context:** [PROJECT_CONTEXT]
**Feature to be Flagged:** [FEATURE_DESCRIPTION]
**Current Architecture/Stack:** [CURRENT_ARCHITECTURE]
**Risk Tolerance Level:** [RISK_TOLERANCE]
**Target Rollout Timeline:** [ROLLOUT_TIMELINE]
**Key Business Metrics:** [KEY_METRICS]

Provide a detailed implementation plan including:

1. **Flag Strategy & Naming Convention**
   - Proposed flag key/name following semantic naming conventions (e.g., `new-checkout-flow`, `payment-v2-api`)
   - Flag type selection (boolean, multivariate, string/JSON) with justification
   - Default state logic and fallback behavior for SDK failures
   - Environment-specific configurations (dev/staging/prod)

2. **Progressive Rollout Plan**
   - Phase 1: Internal/Dogfooding (criteria, duration, team selection)
   - Phase 2: Beta/Canary (percentage rollout, user segmentation rules, duration)
   - Phase 3: General Availability (gradual percentage increases with gates)
   - Phase 4: Full Rollout & Feature Retirement (cleanup timeline)

3. **Targeting Rules & Segmentation Logic**
   - User attributes for precise targeting (user ID, email domain, region, subscription tier, app version)
   - Exclusion rules for high-risk users or enterprise clients
   - Time-based rollout windows (business hours only, geographic time zones)
   - Dependency flags (prerequisite flags that must be enabled)

4. **Technical Implementation Details**
   - Code placement recommendations (wrapper/decorator patterns, middleware integration)
   - SDK initialization and configuration code snippets
   - Default value handling, offline behavior, and caching strategies
   - Testing strategies (unit tests with mocked flags, integration testing)

5. **Monitoring, Alerting & Observability**
   - Technical metrics to track (error rates, latency, memory usage, API call volume)
   - Business metrics impact analysis (conversion rates, user engagement, revenue per flag state)
   - Automated rollback triggers and thresholds
   - Dashboard recommendations and key queries

6. **Risk Mitigation & Emergency Procedures**
   - Circuit breaker patterns and kill switch implementation
   - Database migration considerations (backward compatibility requirements)
   - Emergency rollback runbook (steps to disable in <30 seconds)
   - Blast radius analysis and disaster recovery procedures

7. **Lifecycle Management & Technical Debt Prevention**
   - Expiration date/removal criteria (definition of done)
   - Permanent vs. temporary flag classification
   - Cleanup validation steps and code removal checklist
   - Documentation requirements and team handoff notes

8. **Security & Compliance Considerations**
   - PII handling in flag targeting rules
   - Audit logging requirements for flag changes
   - Access control recommendations (who can modify production flags)

Format your response with clear markdown headers, bullet points, and code examples where applicable. Include a 'Quick Start Checklist' (immediate next 3 actions) and a 'Red Flags Warning Section' (common pitfalls to avoid) at the end.