gpd-remove-phase

Removes an unstarted future research phase and renumbers subsequent roadmap phases.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --skill gpd-remove-phase-michaelsengineering
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gpd-remove-phase
Source: https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics/tree/main/.agents/skills/gpd-remove-phase
Command: npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --skill gpd-remove-phase-michaelsengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research roadmaps change: a planned numerical phase may become analytically tractable, a validation step may turn redundant, or scope may shrink. This Skill cleanly deletes an unstarted future phase from the project roadmap, renumbers all subsequent phases, and records the removal as a commit, keeping the phase sequence linear without polluting context with cancelled markers. ## Core Features & Use Cases - Validated Phase Removal: Parses the target phase number, verifies it exists, and confirms it is a future (unstarted) phase before any deletion occurs. - Automatic Renumbering: Delegates directory deletion, file renaming, and ROADMAP.md/STATE.md updates to the gpd CLI so all subsequent phases stay in a clean linear sequence. - Historical Commit Record: Commits the removal with a descriptive message so the deletion is preserved in git history rather than annotated in state files. - Use Case: You planned Phase 17 as a numerical simulation, but found an exact analytical solution. Run the removal to delete Phase 17, renumber Phases 18-22 down by one, and commit the change. ## Quick Start Ask the assistant to remove phase 17 from the roadmap using the gpd-remove-phase skill and confirm the removal when prompted.

Frequently Asked Questions about gpd-remove-phase

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

FAQPage Schema
How do I remove a phase from a gpd research roadmap?▼

Invoke the remove-phase workflow with the target phase number, for example $gpd-remove-phase 17. The skill validates the phase exists, confirms it is unstarted, deletes its directory, renumbers subsequent phases, and commits the change.

Can I remove a phase that has already been started or completed?▼

No, only future phases can be removed. If the target phase is the current phase or already completed, the workflow exits with an error and suggests using the pause-work command instead to abandon current work.

What happens to phases after the removed phase number?▼

All subsequent phases are automatically renumbered by the gpd CLI. Directories are renamed in reverse order to avoid conflicts, files inside them are renamed, and ROADMAP.md and STATE.md references are updated.

Why does phase removal fail when the phase has executed plans?▼

The gpd CLI blocks removal when the phase directory contains SUMMARY.md files indicating executed plans. You can retry with the --force flag only after explicitly confirming with the user.

Is there a dry-run option to preview phase removal?▼

Yes, passing the --dry-run flag shows what would be removed and what renumbering would occur, then stops without making any changes to directories, roadmap files, or git history.