speckit-deprecate

Automate phased feature deprecations with a spec-kit workflow.

2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-deprecate-pradeepmouli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-deprecate
Source: https://github.com/pradeepmouli/lspeasy/tree/main/.github/skills/speckit-deprecate
Command: npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-deprecate-pradeepmouli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deprecating features without a plan can confuse users, risk breaking changes, and delay sunset timelines. This Skill provides a structured, phased approach to deprecation, including warnings, feature-disablement, and removal with migration guidance.

Core Features & Use Cases

  • Guided, three-phase deprecation workflow aligned with organizational standards.
  • Interactive mode to select features when a reason is provided without a feature number.
  • Automated plan generation, dependencies reporting, and migration path recommendations.

Quick Start

Run /speckit.deprecate <feature_number> "reason" to start a deprecation plan.

Frequently Asked Questions about speckit-deprecate

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

FAQPage Schema
How do I plan a phased feature deprecation without breaking changes?

A phased feature deprecation requires a structured workflow guiding users through warning states, feature-disablement, and eventual removal with migration paths. This ensures deprecation plans, dependencies, and timelines align with organizational standards.

What's the best way to communicate a feature sunset timeline to users?

Feature sunset communication is best handled through a three-phase deprecation workflow that generates rollout, communication, and rollback strategies. This ensures users receive proper warnings and migration guidance before features are disabled and removed.

How do I generate a migration path for deprecated features?

Migration paths for deprecated features are generated automatically as part of a structured deprecation plan. This includes dependencies reporting and recommendations ensuring users transition smoothly through warning, disabled, and removal phases.

When do I need a structured workflow for feature deprecation?

A structured deprecation workflow is needed when retiring features without a plan risks confusing users, causing breaking changes, or delaying sunset timelines. It provides warnings, feature-disablement, and removal guidance aligned with organizational standards.

Can I select specific features to deprecate interactively or do I need a feature number?

Interactive mode allows you to select features for deprecation when a reason is provided without a feature number. Alternatively, direct mode runs by specifying the feature number and reason together to initiate the deprecation plan.

Does the deprecation workflow include a rollback strategy?

The deprecation workflow includes a rollback strategy as part of its three-phase timeline generation. Alongside rollout and communication plans, this ensures safe execution of feature-disablement and removal phases with recovery options.