gsd-remove-phase

To remove a phase from a roadmap and renumber the rest, you initiate a remove-phase workflow that deletes the specified unstarted future phase and automatically renumbers subsequent phases to maintain a linear sequence.

When you delete an unstarted phase from a product roadmap, subsequent phases are automatically renumbered to prevent gaps or duplicates, ensuring the planning sequence remains clean and linear.

No, you cannot remove a phase that has already started. This workflow applies validation checks to ensure only unstarted future phases are removed, preventing the disruption of active work.

Yes, removing a roadmap phase preserves historical context by enforcing a git commit. This documents the change in version control when a phase is canceled or deferred during roadmap maintenance.

The best way to handle deferred phases in roadmap maintenance is using an automated workflow that removes the phase, renumbers subsequent phases to avoid gaps, and commits the change to git for historical tracking.

Phase renumbering validation fails if the target phase has already started or if offset integrity checks detect existing gaps or duplicates, ensuring only structurally sound, unstarted future phases are removed.