gsd-remove-phase

Removing a phase from a project roadmap involves targeting the specific phase number within ROADMAP.md. The process enforces safety checks and requires a force flag for potentially destructive deletions to prevent accidental data loss.

Yes, archiving a roadmap phase is supported instead of permanent deletion. The process allows optional archiving when canceling a planned phase, enabling you to clean up the roadmap while preserving historical project data and related work logs.

Yes, removing a roadmap phase supports optional phase renumbering. When you delete a phase, the skill can renumber subsequent phases to maintain sequential consistency across your roadmap documentation and state synchronization files.

Roadmap phase removal synchronizes project state by updating STATE.md and logging changes in the CHANGELOG. This ensures that state references and historical logs accurately reflect the deletion, keeping project management documents consistent.

Attempting to delete a roadmap phase without the force flag blocks the operation. The skill enforces safety checks and requires explicit force commands for potentially destructive deletions to protect your project roadmap data from accidental removal.

You should prune phases from your project roadmap when they are no longer needed or were created by mistake. This keeps your plans current and cleans up the roadmap while preserving history through optional archiving and state synchronization.