remove-phase

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

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/sidunrealde/ArchVis --skill remove-phase-sidunrealde
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remove-phase
Source: https://github.com/sidunrealde/ArchVis/tree/main/.github/skills/remove-phase
Command: npx skills add https://github.com/sidunrealde/ArchVis --skill remove-phase-sidunrealde

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gsd-tools.cjs, and includes scripts (resource) components.

What problem does it solve?

This Skill allows for the clean removal of unstarted future phases from a project roadmap, ensuring the roadmap remains organized and sequential.

Core Features & Use Cases

  • Phase Removal: Safely delete future project phases and their associated directories.
  • Renumbering: Automatically renumbers all subsequent phases to maintain a linear sequence.
  • Commit History: Records the removal in git history for accountability.
  • Use Case: If a planned future phase is no longer relevant, use this Skill to remove it without manual file management or complex renumbering.

Quick Start

Use the remove-phase skill to remove phase 17 from the project roadmap.

Frequently Asked Questions about remove-phase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I delete a future phase from a project roadmap and renumber the rest?

Removing an unstarted future phase deletes its directory and renumbers subsequent phases sequentially. The process updates ROADMAP.md and STATE.md, committing changes to git to maintain roadmap organization and historical record.

Can I remove a phase from the roadmap if it is the current active phase?

No, this Skill validates the target phase against the current phase using confirmation prompts before execution. It strictly handles the removal of unstarted future phases to prevent accidental deletion of active project work.

How does phase renumbering work when removing planned phases from a roadmap?

When a future phase is removed, the Skill automatically renumbers all subsequent phases to maintain a linear sequence. This ensures the roadmap remains sequential without manual file management after the directory is deleted.

Do I need gsd-tools to automate workflow phase removal and git commits?

Yes, gsd-tools.cjs is required. The Skill uses this dependency to handle phase number parsing, validation against the current phase, and confirmation prompts before deleting directories and committing updates to git.

What happens to ROADMAP.md and STATE.md when a future phase is removed?

ROADMAP.md and STATE.md are updated to reflect the removed phase and renumbered sequence. These file modifications are then committed to git, ensuring the project state tracking remains accurate and accountable.