All products

Plan a feature retirement with AI

Work out who still needs a feature, what changes for them and how to communicate the deadline, migration path and exceptions.

To plan a feature retirement with AI, start with the customer who still relies on the old workflow. A dashboard may have few visitors but produce a report somebody needs at month end. The deprecation-plan skill prompts you to distinguish observed use from an assumption about who will be affected. It also asks whether the replacement changes the task or leaves someone without an equivalent.

The resulting plan can use relative dates until a deadline exists. It gives your team somewhere to record who will handle late requests and who can grant exceptions, before those decisions become urgent.

What it does

  • List affected groups, known usage and unanswered contract questions.
  • Sequence internal preparation, an announcement, reminders and removal.
  • Describe the action a customer must take to keep working.
  • Draft a notice that names the change and deadline up front.
  • Assign a route for accounts that miss the migration window.

Install and use

  1. Install the skill in a compatible agent and provide authorised product context. No separate account is needed to draft the plan.
  2. Ask, “Prepare a retirement plan for the old export, keeping unknown usage and dates visible.”
  3. Have the owners check the dates, contractual commitments and replacement instructions before sending the notice.

FAQ

Source

Made by Charlene Strain. Original skill: deprecation-plan, published on GitHub under the MIT licence.

View on GitHub