gsd-remove-phase

To remove a future phase from an agile roadmap and renumber the rest, you need a validated workflow that deletes the unstarted phase and shifts subsequent phase numbers to maintain a clean, linear sequence.

Yes, renumbering subsequent roadmap phases automatically after deleting a future phase ensures the project maintains a consistent order without manual numbering gaps, applying validated renumbering logic to the planning workflow.

Deleting an unstarted phase from a roadmap should conclude with a git commit that records the change, ensuring the project history clearly describes the phase removal and renumbering update.

Removing a phase that has already started from the roadmap triggers a future-phase validation guard, which prevents the removal and renumbering workflow from executing on active or past project phases.

The best way to maintain a linear sequence when canceling future phases in a workflow is to apply an automated remove-phase process that validates the phase is unstarted and renumbers all subsequent phases.

Removing a roadmap phase leaves gaps in the project numbering sequence if the workflow lacks automated renumbering logic, requiring subsequent phases to be manually shifted to preserve a clean, linear order.