gsd-remove-phase

Renumbering phases after removing a roadmap item maintains a strict sequential order by shifting all later phases up. This renumbering logic ensures your project plan retains a clean, linear sequence without gaps in the phase numbering.

When you delete a future phase, validation gates check roadmap integrity and update dependent milestones accordingly. This ensures that removing a cancelled phase does not break the dependencies of later phases in your project plan.

Removing a roadmap phase triggers a git commit to serve as a historical record of the deletion and subsequent phase renumbering. This ensures you can track when and why a phase was cancelled from the workflow.

You should use an automated phase renumbering workflow when a planned future phase is cancelled and you need to shift all later phases to maintain a strict sequential order. It is ideal for product roadmaps with sequential phases and dependencies.

Yes, you can remove a phase from a roadmap with existing dependencies. The workflow enforces validation gates to check the integrity of the roadmap and automatically updates dependent milestones before applying the phase renumbering logic.