gsd-remove-phase

Remove an unstarted future phase and renumber subsequent roadmap phases.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/rkz91/coco --skill gsd-remove-phase-rkz91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-remove-phase
Source: https://github.com/rkz91/coco/tree/main/systems/gsd/skills/gsd-remove-phase
Command: npx skills add https://github.com/rkz91/coco --skill gsd-remove-phase-rkz91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a controlled method to drop a future, unstarted phase from a project roadmap and ensure all later phases are renumbered in a consistent sequence.

Core Features & Use Cases

  • Phase removal: Safely remove an unstarted future phase without leaving cancelled markers.
  • Renumbering: Update all subsequent phase numbers to maintain a clean, linear roadmap.
  • Auditability: Record a git commit or history entry to preserve historical context of the decision.

Quick Start

Run the remove-phase workflow to delete a specified future phase and renumber all following 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 project roadmap, you delete the specified unstarted phase and automatically renumber all subsequent phases. This maintains a clean, linear sequence and updates all related IDs and references.

Can I delete an active or completed phase from the roadmap?

No, you cannot delete an active or completed phase from the roadmap. Validation gates strictly prevent the removal of active or completed phases, ensuring only unstarted future phases are eligible for deletion.

What happens to phase IDs and references when I remove a phase?

When you remove a phase, renumbering logic applies consistently across the roadmap, automatically updating all subsequent phase numbers, IDs, and internal references to maintain a clean sequence without leaving cancelled markers.

Does removing a phase from the roadmap preserve project history?

Yes, removing a phase preserves project history by recording a git commit or history entry. This auditability feature ensures the historical context of the decision is kept within the workflow.

What is the best way to drop an unstarted phase without leaving cancelled markers?

The best way to drop an unstarted phase without leaving cancelled markers is using a controlled workflow that safely removes the phase and renumbers subsequent phases, ensuring the roadmap remains clean and linear.