gsd-remove-phase

Remove unstarted future roadmap phases and renumber subsequent phases.

1|Updated Aug 17, 2025
One-click install
npx skills add https://github.com/DuySeu/StockMind --skill gsd-remove-phase-duyseu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-remove-phase
Source: https://github.com/DuySeu/StockMind/tree/main/.agent/skills/gsd-remove-phase
Command: npx skills add https://github.com/DuySeu/StockMind --skill gsd-remove-phase-duyseu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remove future, unstarted phases from a roadmap and renumber subsequent phases to maintain a clean, linear sequence. This prevents dead scaffolding from polluting context and ensures a tidy historical record through a commit.

Core Features & Use Cases

  • Remove an unstarted future phase from the roadmap without affecting started or completed phases.
  • Renumber all subsequent phases to preserve a continuous sequence and avoid gaps.
  • Preserve validation gates (future phase check, work check) and generate a clear Git history for audit.

Quick Start

Provide the target phase name to remove and run the remove-phase workflow to apply changes.

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 roadmap and renumber the remaining phases?

The remove-phase workflow targets only future, unstarted phases for deletion, leaving active, started, or completed phases untouched while renumbering subsequent phases to prevent gaps in the roadmap sequence.

Can I delete an active or completed phase from the roadmap without affecting other phases?

No, active, started, or completed phases cannot be removed. The workflow applies exclusively to future, unstarted phases, preserving validation gates and work checks to protect in-progress or finished roadmap sections.

How does version control track changes when removing unstarted phases from a roadmap?

Version control tracks phase removal by generating a git commit history as the historical record, ensuring a tidy audit trail of the deleted future phase and the subsequent renumbering logic applied to the roadmap.

What is the best way to maintain a clean linear phase sequence after deleting a future roadmap phase?

The best way to maintain a clean linear phase sequence is to use automated renumbering logic, which shifts subsequent phases down to close gaps, preserve continuous workflow progression, and prevent dead scaffolding from polluting context.

Does removing a future phase from the roadmap affect existing validation gates?

No, removing a future phase preserves existing validation gates, including the future phase check and work check. The process ensures only the targeted unstarted phase is removed while underlying workflow validations remain intact.