gsd-remove-phase

To remove a phase from a roadmap and renumber subsequent phases, this workflow validates the target phase is unstarted and scheduled for the future, deletes it, automatically renumbers later phases to maintain a linear sequence, and records the change with a git commit.

When a future phase is deleted from a project roadmap, the renumbering logic automatically shifts all subsequent phase identifiers down to maintain a contiguous, linear sequence, preventing skipped numbers and reducing confusion in project planning.

No, you cannot delete a roadmap phase that has already started. Validation gates ensure the targeted phase contains no started work and is scheduled for the future before allowing deletion to prevent losing active progress.

Yes, removing a phase from a local roadmap file creates an audit trail by committing the deletion and renumbering changes directly to git, ensuring historical traceability for project planning records.

The best way to keep roadmap phase numbering contiguous after canceling a sprint is to use an automated renumbering logic that shifts later phases down and commits the updated sequence to git for auditability.

You should not use automated phase removal for workflow-managed phase sequences if the target phase has already started or is currently active, as validation gates require phases to be unstarted and scheduled for the future before deletion.