gsd-remove-phase

Remove an unstarted roadmap phase and renumber subsequent phases.

8|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-remove-phase-d0nmega
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-remove-phase
Source: https://github.com/D0NMEGA/donnyclaude/tree/main/packages/skills/gsd-remove-phase
Command: npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-remove-phase-d0nmega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Removes a future roadmap phase to keep the project plan clean and renumbers subsequent phases to preserve linear ordering and history.

Core Features & Use Cases

  • Remove an unstarted future phase from a roadmap and renumber all later phases.
  • Preserve validation gates (future phase checks, work checks), maintain consistent phase indices, and record changes in version history.

Quick Start

Run the remove-phase workflow to prune an unstarted future phase and renumber subsequent phases.

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 future phase from a project roadmap and renumber the rest?

To remove a future phase from a roadmap, you delete the unstarted phase and automatically renumber all subsequent phases to maintain a clean, linear sequence. This preserves project consistency and updates version history with a final git commit.

When do I need to renumber phases in project management?

You need phase renumbering in project management when an unstarted future phase is removed from the roadmap. Renumbering adjusts all subsequent phase indices to preserve linear ordering, ensuring validation gates and historical commits remain consistent.

What is the best way to delete a roadmap phase without breaking validation gates?

The best way to delete a roadmap phase without breaking validation gates is to use an automated workflow that removes the unstarted phase and renumbers subsequent phases. This preserves future phase checks and maintains version control history.

Does removing a phase from a roadmap affect version control history?

Removing a phase from a roadmap does affect version control history by recording the change. The workflow executes a final git commit to document the phase removal and renumbering, ensuring project history accurately reflects the updated roadmap.

Can I remove a phase that has already started from the roadmap?

You cannot remove a phase that has already started. This workflow is designed to remove only future, unstarted phases from the roadmap to preserve validation gates, work checks, and the integrity of historical commits.