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."