gsd-remove-phase

Removing a future phase from a roadmap involves discarding the target phase and deterministically renumbering all subsequent phases to maintain a clean, linear sequence. This process preserves completed work and keeps the roadmap coherent.

Phase renumbering shifts the sequence numbers of subsequent phases after a removal to eliminate gaps. It ensures the roadmap maintains a strict linear order, preventing numbering inconsistencies from disrupting future workflow validation.

No, this process applies only to future, unstarted phases. It validates the target phase before removal to ensure completed work remains unaffected, making it unsuitable for modifying active or historical roadmap phases.

Yes, removing a roadmap phase and renumbering subsequent phases generates a git commit. This creates a historical trace of the roadmap modification, enabling rollback if the phase removal needs to be reversed.

The best way to maintain a strict linear order is through deterministic renumbering of subsequent phases after deletion. This approach validates the phase removal and commits the updated sequence to ensure roadmap consistency.