Verified:GitHub

gsd-remove-phase

Removes an unstarted future phase from a roadmap and renumbers subsequent phases.

Updated Mar 15, 2026

Search Tags:#workflow #project planning #roadmap #git commit #renumbering #phase removal

One-click install

npx skills add https://github.com/WeWake1/BSOMS --skill gsd-remove-phase-wewake1

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: gsd-remove-phase
Source: https://github.com/WeWake1/BSOMS/tree/main/.agent/skills/gsd-remove-phase
Command: npx skills add https://github.com/WeWake1/BSOMS --skill gsd-remove-phase-wewake1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When project plans change, removing a planned phase from a roadmap manually leaves gaps in numbering and stale references. This Skill deletes an unstarted future phase and renumbers all subsequent phases so the roadmap stays a clean, linear sequence. ## Core Features & Use Cases - Safe Phase Removal: Validates that the target phase is a future phase with no completed work before deleting it. - Automatic Renumbering: Shifts all subsequent phase numbers down to close the gap left by the removed phase. - Git Commit Record: Commits the removal as a historical record so the change is traceable. - Use Case: Your team decides to drop a planned integration phase from the project roadmap. Invoke this Skill with the phase number to delete it and renumber phases 5-8 down to 4-7 in one operation. ## Quick Start Ask the assistant to remove phase 4 from the roadmap using the gsd-remove-phase skill.

Frequently Asked Questions about gsd-remove-phase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I remove a phase from a project roadmap?▼

Invoke the skill with the target phase number as the argument. The workflow validates the phase is a future, unstarted phase, deletes it, renumbers all subsequent phases, and commits the change to git.

Can I remove a phase that already has completed work?▼

No. The workflow includes a work check validation gate that blocks removal of phases containing completed work. It is designed only for future phases you have decided not to do.

What happens to phase numbers after a phase is removed?▼

All subsequent phases are renumbered down by one to close the gap, keeping the roadmap a clean linear sequence. The removal is recorded as a git commit for traceability.

Does removing a phase keep a record of the deleted plan?▼

Yes. The workflow creates a git commit as the historical record of the removal, rather than leaving cancelled or deferred markers in the roadmap itself.