gsd-remove-phase

To remove a future phase from a roadmap without leaving numbering gaps, delete the unstarted phase and automatically renumber all subsequent phases to maintain linear sequence consistency. This prevents confusing gaps and outdated numbering in your project timeline.

No, you cannot delete an active phase because the workflow applies validation gates requiring the target phase to be future and unstarted. This prevents accidental deletion of active work and ensures only cancelled planned phases are removed.

To renumber phases after cancelling an unstarted phase, remove the target phase and automatically update all later phases to eliminate sequence gaps. This maintains linear progression and keeps the roadmap structure consistent for ongoing workflow execution.

Yes, removing a roadmap phase creates a git commit that preserves the deletion and renumbering action as an audit-friendly record. This ensures the phase management change is tracked in version control history for future reference.

The main limitation is that the phase must be future and unstarted; active phases cannot be targeted. Additionally, the workflow strictly requires passing validation gates before executing the removal and renumbering process to prevent data loss.