speckit-workflows.deprecate

Manage a three-stage software feature deprecation workflow with dependency analysis.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/refactory-lang/refactory-template --skill speckit-workflows-deprecate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-workflows.deprecate
Source: https://github.com/refactory-lang/refactory-template/tree/main/.claude/skills/speckit-workflows.deprecate
Command: npx skills add https://github.com/refactory-lang/refactory-template --skill speckit-workflows-deprecate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of deprecating software features, ensuring a structured and phased approach to removal that minimizes disruption to users.

Core Features & Use Cases

  • Phased Sunset: Manages a three-phase deprecation process: Warnings, Disabled, and Removed.
  • Dependency Analysis: Identifies code and features dependent on the one being deprecated.
  • Use Case: A product team decides to remove an underutilized API endpoint. This Skill helps them generate a deprecation plan, communicate the changes to users, and manage the technical rollout across different phases.

Quick Start

Initiate a deprecation workflow for feature 014 with the reason "low usage and high maintenance burden".

Frequently Asked Questions about speckit-workflows.deprecate

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

FAQPage Schema
How do I plan a phased deprecation workflow for a software feature?

A phased deprecation workflow manages a three-stage sunset process—Warnings, Disabled, and Removed—to minimize user disruption. It analyzes feature dependencies and generates a comprehensive deprecation plan with migration paths and communication strategies.

What is the best way to sunset an API endpoint without disrupting users?

Sunsetting an API endpoint requires a structured feature lifecycle approach that includes dependency analysis and a phased rollout. This generates migration paths and communication strategies to transition users smoothly through warning and disabled phases before removal.

How does dependency analysis work when removing underutilized software features?

Dependency analysis identifies code and features reliant on the deprecated component before removal. It maps technical dependencies to generate a safe deprecation plan, ensuring migration paths address all affected areas during the phased sunset.

Do I need a spec-kit project structure to automate feature deprecation plans?

Yes, automating a feature deprecation workflow requires a spec-kit project structure and specific bash scripts for execution. This environment setup supports the three-stage sunset process and triggers the dependency analysis needed for migration planning.

What should be included in a software sunset communication strategy?

A software sunset communication strategy must outline migration paths and phase transitions from warnings to complete removal. It is generated as part of a comprehensive deprecation plan to inform users about the feature lifecycle changes.

Can I skip the warning phase when automating a feature deprecation workflow?

No, the automated feature deprecation workflow enforces a three-stage sunset process: Warnings, Disabled, and Removed. This phased rollout structure ensures users receive migration notices before the feature is fully retired.