eol-readiness-advisor

Assess whether to retire a product and right-size the end-of-life effort.

6.8k|818|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill eol-readiness-advisor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eol-readiness-advisor
Source: https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-readiness-advisor
Command: npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill eol-readiness-advisor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often say "we should probably kill this" without anyone making a defensible call, leading to premature retirements, delayed sunsets, or mismatched effort where a small feature deprecation gets a steering committee while a revenue-critical product gets a Jira ticket.

Core Features & Use Cases

  • Go/No-Go Verdict: Produces a Go, Go-with-conditions, Hold, Harvest, or Extend verdict backed by named retire and hold signals, with labeled assumptions for unknowns.
  • Intensity Right-Sizing: Recommends a Light, Standard, or Heavy effort level across lifecycle gates, stakeholder counts, and functional areas, while letting the user override the dial.
  • Obligation and Landing-Place Checks: Surfaces contracts, SLAs, regulatory commitments, and channel obligations early, and validates that customers have a real replacement, migration, or graceful-exit path.
  • Use Case: A PM asks whether to retire a legacy module with 800 accounts and $2.4M ARR; the skill walks through four questions and returns a Go-with-conditions verdict at Level 1 plus a Legal check, flagging the 30 accounts lacking feature parity.

Quick Start

Ask the assistant to run an EOL readiness assessment on your product, for example: "Should we retire our legacy reporting module? Usage is down 60% and support costs are climbing."

Frequently Asked Questions about eol-readiness-advisor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide whether to retire a product or feature?

Run a structured go/no-go assessment that weighs four retire signals (financial viability, strategic alignment, replacement, market irrelevance) against four hold signals (obligation lock, strategic hostage, no landing place, exit costs). Two or more strong retire signals make a real case for EOL.

How do I right-size an end-of-life plan for a small feature versus a flagship product?

Choose an intensity level: Light for internal tools with 3-4 stakeholders, Standard for commercial products with 7-8 stakeholders, Heavy for revenue-critical, hardware, or regulated products with 10+ stakeholders. Level 2 is the default; adjust based on blast radius.

What is the difference between End of Sale and End of Life?

End of Sale (EOS) stops new purchases while support continues; End of Life (EOL) retires the product entirely. EOL is a series of gates including NSC, EOS, EOE, EOR, EOM, and EOSRV, and light sunsets may use only three of the eight gates.

When should I not retire a product even if usage is declining?

Hold when contracts, SLAs, or regulatory commitments still run, when the product sits inside strategic accounts, when customers have no replacement or migration path, or when exit costs exceed carry costs. A Hold or Harvest verdict is a legitimate outcome.

What obligations should I check before announcing a product sunset?

Check contracts, SLAs, renewal dates, regulatory certifications, lifetime promises, channel agreements, and spare-parts commitments. The worst EOL failures are legal rather than commercial, so obligation checks happen before any customer announcement.