speckit-deprecate

A phased deprecation workflow manages software feature sunset through three stages: warnings, disabled, and removed. This structured approach minimizes codebase disruption by gradually removing features while tracking dependent systems throughout the process.

Feature sunset planning uses dependency analysis to automatically scan and report code relying on the deprecated feature. This identifies affected systems before removal, generating a comprehensive deprecation plan that safely transitions through warning and disabling phases.

Yes, direct mode supports deprecating features by specifying feature numbers as arguments. Alternatively, interactive mode allows manual feature selection from a list, providing flexibility when initiating the phased sunset workflow for single or multiple features.

The best way to notify users before feature removal is implementing a three-phase sunset process. It starts with warnings to alert users, proceeds to disabling the feature, and concludes with complete code removal while dependency scans ensure system stability.

Automated feature deprecation may be unnecessary for trivial code deletions with zero dependencies. If a feature has no dependent systems and requires no user notification, a phased sunset workflow adds overhead compared to immediate removal.

Yes, the deprecation workflow runs dependency scans to identify affected code and generates a comprehensive removal plan. This plan structures the three-phase sunset process, ensuring all dependent systems are accounted for before final code removal.