What problem does it solve? Feature flags accumulate as dead conditional code in trunk when no one owns their retirement, causing technical debt, confusing configuration bundles, and blocked release-train retirements. ## Core Features & Use Cases - Ownership Chain: Defines who introduces, maintains, and retires each flag, tied to the owning release train's lifecycle phases (active, maintained, frozen, retired). - Flag Dies + 1 Cycle Rule: Enforces that a flag must be retired within one cycle after its owning train graduates, with blocking violations at train retirement. - Cleanup Triggers and Audit: Supports calendar-based monthly audits, train-retire gates, and manual on-demand audits, plus a full cleanup checklist covering config bundles, service code, state.json, and tests. - Use Case: When retiring a release train, run the flag audit to find flags still declared in specs, then open cleanup specs to remove flag entries from config bundles, env var reads, conditionals, and tests before the retire gate passes. ## Quick Start Ask the agent to audit feature flags for a retiring release train and generate the cleanup spec covering config bundles, service code, and tests.
