gsd-remove-phase

Remove future phases from a project roadmap and renumber subsequent phases.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/NUbivek/Searchbar3 --skill gsd-remove-phase-nubivek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-remove-phase
Source: https://github.com/NUbivek/Searchbar3/tree/main/.codex/skills/gsd-remove-phase
Command: npx skills add https://github.com/NUbivek/Searchbar3 --skill gsd-remove-phase-nubivek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines roadmap management by allowing the clean removal of future, unstarted phases and automatically renumbering subsequent phases to maintain order.

Core Features & Use Cases

  • Phase Removal: Safely delete a future phase from your project roadmap.
  • Renumbering: Automatically adjusts the numbering of all subsequent phases.
  • Use Case: If a planned phase is no longer relevant before development begins, use this skill to remove it without leaving gaps or confusing numbering in your roadmap.

Quick Start

Use the gsd-remove-phase skill to remove the phase named 'Phase 3'.

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 and renumber the rest?

Removing a phase from a project roadmap deletes the specified future phase and automatically renumbers all subsequent phases to maintain sequential integrity without leaving gaps in the workflow.

Can I delete a phase that has already started in my workflow automation?

Deleting a phase that has already started is not allowed. The skill performs validation checks on work status and only permits the removal of future, unstarted phases in the project roadmap.

What happens to phase numbering when a future phase is no longer relevant?

When a future phase is no longer relevant and gets removed, the skill automatically adjusts the numbering of all subsequent phases to ensure the project roadmap maintains strict sequential order.

Does removing an unstarted phase create a historical record in version control?

Removing an unstarted phase creates a historical record by committing the changes via a git commit, ensuring your roadmap modifications are tracked properly within your project management workflow.

Are there limitations on which phases can be targeted for removal and renumbering?

Limitations include strict validation checks that prevent removing active or past phases. Only future phases that have not begun work can be safely deleted and renumbered in the roadmap.