Eol Readiness Advisor
Run a go/no-go assessment for retiring a product or feature, then right-size the effort.
Install
npx skills add deanpeters/Product-Manager-Skills --skill eol-readiness-advisor -g -a claude-code -y- Repository
- deanpeters/Product-Manager-Skills7.8k
- Category
- Engineering
- Updated
- 20d ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Run a go/no-go assessment for retiring a product or feature, then right-size the effort. Use when someone says \"we should probably kill this\" and nobody has made the call.
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 know" is a valid answer that becomes a labeled assumption in the verdict.
Example invocations:
Should we retire our legacy reporting module? Usage is down 60% and support costs are climbing.EOL readiness check on our NFA-200 controller line, 120 installs, channel partners, UL certified.
