shine-remove-phase

Remove a future roadmap phase and renumber subsequent phases.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-remove-phase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shine-remove-phase
Source: https://github.com/diShine-digital-agency/SHINE-Code-System/tree/main/skills/shine-remove-phase
Command: npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-remove-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Removes a future phase from the roadmap and renumbers all subsequent phases to maintain a clean, linear sequence.

Core Features & Use Cases

  • Clean removal of an unstarted future phase without polluting context with cancelled or deferred work.
  • Automatic renumbering of all following phases to preserve a consistent order.
  • Auditable change with a historical git commit recording the removal.

Quick Start

Provide the phase number to remove and execute the remove-phase workflow to apply the change.

Frequently Asked Questions about shine-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 breaking the sequence?

Yes, after removing a future phase, the workflow automatically renumbers all subsequent phases in the roadmap. This preserves the linear sequence and ensures consistent ordering without manual adjustments.

Can I delete an unstarted roadmap phase and keep an auditable history?

Yes, deleting an unstarted future phase from the roadmap creates a git commit recording the removal. This maintains an auditable history of changes while keeping the context free of cancelled work.

What happens to the phase numbering when I delete a future phase from the workflow?

When you delete a future phase, the workflow automatically renumbers all subsequent phases. Validations ensure the targeted phase exists and proper numbering is maintained throughout the roadmap.

What do I need to provide to remove a phase from a multi-phase roadmap?

To remove a future phase from a multi-phase roadmap, you need to provide the specific phase number. The workflow validates that the future phase exists before removing it and renumbering subsequent phases.

Are there limitations on which roadmap phases can be removed using this workflow?

This workflow applies to roadmaps with multiple phases and specifically targets future phases for removal. Validations ensure the targeted future phase exists before removing it and renumbering subsequent phases.