eol-readiness-advisor

# EOL Readiness Advisor ## Purpose Decide whether a product or feature should actually be retired — and if so, how much machinery the retirement deserves. This skill produces a go/no-go verdict with named evidence, an **intensity level** you choose, and a short list of the obligations that will bite you if ignored. Most EOL guidance assumes the decision is already made and jumps to the plan. This skill sits earlier: it is the conversation where "we should probably kill this" becomes a decision someone will defend in a room. It is equally willing to tell you **not** to retire. A "hold" or "harvest" verdict is a real outcome here, not a consolation prize. ## Input **Works best with:** The product or feature under consideration and what triggered the conversation (a declining number, a strategy shift, a support-cost complaint, an exec offhand remark). **Also useful:** Revenue and customer counts, whether a replacement exists, contract or regulatory commitments, and any political sensitivities you already know about. 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 opens by asking what's under review and why, then walks you through blast radius, intensity, and transition path one question at a time. You do not need the numbers in front of you — "I don't kn...