eol-message

# EOL Message ## Purpose Craft a clear, empathetic End-of-Life (EOL) message that communicates discontinuation, explains the rationale, addresses customer impact, provides transition support, and positions what comes next. Use this to maintain customer trust during a difficult transition and reduce the churn that comes from customers feeling abandoned. This is not a generic sunset announcement — it's a customer-centric communication that acknowledges loss while framing the change as progress. And it is **sized to the change**: a deprecated toggle gets a paragraph, a flagship retirement gets phased communications across months. ## Input **Works best with:** What's being retired (product, feature, or plan) and roughly when. **Also useful:** The rationale, affected customer segments, migration or replacement path, support commitments, and any contract or regulatory language that constrains what you can say. Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line — counts as answers already given. Use it and skip whatever it covers; don't re-ask. **Arriving empty-handed? That works too.** The skill asks for the what/when/why and the landing place before drafting, then recommends a message size you can override. An EOL message without a stated rationale and a next step reads as abandonment — so those two get asked for either way. **Example invocations:** - `Draft an EOL message: retiring our legacy ...