gsd-remove-phase

Removing an unstarted future phase from a roadmap requires validating the phase is unstarted, deleting its entries, automatically renumbering all subsequent phases to preserve a contiguous sequence, and committing the change to git for a clean repository state.

You should delete a roadmap phase instead of deferring it when you want to keep the phase sequence linear and avoid leaving cancelled or deferred markers in your repository, ensuring unstarted future phases are cleanly removed and renumbered.

No, you cannot remove a phase that has already started because the safe removal process validates that the target phase is unstarted before deleting related entries, preventing the accidental removal of in-progress work.

The best way to renumber subsequent phases is using a dedicated workflow that safely deletes the target phase, automatically renumbers all following phases to close the gap, updates the files, and records the change in a git commit.

Yes, removing a phase automatically creates a git commit to serve as an audit trail, recording the removal and renumbering as historical context for the team rather than leaving untracked changes in the repository.

This workflow applies specifically to repositories that use numbered roadmap phases where unstarted future phases must be removed and subsequent phases renumbered, making it suitable for structured phase-management workflows.