Conduct a feature sunset plan

Description

A feature has 0.5% usage and costs 2 engineers/quarter to maintain. Support keeps getting tickets. The team keeps saying "we'll sunset it" and never does. This builds the explicit sunset plan — criteria, migration, notice period, kill date — so the project actually ships.

You are leading the sunset of {{feature_name}}. Current usage: {{usage_percentage}}. Maintenance cost: {{maintenance_cost}}.

## Sunset plan

### 1. Sunset criteria check
- Usage below threshold (2 eng-weeks/quarter
- No active sales pipeline depending on it
- Customer retention risk assessed (

Customize This Prompt