CW-301h · Module 2

Deprecation & Retirement

3 min read

Library prompts have a lifespan. The prompt that analyzed competitor pricing using a specific framework becomes obsolete when the framework changes. The prompt that generated reports in a specific format becomes obsolete when the format standard is updated. Prompts that are no longer accurate, relevant, or effective need to be deprecated — marked as outdated and eventually removed.

The deprecation protocol: mark the prompt as "deprecated" with a reason and a pointer to the replacement prompt (if one exists). Keep the deprecated prompt visible but clearly labeled for 60 days. After 60 days, archive it — remove it from the active library but preserve it in version history. Never delete without warning. Team members who depend on a prompt need time and guidance to transition.

Do This

  • Deprecate prompts when their output is no longer accurate or their context assumptions are outdated
  • Point deprecated prompts to their replacement — "Use v3.0 of Competitive Analysis instead"
  • Keep deprecated prompts visible for 60 days before archiving — people need transition time

Avoid This

  • Delete prompts without notice — someone is using it in a workflow you do not know about
  • Keep obsolete prompts active because "someone might need it" — obsolete prompts produce wrong output
  • Deprecate without providing an alternative — tell people what to use instead