What problem does it solve?
This Skill helps you decide when old services, APIs, flags, and code should be deliberately removed instead of indefinitely preserved. It turns vague deprecation thinking into a structured lifecycle review that separates healthy sunsetting from risky, incident-driven rip-outs.
Core Features & Use Cases
- Deprecation diagnosis: Distinguishes planned, orderly removal from emergency removal with collateral damage.
- Lifecycle design: Defines death signals, survival signals, and step-by-step sunset cascades for components that should end.
- Cleanup planning: Identifies zombie services, senescent features, dead code, lingering dashboards, and other leftovers that keep operational and cognitive costs alive.
- Use cases: Useful for API sunsets, feature-flag cleanup, migration completion reviews, dead-code audits, and post-incident analysis where retention created risk.
Quick Start
Ask the apoptosis-and-cell-death skill to evaluate a legacy API or service, identify its death trigger, classify its pathology, and produce a full deprecation cascade.