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.