Deprecation Comms Plan Skill

Deprecations go wrong in two ways: too fast (customers get broken and churn angry) or too quiet (they find out when it breaks). This skill plans the wind-down as a communications program, not an announcement — enough runway, messaging matched to how much each customer depends on the thing, a real migration path, and a plan for the accounts that will need a human.

Working from a brief

Given what's being deprecated and why, produce the full plan — infer the risk tiers from usage and contract exposure. Right-size the runway to how hard the migration is (an internal flag flip is weeks; a public API is many months). If there's no migration path yet, flag that as a blocker before any announcement.

Required Inputs

Ask for (if not provided, else infer and label the assumption):

• What's being deprecated and why (cost, security, strategy, replaced-by)
• Who depends on it — rough usage, and which segments/contracts are exposed
• The replacement / migration path (or that there isn't one yet)
• Hard constraints — a forcing date (security, legal, contract), team capacity

Output Format