gsd-remove-phase

Removing a future phase from a roadmap requires pruning the unstarted phase and automatically renumbering subsequent phases. This maintains a clean linear sequence and ensures the planning workflow remains continuous without manual reordering.

The best way to handle phase-removal in a planning workflow is to use an automated process that prunes the phase and renumbers the rest. Recording the operation with a git commit preserves historical context for future reference.

No, you cannot remove a phase that has already started. The removal process applies validation gates for work completion checks, ensuring only unstarted, future phases are pruned from the roadmap to maintain planning integrity.

When you remove a phase, git commit generation automatically records the roadmap modification to preserve historical context. This ensures the pruning and renumbering operations are traceable within your planning workflow's version history.

When you delete a future phase, subsequent phases are automatically renumbered to maintain a clean, linear sequence. This ensures your roadmap remains logically ordered without any gaps in the phase numbering.

No dependencies are required to execute roadmap phase-removal and renumbering. The process operates independently to validate future-phase existence, apply renumbering logic, and generate a git commit for historical context.