eol-checklist

Generate a phase-gated end-of-life checklist with named owners for product sunsets.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Once a product retirement decision is made, teams often improvise the operational plan, stranding customer data, contracts, integrations, and revenue. This Skill turns a sunset decision into a phase-gated EOL checklist sized to the complexity of the retirement, with a named owning function on every item.

Core Features & Use Cases

  • Right-sized planning levels: Chooses between Light (feature or internal tool), Standard (commercial product), and Heavy (hardware, regulated, channel partners) so process matches risk.
  • Lifecycle phase gating: Structures work across NSC, EOS, EOE, EOR, EOM, EOL, and EOSRV phases with gate criteria and named approvers between transitions.
  • Owned, verb-first items: Every checklist item is 4-8 words, starts with a verb, and names an owning function, covering the four things sunsets strand: data, contracts, access, and money.
  • Use Case: You are retiring a legacy SaaS module with 800 accounts and annual contracts. Invoke the skill with the product name and shutdown date to get a five-phase checklist with owners, gate criteria, and post-EOL actions.

Quick Start

Ask the AI to build an EOL checklist for your product being sunset, including any committed dates, customer scale, and whether contracts, hardware, or channel partners are involved.

Frequently Asked Questions about eol-checklist

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

FAQPage Schema
How do I create an end-of-life checklist for a product sunset?

Invoke the skill with the product being retired and any committed dates. It recommends a complexity level based on blast radius, selects the applicable lifecycle phases, and builds verb-first checklist items with a named owning function for each.

What are the phases of a product end-of-life process?

The standard lifecycle gates are NSC (Notice of Status Change), EOS (End of Sale), EOE (End of Expansion), EOR (End of Renewal), EOM (End of Maintenance), EOL (End of Life), and EOSRV (End of Service). Working checklists typically span the six actionable phases, with EOR inserted when contracts run past EOS.

When should I use a light versus heavy EOL checklist?

Use Light for features, internal tools, or unversioned APIs; Standard for commercial products with paying customers; Heavy for revenue-critical, hardware, regulated, or channel-partner sunsets. Standard is the default, and Heavy should never be applied to a minor deprecation.

What do product sunsets most often forget to plan for?

Sunsets most often strand four things: customer data (export format and deletion schedule), contracts (renewal terms and refunds), access (API keys, integrations, downstream systems), and money (forecast adjustments and revenue recognition). The checklist covers all four at every level.

Can I set an EOL date before a migration path exists?

No. The skill treats an invented date as a failure mode. If no migration path exists, the EOL entry is marked Not scheduled and paired with the precondition that would allow scheduling, such as a validated replacement and a shrinking installed base.