gsd-remove-phase

To remove a future roadmap phase and renumber subsequent phases, invoke the skill with the target phase number. It safely deletes the unstarted phase, automatically renumbers the sequence to maintain linear order, and commits the change to git for traceability.

Roadmap phase renumbering works by shifting all subsequent phases down to fill the gap left by the removed phase. This preserves a clean, linear sequence in the project plan and records the modification via a git commit.

No, you cannot remove a roadmap phase that has already started. The skill enforces validation gates that only allow the safe removal of unstarted future phases to prevent breaking active project workflows.

Yes, removing a project phase automatically creates a git commit. The skill records the modification to provide an auditable history of the roadmap change, ensuring full traceability for project management.

The best way to maintain linear phase sequencing after a deletion is to use an automated renumbering workflow. The skill validates the phase is unstarted, removes it, renumbers the subsequent phases, and commits the traceable change to git.