qsd-remove-phase

Name: qsd-remove-phase
Availability: InStock
Author: thecomputer07

Remove an unstarted future phase and renumber subsequent phases.

Updated Apr 13, 2026

Search Tags:#automation #workflow #roadmap #remove #version-control #phase #renumber

Ready to run

npx skills add https://github.com/thecomputer07/qsd --skill qsd-remove-phase

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qsd-remove-phase
Source: https://github.com/thecomputer07/qsd/tree/main/skills/qsd-remove-phase
Command: npx skills add https://github.com/thecomputer07/qsd --skill qsd-remove-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remove an unstarted future phase from a roadmap and renumber subsequent phases to maintain a clean, linear sequence.

Core Features & Use Cases

Remove a future phase from the roadmap without leaving gaps.
Renumber all subsequent phases to preserve order and enable clear historical tracking.
Commit changes to version control to preserve provenance of the roadmap edits.

Quick Start

Remove phase 4 from the roadmap and renumber subsequent phases.

Frequently Asked Questions about qsd-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 without leaving gaps?▼

To remove a future phase without leaving gaps, delete the unstarted phase and renumber all subsequent phases to maintain a clean, linear sequence. This preserves order and enables clear historical tracking across the roadmap.

What happens to validation gates when you delete an unstarted phase?▼

When you delete an unstarted phase, validation gates and phase order are updated during the renumbering process. The roadmap maintains its linear sequence so that validation gates align correctly with the new phase numbering.

Can I renumber subsequent phases automatically after removing a roadmap phase?▼

Yes, subsequent phases are renumbered automatically after removing a roadmap phase. The workflow enforces commit discipline to version control, preserving the provenance of roadmap edits and maintaining a continuous sequence.

Does removing a phase affect version history in roadmap updates?▼

Removing a phase affects version history by requiring commit discipline during updates. Changes to phase order and validation gates are committed to version control, ensuring the provenance of roadmap edits is preserved.

When should I not use automated phase removal on a roadmap?▼

You should not use automated phase removal on phases that have already started. The workflow applies only to roadmaps with unstarted future phases to ensure safe renumbering without disrupting active work or validation gates.