# eol-readiness-advisor

This skill assesses whether a product or feature should reach end of life and sizes the transition work. Use it when the retirement decision is stuck.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 905 installs · ★ 7673
- Author: deanpeters
- License: CC-BY-SA-4.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/deanpeters/Product-Manager-Skills/tree/HEAD/skills/eol-readiness-advisor/SKILL.md
- Updated: 2026-10-16
- HTML: https://affpapa.org/en/nevibecode/skills/eol-readiness-advisor

## What it does

\`eol-readiness-advisor` runs an interactive go/no-go review for a product or feature under EOL consideration. It weighs financial, strategic, replacement, and market signals against contracts, service promises, regulatory duties, and the cost of continued maintenance. The output includes a verdict, an intensity level, and the organizational areas that need to take part.

The skill uses a three-level scale, from a light feature sunset to a heavy transition for revenue-critical, hardware, or regulated products. It also separates lifecycle gates so a status change, end of sale, maintenance stop, and final service end are not treated as one event. A missing replacement is a reason to resist an immediate EOL decision when customers would have nowhere to move.

The interaction starts by asking what is being reviewed and what triggered the discussion. The agent then works through impact, intensity, and the transition path one question at a time. You can provide revenue, customer counts, replacement details, or contractual and regulatory context with the request.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add deanpeters/Product-Manager-Skills --skill eol-readiness-advisor -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/eol-readiness-advisor/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/eol-readiness-advisor/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add deanpeters/Product-Manager-Skills --skill eol-readiness-advisor -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/eol-readiness-advisor/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add deanpeters/Product-Manager-Skills --skill eol-readiness-advisor -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/eol-readiness-advisor/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install deanpeters/Product-Manager-Skills eol-readiness-advisor
```

2. **Manually: put the files in place**
- File: `.github/skills/eol-readiness-advisor/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add deanpeters/Product-Manager-Skills --skill eol-readiness-advisor -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/deanpeters/Product-Manager-Skills --path skills/eol-readiness-advisor
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/eol-readiness-advisor/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add deanpeters/Product-Manager-Skills --skill eol-readiness-advisor -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/deanpeters/Product-Manager-Skills/tree/HEAD/skills/eol-readiness-advisor/SKILL.md

## When to use it
- decide whether to retire a product or feature
- test the case for closing a declining offering
- size the work required for an EOL transition
- surface contractual and regulatory obligations
- identify the teams that must be involved

## Example prompts
- Run an EOL assessment for our reporting module: usage is falling and support costs are rising.
- Review whether we should retire a controller line with installed units and channel partners.
- Compare retiring, holding, and reducing support for this feature.

## Similar
- [setup-matt-pocock-skills](https://affpapa.org/en/nevibecode/skills/setup-matt-pocock-skills.md) — skill · 1052851 installs
- [ask-matt](https://affpapa.org/en/nevibecode/skills/ask-matt.md) — skill · 766587 installs
- [to-tickets](https://affpapa.org/en/nevibecode/skills/to-tickets.md) — skill · 711230 installs
- [writing-plans](https://affpapa.org/en/nevibecode/skills/writing-plans.md) — skill · 282859 installs
- [caveman-review](https://affpapa.org/en/nevibecode/skills/caveman-review.md) — skill · 411800 installs
- [caveman-compress](https://affpapa.org/en/nevibecode/skills/caveman-compress.md) — skill · 411500 installs

From the same set: [deanpeters/product-manager-skills](https://affpapa.org/en/nevibecode/by/deanpeters/product-manager-skills.md) — 73 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md