Agent skill · Business & Finance

eol-readiness-advisor

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.

Dean Peters6,255★ · 1 repos on radarProfile →
claude-codeNOASSERTION
Install
npx skills add deanpeters/Product-Manager-Skills --skill eol-readiness-advisor --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 21 KB
Bundled scripts: none
Path: skills/eol-readiness-advisor/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 6,444
Language: Shell
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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

What's inside
Steps it walks through
  1. Purpose
  2. Input
  3. Key Concepts
  4. The Right-Sizing Dial
  5. Lifecycle Gates (shared vocabulary)
  6. The Four Retire Signals
  7. The Four Hold Signals
  8. Anti-Patterns (what this is NOT)
  9. Application
  10. Question 1 of 4 — What's under review, and what triggered this?
  11. Question 2 of 4 — What's the blast radius?
  12. Question 3 of 4 — Set the intensity
  13. Question 4 of 4 — Where do customers land?
  14. Final Step: Deliver the assessment
More from Product-Manager-Skills
All skills →
About this skill
What does the eol-readiness-advisor skill do?

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.

How do I install it?

Run `npx skills add deanpeters/Product-Manager-Skills --skill eol-readiness-advisor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From deanpeters/Product-Manager-Skills, a repository with 6,444 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going