lifecycle-play-advisor

Diagnose a product's lifecycle stage and recommend extend, replace, retire, or harvest plays.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams argue about whether to extend, replace, or retire a fading product without first agreeing on where the product actually sits in its lifecycle, so the debate is unwinnable and the expensive assumption inside the chosen play goes unexamined.

Core Features & Use Cases

  • Lifecycle Stage Diagnosis: Scores seven transition questions to classify a product as mature-healthy, mature-softening, crossing into decline, or in decline, and names the pattern behind the count.
  • Pressure Source Discrimination: Identifies whether demand-side, supply/cost-side, or capability-side pressure is driving the question, since each points toward a different play.
  • Extension Test: Explicitly tests segment, capability, repackaging, and channel/price levers before conceding to a more expensive replacement or retirement.
  • Use Case: A PM whose reporting module has been flat for six quarters runs the four-question triage and learns the decline signals sit on channel and price, not the product, so the right move is a distributor-tier extension rather than a rebuild.

Quick Start

Ask the advisor to diagnose whether your fading product should be extended, replaced, or retired, and answer its four questions.

Frequently Asked Questions about lifecycle-play-advisor

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

FAQPage Schema
How do I decide whether to extend, replace, or retire a product?

Run a lifecycle diagnosis before choosing a play: score seven transition questions to establish the stage, identify whether the pressure is demand-side, supply/cost-side, or capability-side, then test extension options explicitly. The cheapest play that addresses the actual pressure wins.

How do I know if my product is in decline or just mature?

Answer seven yes/no transition questions covering share defense profitability, loyalty retention, support costs, migration versus loyalty campaigns, channel profitability, bundle effectiveness, and data trends. Zero to one yeses means mature and healthy; six to seven means in decline.

What if flat revenue is caused by the sales channel, not the product?

Check which transition questions came back yes, not just the count. Yeses clustered on channel profitability and bundle effectiveness indicate a distribution problem, which is fixed far more cheaply by repairing the channel or repackaging than by replacing the product.

When is it right to do nothing with a fading product?

When the transition score is zero to one yeses, the product is mature and healthy, so no play is needed. A mature product generating margin with manageable support cost should be left alone or harvested with a set review date rather than given an unneeded project.

What are the risks of replacing a product with a successor?

Replacement runs go-to-market and end-of-life simultaneously for two competing products, making it the most expensive play. Key hazards include internal misalignment, cannibalization, and poor EOL management, and the retirement workstream must be funded alongside the launch.