eol-stakeholder-sequence

# EOL Stakeholder Sequence ## Purpose Plan the order of EOL conversations, and what each one must cover. The output is a sequenced list of stops — each with what you need **from** them, what you owe **to** them, the red flags to listen for, and what the conversation must produce. EOL is not a broadcast. It is a series of conversations where each one informs the next, and each one surfaces something the last one missed. Sequenced well, the awkward discoveries happen in a conference room. Sequenced badly, they happen in public, after the announcement, in front of customers. ## Input **Works best with:** The product being sunset and who already knows about it. **Also useful:** Scale (customers, revenue, contracts), whether channel partners or regulators are involved, and any political sensitivities, strained relationships, or past surprises worth planning around. 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 up to three questions — what's being sunset and who knows, how big the blast radius is, and whether there's history to plan around — then builds the sequence. Political sensitivities are optional; the sequence works without them and sharpens with them. **Example invocations:** - `Sequence the stakeholder conversations for retiring our legacy r...